From: Johannes Berg <johannes@sipsolutions.net>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Peter Osterlund <petero2@telia.com>,
linux-kernel@vger.kernel.org, Bcm43xx-dev@lists.berlios.de,
"John W. Linville" <linville@tuxdriver.com>,
Netdev <netdev@vger.kernel.org>
Subject: Re: Occational lockups during boot with post 2.6.22 kernels
Date: Wed, 18 Jul 2007 17:51:10 +0200 [thread overview]
Message-ID: <1184773870.4002.8.camel@johannes.berg> (raw)
In-Reply-To: <469E2AAB.2010408@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Wed, 2007-07-18 at 10:58 -0400, Chuck Ebbert wrote:
> On 07/17/2007 08:20 PM, Peter Osterlund wrote:
> > Current -git kernels sometimes lock up on my computer during boot. I
> > guess it happens about 10-20% of the time. I first saw this maybe a
> > week ago, but never with kernels <= 2.6.22.
> >
> > The last reported info on the console is that named is started.
> > SysRq-T still works and reports the non-sleeping tasks below.
> >
> > My guess is that wpa_supplicant and events/0 deadlock and later the
> > named thread also hangs when it needs a deadlocked resource.
> >
> > I'm using the bcm43xx driver.
> >
> > No lockdep errors are reported before the lockup. Earlier during boot
> > the kernel reports:
> >
> > Good, all 218 testcases passed! |
>
> Try this, it should at least detect the problem:
>
> http://lkml.org/lkml/2007/7/17/202
> http://lkml.org/lkml/2007/7/17/204
> http://lkml.org/lkml/2007/7/17/203
>
> It's a known bug in wireless/80211, not sure when it will be fixed.
Heh, yes, that's the patchset that came from this bug :)
A patch for this is available but due to process issues hasn't
percolated up yet. See
http://thread.gmane.org/gmane.linux.kernel.wireless.general/3315/focus=3319
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-07-18 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 0:20 Peter Osterlund
2007-07-18 14:58 ` Chuck Ebbert
2007-07-18 15:51 ` Johannes Berg [this message]
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=1184773870.4002.8.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=petero2@telia.com \
/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
all inboxes | Powered by JetHome®