From: Hugh Dickins <hugh@veritas.com>
To: Bob Copeland <bcopeland@gmail.com>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
linux-wireless@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>,
ath5k-devel@venema.h4ckr.net
Subject: Re: [ath5k-devel] ath5k_tasklet_rx BUG_ON(bf->skb == NULL)
Date: Fri, 9 Jan 2009 14:10:50 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0901091400290.925@blonde.anvils> (raw)
In-Reply-To: <b6c5339f0901090541m1ac135bcta91bacb3f048a9ba@mail.gmail.com>
On Fri, 9 Jan 2009, Bob Copeland wrote:
> On Thu, Jan 8, 2009 at 1:41 PM, Bob Copeland <bcopeland@gmail.com> wrote:
> > On Thu, Jan 8, 2009 at 12:55 PM, Hugh Dickins <hugh@veritas.com> wrote:
> >> Let me see if I can reproduce the ath5k BUG with a straightforward
> >> memhog, repeatedly dirtying more anon memory than RAM can provide.
> >> Is there something suitable I could run to exercise that wireless
> >> path concurrently? It was just idling when I hit the BUGs before.
> >
> > Receiving any packets will do it, in your case it was probably
> > beacons from nearby APs if you weren't using the wifi. So iperf
> > or similar will work.
>
> Actually it's probably enough to just intentionally fail one
> of the allocations in the driver. I'll do that and let you know
> if I can easily break it.
Good, that should be a lot quicker.
My overnight try with simple memhog, and iperf -s receiving from
another machine doing iperf -c at intervals, didn't hit it (but my
more involved test wouldn't necessarily have hit it in that time either).
Currently trying just a 2.6.28 defconfig kernel build in tmpfs
(other filesystems should get their dirty pages pdflushed sooner)
along with the iperf, but haven't got the sizes suitably tuned yet.
Hugh
next prev parent reply other threads:[~2009-01-09 14:11 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 [this message]
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=Pine.LNX.4.64.0901091400290.925@blonde.anvils \
--to=hugh@veritas.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=bcopeland@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--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