From: Chris Vine <chris@cvine.freeserve.co.uk>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>,
"Michael Büsch" <mb@bu3sch.de>,
b43-dev <b43-dev@lists.infradead.org>
Subject: b43 error under heavy load
Date: Wed, 1 Jun 2011 13:08:42 +0100 [thread overview]
Message-ID: <20110601130842.077da1c3@boulder.homenet> (raw)
In-Reply-To: <BANLkTin_RnMV3KnGS4qYPtMVxCuW=Vj7mg@mail.gmail.com>
On Wed, 1 Jun 2011 12:56:22 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> 2011/6/1 Chris Vine <chris@cvine.freeserve.co.uk>:
> > On Wed, 1 Jun 2011 11:23:45 +0200
> > Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> >> AFAIK to enable this debugging you only need to:
> >> echo 1 > /sys/kernel/debug/b43/phy0/debug_dmaverbose
> >
> > I don't have a /sys/kernel/debug directory with a running 3.0.0-rc1
> > kernel, so it appears that b43 debugging (which I do have enabled)
> > doesn't use it.
>
> mount -t debugfs none /sys/kernel/debug/
Ah, so I need to compile in debugfs. That isn't/wasn't necessary for
the DMA error debugging. I am surprised that debugfs enables you to
alter kernel debugging levels on the fly (I thought it was a
passive logging mechanism for kernel state), but you live and learn.
I will compile in debugfs, but I don't expect to have any rapid results
for you. With 3 and a half hours of streaming yesterday it happened
once. I won't be able to do much testing by way of transferring files
over the LAN for a while either (I imagine that would provide greater
stress testing).
Chris
next prev parent reply other threads:[~2011-06-01 12:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 18:41 b43 error under heavy load Larry Finger
2010-11-22 18:53 ` Michael Büsch
2010-11-22 19:12 ` Larry Finger
2011-05-10 5:08 ` Rafał Miłecki
2011-05-10 18:34 ` Larry Finger
2011-05-10 21:19 ` Rafał Miłecki
2011-06-01 9:23 ` Rafał Miłecki
2011-06-01 9:24 ` Rafał Miłecki
2011-06-01 10:48 ` Chris Vine
2011-06-01 10:56 ` Rafał Miłecki
2011-06-01 12:08 ` Chris Vine [this message]
2011-06-01 12:25 ` Rafał Miłecki
2011-06-01 15:01 ` Chris Vine
2011-06-01 15:42 ` Rafał Miłecki
2011-06-01 17:49 ` Chris Vine
2011-06-01 18:03 ` Rafał Miłecki
2011-06-01 18:09 ` Chris Vine
2011-06-01 18:10 ` Rafał Miłecki
2011-07-26 9:28 ` Chris Vine
2011-08-14 11:10 ` Rafał Miłecki
2011-08-14 11:11 ` Rafał Miłecki
2011-08-14 20:46 ` Chris Vine
2011-08-14 20:54 ` Rafał Miłecki
2011-08-14 21:19 ` Chris Vine
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=20110601130842.077da1c3@boulder.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=zajec5@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).