linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	"David S. Miller" <davem@davemloft.net>,
	wireless <linux-wireless@vger.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@suse.de>
Subject: Re: Make b43 driver fall back gracefully to PIO mode after fatal DMA  errors
Date: Fri, 26 Feb 2010 15:01:51 -0600	[thread overview]
Message-ID: <4B8836BF.7000403@lwfinger.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1002261246330.4513@localhost.localdomain>

On 02/26/2010 02:50 PM, Linus Torvalds wrote:
> 
> 
> On Fri, 26 Feb 2010, Gábor Stefanik wrote:
>>
>> Does actually enabling mmiotrace fix it for you too?
> 
> I haven't seen the report. What do you need to do? Certainly just enabling 
> CONFIG_MMIOTRACE does nothing, but I'd not expect it to - I'd expect that 
> you have to actually do the tracing itself.
> 
> So if somebody has a recipe for me to test actual tracing of the module, I 
> can try to see if it makes a difference for me.

If you do the following (as root):

modprobe -r b43
echo 6400 > /sys/kernel/debug/tracing/buffer_size_kb
echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
modprobe b43

do some network activity, then

echo nop > /sys/kernel/debug/tracing/current_tracer
sleep 1
killproc cat

That should be a good enough test. If your machine behaves the same as has been
reported, you should see a DMA error at the point that tracing is turned off.

Larry


  reply	other threads:[~2010-02-26 21:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.00.1002261034140.4513@localhost.localdomain>
2010-02-26 19:09 ` Make b43 driver fall back gracefully to PIO mode after fatal DMA errors Larry Finger
2010-02-26 19:13   ` Linus Torvalds
2010-02-26 20:06     ` Linus Torvalds
2010-02-26 20:09       ` Gábor Stefanik
2010-02-26 20:50         ` Linus Torvalds
2010-02-26 21:01           ` Larry Finger [this message]
2010-02-26 21:45             ` Linus Torvalds
2010-02-26 21:50               ` Linus Torvalds
2010-02-26 22:08                 ` Gábor Stefanik
2010-02-26 22:46                   ` Linus Torvalds
2010-02-26 22:54                     ` Gábor Stefanik
2010-02-27 15:04                     ` Michael Buesch
2010-02-27 14:59                 ` Michael Buesch
2010-02-27 18:31                   ` Linus Torvalds
2010-02-27 18:51                     ` Michael Buesch
2010-02-26 19:59   ` Michael Buesch
2010-02-26 20:07     ` Linus Torvalds
2010-02-26 20:20       ` Michael Buesch
2010-02-26 20:33         ` Linus Torvalds
2010-02-26 20:42           ` Linus Torvalds
2010-02-27 14:44             ` Michael Buesch
2010-02-27 14:49           ` Michael Buesch
2010-02-27 17:36           ` Michael Buesch
2010-02-27 20:12             ` Nathan Schulte
2010-02-27 21:08             ` Linus Torvalds
2010-02-27 21:43               ` Michael Buesch
2010-02-27 22:12                 ` Linus Torvalds
2010-02-26 20:46 Nathan Schulte

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=4B8836BF.7000403@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netrolller.3d@gmail.com \
    --cc=torvalds@linux-foundation.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).