From: Michael Buesch <mb@bu3sch.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
"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: Sat, 27 Feb 2010 15:59:20 +0100 [thread overview]
Message-ID: <201002271559.20531.mb@bu3sch.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1002261345300.4513@localhost.localdomain>
On Friday 26 February 2010 22:50:35 Linus Torvalds wrote:
>
> On Fri, 26 Feb 2010, Linus Torvalds wrote:
> >
> > so even if mmiotrace fixes it for others, it's not working for me.
>
> Side note: In case this is timing-related: the machine in question is a
> dual-core 1.3Ghz CPU (Core 2 Duo U1400). I think SMP has always been
> enabled, I don't think I ever tried UP.
>
> Also, in addition to the PIO fallback code, that particular mmiotrace test
> was done with the "udelay(10)" added to the b43_write*() functions. So it
> was even slower.
>
> Maybe the bug only happens on slow machines (and then the udelay obviously
> wouldn't help!),
I'm pretty sure it's triggered by some kind of BIOS background service.
Power saving or something like that. There must be some interference
that fucks up the memory link between machine->ssb->wireless.
However, did you add the udelay to b43_write()? Please try to add it
further down in the callchain into the lowlevel SSB read and write functions.
drivers/ssb/pci.c
I don't think it'll help at all, but it's worth a try.
--
Greetings, Michael.
next prev parent reply other threads:[~2010-02-27 14:59 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
2010-02-26 22:54 ` Gábor Stefanik
2010-02-27 15:04 ` Michael Buesch
2010-02-27 14:59 ` Michael Buesch [this message]
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=201002271559.20531.mb@bu3sch.de \
--to=mb@bu3sch.de \
--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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.