From: Larry Finger <larry.finger@lwfinger.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: Aaron Sethman <androsyn@ratbox.org>,
linux-kernel@vger.kernel.org, linville@tuxdriver.com,
netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [OOPS] bcm43xx oops on 2.6.20-rc1 on x86_64
Date: Sat, 30 Dec 2006 16:45:21 -0600 [thread overview]
Message-ID: <4596EC01.3060508@lwfinger.net> (raw)
In-Reply-To: <20061230213245.GD20714@stusta.de>
Adrian Bunk wrote:
> On Sat, Dec 30, 2006 at 03:23:42PM -0600, Larry Finger wrote:
>> Adrian Bunk wrote:
>>> On Sun, Dec 17, 2006 at 03:15:28PM -0500, Aaron Sethman wrote:
>>>> Just was loading the bcm43xx module and got the following oops. Note that
>>>> this card is one of the newer PCI-E cards. If any other info is needed
>>>> let me know.
>>> Is this issue still present in 2.6.10-rc2-git1?
>>>
>>> If yes, was 2.6.19 working fine?
>> ...
>>
>> Any oops involving wireless extensions is due to 2.6.20-rc1 and -rc2 not having the fix for softmac
>> that is necessitated by the 2.6.20 changes in the work structure.
>
> "Any oops" are very strong words.
Yes - but I have seen at least 7 or 8 different occurrences of that bug since the patch was first
made available on Dec. 10, and I have seen no bcm43xx oopses from any other cause.
> It wouldn't be the first time that we have several similar bug reports,
> and it turns out that one is for a completely different issue...
>
> That's why I asked for testing with 2.6.20-rc2-git1 that includes the
> two ieee80211softmac patches.
I have been chasing a sound-card issue today and missed that -git1 was out. That version fixes the
two outstanding 2.6.20 softmac issues.
Larry
next prev parent reply other threads:[~2006-12-30 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0612171510030.17532@squeaker.ratbox.org>
2006-12-30 19:21 ` [OOPS] bcm43xx oops on 2.6.20-rc1 on x86_64 Adrian Bunk
2006-12-30 21:23 ` Larry Finger
2006-12-30 21:32 ` Adrian Bunk
2006-12-30 22:45 ` Larry Finger [this message]
2006-12-31 13:43 ` Adrian Bunk
2006-12-31 14:22 ` Larry Finger
2006-12-31 4:14 ` Aaron Sethman
2006-12-31 5:14 ` Larry Finger
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=4596EC01.3060508@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=androsyn@ratbox.org \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).