On Tue, 2009-06-02 at 15:59 -0500, Larry Finger wrote: > I'm trying to test, but I get an oops on boot. I'm still tracking it > and I lose the reason off the top of the screen, but the trace is: > > queue_work + 0x1a > schedule_work + 0x16 > rfkill_resume_polling + 0x23 > wiphy_rfkill_start_polling + 0x35 (Line 452 of net/wireless/core.c) > b43_op_start + 0x172 (Line 4336 of drivers/net/wireless/b43/main.c) > > The offsets are appropriate for wireless-testing and x86_64. The line > in b43_op_start is the one just before the mutex_unlock. > > Is it possible that we reached this point without hw->wiphy being set? Thanks for testing. This doesn't happen on a current wireless-testing tree I hope? I'll look more into it tomorrow, need some sleep now. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
