From: Adrian Bunk <bunk@stusta.de>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Johannes Berg <johannes@sipsolutions.net>,
Joseph Fannin <jhf@columbus.rr.com>,
Andrew Morton <akpm@osdl.org>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
John Linville <linville@tuxdriver.com>,
Michael Buesch <mb@bu3sch.de>,
Bcm43xx-dev@lists.berlios.de
Subject: Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?
Date: Sat, 18 Nov 2006 19:30:01 +0100 [thread overview]
Message-ID: <20061118183001.GY31879@stusta.de> (raw)
In-Reply-To: <455F4271.1060405@madrabbit.org>
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 /proc/interrupts when this happens.
>
> When it happens, I can't. The keyboard is entirely dead (I'm in X, perhaps at
> a console it would be okay). The only thing that works is magic SysRq. even
> ctrl-alt-f1 to get to a console doesn't work.
>
> That said, /proc/interrupts doesn't show MSI routed things on my AMD64 laptop.
>...
If there is any interrupt related problem involved, it should be visible
from dmesg.
Can you send the complete dmesg's from -rc3, -rc5 and -rc6?
> Ray
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
next prev parent reply other threads:[~2006-11-18 18:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 19:01 bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble? Ray Lee
[not found] ` <455B63EC.8070704-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>
2006-11-15 19:15 ` Michael Buesch
2006-11-15 19:41 ` Ray Lee
[not found] ` <455B6D74.2020507-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>
2006-11-16 2:51 ` Larry Finger
2006-11-16 5:51 ` Ray Lee
2006-11-16 18:17 ` Larry Finger
[not found] ` <455CAB2F.1060709-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-11-16 19:16 ` Michael Buesch
2006-11-16 19:36 ` Ray Lee
[not found] ` <455CBDD7.6000507-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>
2006-11-16 22:40 ` Larry Finger
2006-11-16 23:26 ` Ray Lee
[not found] ` <ae017dc00611161526v6bcbddc2ve2c7e10963d25c3b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-11-17 1:13 ` Larry Finger
2006-11-18 11:24 ` Joseph Fannin
[not found] ` <20061118112438.GB15349-JY2TvBve8Und/56dcus+/6462+2Rg2F6@public.gmane.org>
2006-11-18 16:55 ` Johannes Berg
[not found] ` <1163868955.27188.2.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2006-11-18 17:05 ` Larry Finger
2006-11-18 17:27 ` Ray Lee
2006-11-18 18:30 ` Adrian Bunk [this message]
2006-11-21 6:21 ` Ray Lee
2006-11-18 19:02 ` Larry Finger
2006-11-19 16:01 ` Michael Buesch
2006-12-12 4:06 ` ieee80211 sleeping in invalid context Ray Lee
2006-12-12 9:14 ` Michael Buesch
2006-12-12 17:51 ` Ray Lee
[not found] ` <457EEC1E.9000806-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>
2006-12-12 18:31 ` 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=20061118183001.GY31879@stusta.de \
--to=bunk@stusta.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.net \
--cc=akpm@osdl.org \
--cc=jhf@columbus.rr.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=ray-lk@madrabbit.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).