On Thu, 2010-09-23 at 17:02 +0200, Johannes Berg wrote: > On Thu, 2010-09-23 at 07:53 -0700, Luis R. Rodriguez wrote: > > > >> After roaming for a good while, this is what I got, not sure > > >> yet what caused the NULL pointer dereference... Am I the only > > >> one able to reproduce this? > > > > > >> [ 3276.730081] BUG: unable to handle kernel NULL pointer dereference at 0000000000000003 > > >> [ 3276.730148] IP: [<0000000000000003>] 0x3 > > > > > > Something called a NULL pointer function pointer. Rafael recently said > > > "cpuidle is buggy" when a similar issue came up: > > > http://mid.gmane.org/201009182344.12498.rjw@xxxxxxx > > > > But that seems related to ACPI, no? On my box I never suspended, I > > just associated and disassociated rapidly between two peers. The only > > suspicion I have is its obviously right after adding the STA peer. > > Yes, but he said suspend/resume _fixed_ it :-) Hm never mind, misunderstood the original report ... suspend + wait + resume was what was broken. But still, it's a NULL pointer call, and I can't really see how that would happen. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
