From: Chris Vine <chris@cvine.freeserve.co.uk>
To: b43-dev <b43-dev@lists.infradead.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: [RFT] BCM4312 users with DMA errors, please test!
Date: Tue, 17 Aug 2010 21:28:25 +0100 [thread overview]
Message-ID: <20100817212825.6f5ecb66@boulder.homenet> (raw)
In-Reply-To: <20100817132337.01392797@boulder.homenet>
On Tue, 17 Aug 2010 13:23:37 +0100
Chris Vine <chris@cvine.freeserve.co.uk> wrote:
> Reverting to 2.6.35.1 solves this. Probably 2.6.36-rc1 would be OK as
> well. I might later today try the ssb patch on the 2.6.35.1 kernel,
> but it doesn't look as if it solves the DMA errors. However,
> yesterday's tests clearly aren't conclusive about anything.
I have applied the patch to 2.6.35.1, and it does not appear to have
any effect on the DMA errors.
Chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: b43-dev <b43-dev@lists.infradead.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT] BCM4312 users with DMA errors, please test!
Date: Tue, 17 Aug 2010 21:28:25 +0100 [thread overview]
Message-ID: <20100817212825.6f5ecb66@boulder.homenet> (raw)
In-Reply-To: <20100817132337.01392797@boulder.homenet>
On Tue, 17 Aug 2010 13:23:37 +0100
Chris Vine <chris@cvine.freeserve.co.uk> wrote:
> Reverting to 2.6.35.1 solves this. Probably 2.6.36-rc1 would be OK as
> well. I might later today try the ssb patch on the 2.6.35.1 kernel,
> but it doesn't look as if it solves the DMA errors. However,
> yesterday's tests clearly aren't conclusive about anything.
I have applied the patch to 2.6.35.1, and it does not appear to have
any effect on the DMA errors.
Chris
next prev parent reply other threads:[~2010-08-17 20:28 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
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 [this message]
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=20100817212825.6f5ecb66@boulder.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--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.