From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
b43-dev <b43-dev@lists.infradead.org>
Subject: [RFT] BCM4312 users with DMA errors, please test!
Date: Mon, 16 Aug 2010 20:01:45 -0500 [thread overview]
Message-ID: <4C69DF79.2020900@lwfinger.net> (raw)
In-Reply-To: <20100817011455.4919cfbb@boulder.homenet>
On 08/16/2010 07:14 PM, Chris Vine wrote:
>>
>> I have reproduced it twice. It is definitely the patch, in the sense
>> that it happens with the patch included (on two separate tests that I
>> have conducted) and never without.
>>
>> I do not doubt that you do not experience this effect. However, you
>> don't experience the DMA bug either.
>
> Out of interest, which version of the wl module do you have installed,
> as I wonder if that makes a difference? (As I said in my e-mail on
> this, this problem only occurs if the wl module is available to the
> kernel.)
My wl came from hybrid-portsrc-x86_32-v5.60.48.36.tar.gz. My kernel is
2.6.36-rc1 from mainline.
Very strange that a patch to ssb, which is a module that cannot even load due to
being blacklisted, can cause this kind of problem. Are you warm or cold rebooting?
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: [RFT] BCM4312 users with DMA errors, please test!
Date: Mon, 16 Aug 2010 20:01:45 -0500 [thread overview]
Message-ID: <4C69DF79.2020900@lwfinger.net> (raw)
In-Reply-To: <20100817011455.4919cfbb@boulder.homenet>
On 08/16/2010 07:14 PM, Chris Vine wrote:
>>
>> I have reproduced it twice. It is definitely the patch, in the sense
>> that it happens with the patch included (on two separate tests that I
>> have conducted) and never without.
>>
>> I do not doubt that you do not experience this effect. However, you
>> don't experience the DMA bug either.
>
> Out of interest, which version of the wl module do you have installed,
> as I wonder if that makes a difference? (As I said in my e-mail on
> this, this problem only occurs if the wl module is available to the
> kernel.)
My wl came from hybrid-portsrc-x86_32-v5.60.48.36.tar.gz. My kernel is
2.6.36-rc1 from mainline.
Very strange that a patch to ssb, which is a module that cannot even load due to
being blacklisted, can cause this kind of problem. Are you warm or cold rebooting?
Larry
next prev parent reply other threads:[~2010-08-17 1:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 17:59 [RFT] BCM4312 users with DMA errors, please test! Gábor Stefanik
2010-08-16 17:59 ` Gábor Stefanik
[not found] ` <AANLkTin0R6k0_GoSEN8aJ8t_fTJw9h_N_0etcxAokv6N@mail.gmail.com>
2010-08-16 18:15 ` Gábor Stefanik
2010-08-16 18:15 ` Gábor Stefanik
[not found] ` <AANLkTinkx+FjrAR48dziDR2kX48JRcjm3SF7jhhi4_oM@mail.gmail.com>
2010-08-16 18:45 ` Gábor Stefanik
2010-08-16 18:45 ` Gábor Stefanik
2010-08-17 15:49 ` Arthur Moreira
2010-08-16 19:06 ` Larry Finger
2010-08-16 19:06 ` Larry Finger
2010-08-16 19:16 ` Gábor Stefanik
2010-08-16 19:16 ` Gábor Stefanik
2010-08-16 19:30 ` Larry Finger
2010-08-16 19:30 ` Larry Finger
2010-08-16 19:32 ` Gábor Stefanik
2010-08-16 19:32 ` Gábor Stefanik
2010-08-16 19:41 ` Chris Vine
2010-08-16 19:41 ` Chris Vine
2010-08-16 22:35 ` Chris Vine
2010-08-16 22:35 ` Chris Vine
2010-08-16 23:53 ` Larry Finger
2010-08-16 23:53 ` Larry Finger
2010-08-17 0:09 ` Chris Vine
2010-08-17 0:09 ` Chris Vine
2010-08-17 0:10 ` Chris Vine
2010-08-17 0:10 ` Chris Vine
2010-08-17 0:14 ` Chris Vine
2010-08-17 0:14 ` Chris Vine
2010-08-17 1:01 ` Larry Finger [this message]
2010-08-17 1:01 ` Larry Finger
2010-08-17 12:23 ` Chris Vine
2010-08-17 12:23 ` Chris Vine
2010-08-17 20:28 ` Chris Vine
2010-08-17 20:28 ` Chris Vine
2010-08-17 20:38 ` Gábor Stefanik
2010-08-17 20:38 ` Gábor Stefanik
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=4C69DF79.2020900@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--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.