linux-kernel - Re: [OOPS] bcm43xx oops on 2.6.20-rc1 on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061231134302.GJ20714@stusta.de>
Date:	Sun, 31 Dec 2006 14:43:02 +0100
From:	Adrian Bunk <bunk@...sta.de>
To:	Larry Finger <larry.finger@...inger.net>
Cc:	Aaron Sethman <androsyn@...box.org>, linux-kernel@...r.kernel.org,
	linville@...driver.com, netdev@...r.kernel.org, jgarzik@...ox.com
Subject: Re: [OOPS] bcm43xx oops on 2.6.20-rc1 on x86_64

On Sat, Dec 30, 2006 at 04:45:21PM -0600, Larry Finger wrote:
> 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.
>...

To avoid any misunderstandings:

This wasn't in any way meant against you personally.

And in this case you were right, it was the same bug.

My answer was based on experiences like one during 2.6.19-rc where we 
had 4 bug reports for a regression with a patch available. And it turned 
out that one of them was for a completely different regression.

That's why I prefer to get confirmations that a user actually run into 
the same issue, and not into something completely different with similar 
symptoms.

> Larry

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/