On Fri, Oct 03, 2008 at 12:02:11PM +0200, Ingo Molnar wrote: > > * Steven Noonan <steven@xxxxxxxxxxxxxx> wrote: > > > Hey folks, > > > > Just got a panic on tip. According to the stack trace, ath9k is what > > decided to bomb. > > > > http://www.uplinklabs.net/~tycho/linux/ath9k_panic_tip_10.3.2008.jpg > > > > Note: Although it says 'sudo modprobe radeon' on the bash prompt above > > the panic, I never got to hit 'enter' on that command before the panic > > occurred. > > it appears to me that ath9k's eth_rx_input() takes a spinlock that is > not initialized (or already destroyed by the allocator). Seems reasonable... > this would be consistent with an IRQ storm hitting some race in the > ath9k driver init sequence. For example if request_irq() is done before > all structures that the IRQ handler relies on are properly initialized. > > i.e. this has the signature of a genuine ath9k bug. Agreed, although I don't see anything specifically relating to request_irq or the like. I think the spin_lock call may actually be in ath_ampdu_input (called from ath_rx_input), which perhaps is getting called simultaneous with ath_rx_node_init still running? With no locks in between them, it seems like this could be the culprit? Sorry to not be more immediately helpful, but I'm going to have to run in a few minutes. Perhaps this insight is helpful for someone more familiar with the internals of this driver? John -- John W. Linville Linux should be at the core linville@xxxxxxxxxxxxx of your literate lifestyle. -- 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
