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...
Ray,
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
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
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.
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. The
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, please check
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
Ray Lee wrote:
Larry Finger wrote:
Ray Lee wrote:
Michael Buesch wrote:
On Wednesday 15 November 2006 20:01, Ray Lee wrote:
Suggestions? Requests for shudder even more info?
Yeah, enable bcm43xx debugging.
Sigh, didn't even think to look for that. Okay, enabled and compiling
a new kernel.
On Thursday 16 November 2006 19:17, Larry Finger wrote:
Ray Lee wrote:
Larry Finger wrote:
Ray Lee wrote:
Michael Buesch wrote:
On Wednesday 15 November 2006 20:01, Ray Lee wrote:
Suggestions? Requests for shudder even more info?
Yeah, enable bcm43xx debugging.
Sigh, didn't even
Ray Lee wrote:
If I could figure out a way to make it repeatable, I'd happily do a blind
bisect. As it stands, I can't trigger it manually. I've got a while true; do
iwconfig eth1; done running to hit the ioctls (as the trace in my first
message showed one of them in use), but that's might be a
First off, thanks for all your help.
Second off,
On 11/16/06, Larry Finger [EMAIL PROTECTED] wrote:
Ray Lee wrote:
If I could figure out a way to make it repeatable, I'd happily do a blind
bisect.
[...]
I'm open to suggestions on how to make the problem trigger more than once
every two
Ray Lee wrote:
First off, thanks for all your help.
Second off,
On 11/16/06, Larry Finger [EMAIL PROTECTED] wrote:
Ray Lee wrote:
If I could figure out a way to make it repeatable, I'd happily do a
blind
bisect.
[...]
I'm open to suggestions on how to make the problem trigger more than
Hey all,
I ran 2.6.19-rc3 for almost two weeks or so with no difficulties (none related
to the bcm43xx driver, at least). However, Andrew asked me to double check the
latest release to see if my problem report against 2.6.18 (hard locks) was
fixed. Good news is that it still is fixed. Bad news is
Ray Lee wrote:
Michael Buesch wrote:
On Wednesday 15 November 2006 20:01, Ray Lee wrote:
Suggestions? Requests for shudder even more info?
Yeah, enable bcm43xx debugging.
Sigh, didn't even think to look for that. Okay, enabled and compiling a new
kernel. This will take a few days to
Larry Finger wrote:
Ray Lee wrote:
Michael Buesch wrote:
On Wednesday 15 November 2006 20:01, Ray Lee wrote:
Suggestions? Requests for shudder even more info?
Yeah, enable bcm43xx debugging.
Sigh, didn't even think to look for that. Okay, enabled and compiling
a new kernel. This will take
15 matches
Mail list logo
