From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
"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 14:46:57 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002261430430.4513@localhost.localdomain> (raw)
In-Reply-To: <69e28c911002261408j4f5fa5cdo6a69a43749d99f3f@mail.gmail.com>
On Fri, 26 Feb 2010, Gábor Stefanik wrote:
>
> Well, we have a report from someone with an Intel T7250, which is
> definitely neither a slow CPU nor a ULV. The machine has PhoenixBIOS
> (in the same rebranded form as yours). My Intel T7100 + InsydeH2O
> machine (almost the same CPU, but with Insyde EFI in BIOS emulation
> mode instead of PhoenixBIOS, or maybe TrustedCore) didn't reproduce
> the bug. The trigger still seems to be PhoenixBIOS.
Well, I'd love to give you a register dump. It _looks_ like it should be
possible write some script to dump all the registers by accessing
/sys/kernel/debug/b43/phy0/[mmio,shm][16,32]read
but that's a very odd interface and I don't know what the index ranges are
for them (and which registers need 16-bit vs 32-bit accesses).
But if you give me a script to dump all the relevant registers, I could
just dump them after a cold-boot, and _before_ loading the b43 driver fir
the first time. Maybe you can compare it to your state with your BIOS, in
the same situation, and see if there is some obvious difference that
strikes you?
Of course, maybe there is some hidden state that doesn't show up there
either?
Linus
next prev parent reply other threads:[~2010-02-26 22:47 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
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 [this message]
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=alpine.LFD.2.00.1002261430430.4513@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=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 \
/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