----- Forwarded message from Ingo Molnar <mingo@xxxxxxx> ----- > Delivery-date: Fri, 03 Oct 2008 06:03:27 -0400 > Date: Fri, 3 Oct 2008 12:02:11 +0200 > From: Ingo Molnar <mingo@xxxxxxx> > To: Steven Noonan <steven@xxxxxxxxxxxxxx> > Cc: linux-kernel@xxxxxxxxxxxxxxx, ath9k-devel@xxxxxxxxxxxxxxx, > lrodriguez@xxxxxxxxxxx > Subject: Re: ath9k: panic on tip/master > In-Reply-To: <f488382f0810030256x2859fbf6j3f657621c567287f@xxxxxxxxxxxxxx> > List-ID: <linux-kernel.vger.kernel.org> > X-Mailing-List: linux-kernel@xxxxxxxxxxxxxxx > > * 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). > > 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. > > Ingo > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > ----- End forwarded message ----- -- 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
