From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: [mingo@elte.hu: Re: ath9k: panic on tip/master]
Date: Fri, 3 Oct 2008 11:10:06 -0400 [thread overview]
Message-ID: <20081003151006.GB3368@tuxdriver.com> (raw)
----- Forwarded message from Ingo Molnar <mingo@elte.hu> -----
> Delivery-date: Fri, 03 Oct 2008 06:03:27 -0400
> Date: Fri, 3 Oct 2008 12:02:11 +0200
> From: Ingo Molnar <mingo@elte.hu>
> To: Steven Noonan <steven@uplinklabs.net>
> Cc: linux-kernel@vger.kernel.org, ath9k-devel@lists.ath9k.org,
> lrodriguez@atheros.com
> Subject: Re: ath9k: panic on tip/master
> In-Reply-To: <f488382f0810030256x2859fbf6j3f657621c567287f@mail.gmail.com>
> List-ID: <linux-kernel.vger.kernel.org>
> X-Mailing-List: linux-kernel@vger.kernel.org
>
> * Steven Noonan <steven@uplinklabs.net> 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@vger.kernel.org
> 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@tuxdriver.com of your literate lifestyle.
reply other threads:[~2008-10-03 15:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081003151006.GB3368@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.