linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	linux-wireless@vger.kernel.org, ath5k-devel@venema.h4ckr.net
Subject: Re: [ath5k-devel] ath5k_tasklet_rx BUG_ON(bf->skb == NULL)
Date: Thu, 08 Jan 2009 16:46:57 +0200	[thread overview]
Message-ID: <1231426017.922.2.camel@maxim-laptop> (raw)
In-Reply-To: <Pine.LNX.4.64.0901081318190.22793@blonde.anvils>

On Thu, 2009-01-08 at 13:49 +0000, Hugh Dickins wrote:
> Thank you for the ath5k wireless driver,
> which I've just started using on an Aspire One.
> 
> When running swapping load tests, wireless alive but not in active use,
> I've now twice hit the BUG_ON(bf->skb == NULL) in ath5k_tasklet_rx().
> 
> First time was with 2.6.28 plus kdb patch,
> kernel BUG at drivers/net/wireless/ath5k/base.c:1675!
> and poking around the messages I could see before that an
> ath5k phy0: can't alloc skbuff of size 2673, after a
> swapper: page allocation failure, order:0 mode:0x4020
> on a call from dev_alloc_skb(), with memory summary.
> 
> Second time was with yesterday's 2.6.28-git, no kdb,
> kernel BUG at drivers/net/wireless/ath5k/base.c:1683!
> running ath5k_tasklet_rx() from under do_softirq(),
> Kernel panic - not syncing: Fatal exception in interrupt
> so I couldn't see more; but at the top of the screen, the
> last three lines of a page allocation failure memory summary.
> 
> So, that BUG_ON(bf->skb == NULL) appears to be unsafe under
> memory pressure; but the fix wasn't obvious to me, so over
> to you!
> 
> I'd be glad to try patches, of course, but it's not happening
> often enough for me to report back success quickly - unless I
> stumble on a quicker way to reproduce it, it'll need a week or
> two to grow confident of a fix.
> 
> Thanks,
> Hugh


I use aspire one, and I don't see that, did this happen several times?


Could you try compat-wireless:

http://wireless.kernel.org/en/users/Download


It has many fixes that made my wireless on that notebook more or less
usable.

Best regards,
	Maxim Levitsky


  reply	other threads:[~2009-01-08 14:47 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 ` Maxim Levitsky [this message]
2009-01-08 16:18   ` [ath5k-devel] " 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
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=1231426017.922.2.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=hugh@veritas.com \
    --cc=jirislaby@gmail.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 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).