From: "Bob Copeland" <me@bobcopeland.com>
To: Hugh Dickins <hugh@veritas.com>,
"John W. Linville" <linville@tuxdriver.com>
Cc: ath5k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org,
Jiri Slaby <jirislaby@gmail.com>,
maximlevitsky@gmail.com
Subject: Re: [ath5k-devel] ath5k_tasklet_rx BUG_ON(bf->skb == NULL)
Date: Fri, 6 Feb 2009 15:58:38 -0500 [thread overview]
Message-ID: <20090206205043.M903@bobcopeland.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0902061857410.25517@blonde.anvils>
On Fri, 6 Feb 2009 19:01:28 +0000 (GMT), Hugh Dickins wrote
> On Fri, 6 Feb 2009, John W. Linville wrote:
> > Hmmm...well it is a little big, but I guess it is OK. Do you have
> > an example of the stack trace? Or a link to a bugzilla or somesuch
> > would be even better...
>
> Below is my original report: I didn't copy down the stacktrace,
> and the kernel paniced with "Fatal exception in interrupt", so
> nothing I can send you from the logs I'm afraid.
I can generate the panic if you like, but it will need to wait a few
hours until I am back home to the machine with the serial console.
I just forced one of the skb allocations to fail to test it.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-02-06 20:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 13:49 ath5k_tasklet_rx BUG_ON(bf->skb == NULL) Hugh Dickins
2009-01-08 14:46 ` [ath5k-devel] " Maxim Levitsky
2009-01-08 16:18 ` Hugh Dickins
2009-01-08 17:10 ` Bob Copeland
2009-01-08 17:55 ` Hugh Dickins
2009-01-08 18:41 ` Bob Copeland
2009-01-09 13:41 ` Bob Copeland
2009-01-09 14:10 ` Hugh Dickins
2009-01-10 16:47 ` Bob Copeland
2009-01-10 20:15 ` Bob Copeland
2009-01-13 15:35 ` Hugh Dickins
2009-01-13 15:56 ` Bob Copeland
2009-01-13 16:40 ` Hugh Dickins
2009-01-13 17:45 ` Luis R. Rodriguez
2009-02-06 13:12 ` Hugh Dickins
2009-02-06 18:37 ` Bob Copeland
2009-02-06 18:44 ` John W. Linville
2009-02-06 19:01 ` Hugh Dickins
2009-02-06 20:58 ` Bob Copeland [this message]
2009-02-09 2:30 ` Bob Copeland
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=20090206205043.M903@bobcopeland.com \
--to=me@bobcopeland.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=hugh@veritas.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maximlevitsky@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).