All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Michael Buesch <mb@bu3sch.de>,
	Bcm43xx-dev@lists.berlios.de, LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?
Date: Wed, 15 Nov 2006 20:51:05 -0600	[thread overview]
Message-ID: <455BD219.8080104@lwfinger.net> (raw)
In-Reply-To: <455B6D74.2020507@madrabbit.org>

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 trigger, if the pattern holds, so in the
> meantime, any *other* thoughts?
> 

Which chip and revision do you have? Send me your equivalent of the line "bcm43xx: Chip ID 0x4306, 
rev 0x2".

Thanks,

Larry



WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Ray Lee <ray-lk-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
	Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble?
Date: Wed, 15 Nov 2006 20:51:05 -0600	[thread overview]
Message-ID: <455BD219.8080104@lwfinger.net> (raw)
In-Reply-To: <455B6D74.2020507-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>

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 trigger, if the pattern holds, so in the
> meantime, any *other* thoughts?
> 

Which chip and revision do you have? Send me your equivalent of the line "bcm43xx: Chip ID 0x4306, 
rev 0x2".

Thanks,

Larry

  reply	other threads:[~2006-11-16  2:51 UTC|newest]

Thread overview: 38+ 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
2006-11-15 19:15 ` Michael Buesch
2006-11-15 19:15   ` Michael Buesch
2006-11-15 19:41   ` Ray Lee
2006-11-16  2:51     ` Larry Finger [this message]
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
2006-11-18 16:55   ` Johannes Berg
2006-11-18 16:55     ` Johannes Berg
2006-11-18 17:05     ` Larry Finger
2006-11-18 17:05       ` Larry Finger
2006-11-18 17:27       ` Ray Lee
2006-11-18 18:30         ` Adrian Bunk
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
2006-12-12 18:31                 ` Larry Finger
2006-12-12 18:31                   ` Larry Finger
2006-11-19  6:15         ` Problem with DMA on x86_64 with 3 GB RAM Larry Finger
2006-11-21  4:38           ` Ray Lee
2006-11-21 11:28             ` Alan
2006-11-21 16:34               ` Larry Finger
2006-11-21 10:30           ` Andi Kleen
2006-11-21 16:37             ` Larry Finger
2006-11-21 16:46               ` Andi Kleen
2006-11-21 18:27                 ` Alan
2006-11-21 18:31                   ` Andi Kleen
2006-11-21 20:04                     ` Alan

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=455BD219.8080104@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.