Same problems here, my panic log file reports the airport kernel extensions aswell... dodgy to connect after waking too.
Also my airtunes has been dropping out heaps when using my airport express but when i connect with Lan it works fine.
Good to know. Assuming this was after applying the late July 2007-004 Airport update, yes?
SUGGESTION TO ALL: To send better info to Apple, let's all please indicate whether we've installed the new July 2007-004 Airport update when posting our issues.
My system is getting progressively worse after installing the Airport update, as it did over days following the 10.4.10 install, and it now drops to 3 bars and cannot connect both a) much more frequently, and b) without working again until cycling Airport off and back on. Last time it began this way, then required switching users or restarting to kick things into gear.
Also to be clear, the old problems only occurred while on battery and wireless. The drops now occur even with the power cord connected. This makes me think to recommend against installing the last Airport update, as without it one can at least plug power in and use wireless consistently.
To save others the effort, here are things tried so far, with Apple's help, that did not work:
1. Adding a new Airport "location" profile
2. Deleting (temporarily removing) the root hard drive's Library/Preferences/SystemConfiguration file.
When trying #2 above, however, I did experience the same quirk I saw when installing 10.4.10, where I could not connect via wireless initially until I turned on SSID broadcasting at least once and selected my router from the Airport menu; after doing this once following the upgrade or SystemConfiguration deletion, I could turn broadcasting back off and still connect. Connecting via "other" while broadcasting was off did not work and gave a "failed to connect" message. Anyone else see this?
Suggestion to all #2: Apple will need to continue to hear from us, via calling tech support or submitting info on their site, so they know the issue was not yet fixed and can get logs and other data from us to help diagnose the problem. Thanks to all who've been posting here as well as letting Apple know directly.