Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

2006-11-19 Thread Michael Buesch
On Saturday 18 November 2006 20:02, Larry Finger wrote: > Ray Lee wrote: > > Larry Finger wrote: > >> Johannes Berg wrote: > >>> 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

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

2006-11-18 Thread Larry Finger
Ray Lee wrote: Larry Finger wrote: Johannes Berg wrote: 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. When it happens, I c

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

2006-11-18 Thread Adrian Bunk
On Sat, Nov 18, 2006 at 09:27:13AM -0800, Ray Lee wrote: > Larry Finger wrote: > > Johannes Berg wrote: > >> 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, ple

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

2006-11-18 Thread Ray Lee
Larry Finger wrote: > Johannes Berg wrote: >> 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. When it happens, I can't

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

2006-11-18 Thread Larry Finger
Johannes Berg wrote: 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.

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

2006-11-18 Thread Johannes Berg
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 l

Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?

2006-11-18 Thread Joseph Fannin
On Wed, Nov 15, 2006 at 11:01:00AM -0800, Ray Lee wrote: > I've come back to my laptop being mostly dead after hours of it being off on > its own (twice now). Mostly dead meaning the keyboard is nearly > non-responsive, but the mouse works great (I'm in X, of course). I say 'nearly > dead' as sysr