linux-kernel - Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl

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: <1163868955.27188.2.camel@johannes.berg>
Date:	Sat, 18 Nov 2006 17:55:55 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Joseph Fannin <jhf@...umbus.rr.com>
Cc:	Ray Lee <ray-lk@...rabbit.org>,
	Larry Finger <Larry.Finger@...inger.net>,
	Bcm43xx-dev@...ts.berlios.de, LKML <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org, John Linville <linville@...driver.com>,
	Michael Buesch <mb@...sch.de>, Andrew Morton <akpm@...l.org>
Subject: Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

On Sat, 2006-11-18 at 06:24 -0500, Joseph Fannin wrote:

>     This sounds like what my laptop was doing in -rc5, though mine
> didn't take hours to start acting up.
> 
>     I *think* it was the MSI troubles, causing interrupts to get
> lost forever.  Anyway, it went away in -rc6.

Hah, that's a lot more plausible than bcm43xx's drain patch actually
causing this. So maybe somehow interrupts for bcm43xx aren't routed
properly or something...

Ray, please check /proc/interrupts when this happens.

I am convinced that the patch in question (drain tx status) is not
causing this -- the patch should be a no-op in most cases anyway, and in
those cases where it isn't a no-op it'll run only once at card init and
remove some things from a hardware-internal FIFO.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (191 bytes)