From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: wireless <linux-wireless@vger.kernel.org>, bcm43xx-dev@lists.berlios.de
Subject: Re: Fatal DMA error problem with netbook and BCM4312
Date: Sun, 22 Nov 2009 19:52:47 -0600 [thread overview]
Message-ID: <4B09EAEF.6010202@lwfinger.net> (raw)
In-Reply-To: <20091122190353.06cfdab7@boulder.homenet>
On 11/22/2009 01:03 PM, Chris Vine wrote:
> On Sat, 21 Nov 2009 00:15:12 +0000
> Chris Vine <chris@cvine.freeserve.co.uk> wrote:
>> WARM BOOT FROM KERNEL WITH WL MODULE INSTALLED
>>
>> The patched kernel makes no change on a warm boot in the sense that
>> if I warm boot after initialising the wireless device with the wl
>> module then the b43 module appears to work correctly, both with and
>> without the patch applied.
>>
>> On the same stress test as mentioned above, I have not been able to
>> induce the DMA errors nor kernel warnings. It resolutely refuses to
>> do anything except work correctly.
>
> This is just to say that I have carried out further stress tests today
> after warm booting to an unpatched linux-2.6.32-rc8 kernel with the b43
> driver (on the assumption that unpatched is the least favourable case
> for the driver). This is a warm reboot from a 2.6.31.6 kernel which had
> the wl driver installed.
>
> I have created an extended period of high speed traffic on my wireless
> lan and I cannot induce any errors at all with the b43 driver on a warm
> reboot.
>
> This makes me wonder whether the patch is just (partially) masking the
> problem rather than actually dealing with it.
We know that the wl driver does something to the interface that persists across
a warm boot - we just do not know what. It does not appear to be done in any of
the MMIO traffic - at least I have not seen it in the mmio-trace output. If
anyone has a KVM setup using PCI passthrough, it is possible to trace PCI
configuration traffic?
Have you tried running your system with the patch entitled "[PATCH] b43: Rewrite
DMA Tx status handling sanity checks"? It cleared up some of the problems that I
was seeing with the open-source firmware.
Larry
next prev parent reply other threads:[~2009-11-23 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AFA09C8.4060602@gmail.com>
[not found] ` <200911131216.43704.mb@bu3sch.de>
[not found] ` <4AFD83CA.2050508@lwfinger.net>
[not found] ` <200911131836.26857.mb@bu3sch.de>
[not found] ` <4AFD9E20.3060501@gmail.com>
[not found] ` <4AFDD1C9.4050402@lwfinger.net>
[not found] ` <4AFDF68C.4040804@polymtl.ca>
[not found] ` <4AFE1E5F.9040009@lwfinger.net>
[not found] ` <4AFEFC2C.5030704@polymtl.ca>
2009-11-20 12:43 ` Fatal DMA error problem with netbook and BCM4312 Larry Finger
2009-11-20 19:58 ` Chris Vine
2009-11-20 20:05 ` Larry Finger
2009-11-21 0:15 ` Chris Vine
2009-11-22 19:03 ` Chris Vine
2009-11-23 1:52 ` Larry Finger [this message]
2009-11-23 10:18 ` Johannes Berg
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=4B09EAEF.6010202@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=chris@cvine.freeserve.co.uk \
--cc=linux-wireless@vger.kernel.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.