From: Jeff Garzik <jeff@garzik.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: random wedges with 2.6.25-rc*
Date: Tue, 19 Feb 2008 12:55:13 -0500 [thread overview]
Message-ID: <47BB1801.1000008@garzik.org> (raw)
In-Reply-To: <20080219191035.252d5787@mjolnir.drzeus.cx>
Pierre Ossman wrote:
> Somewhere post 2.6.24, the kernel started getting very temperamentful. I experience random hangs and wedges very often.
>
> Primarily, the udev startup locks up. If I abort it, it just locks up on more or less every action after that. Some quick debugging showed that I had a whole bunch of modprobe processes sitting around. The new CONFIG_USB_ANNOUNCE_NEW_DEVICES setting makes every startup of udev lock up consistently on at least two machines. It does not seem to be the root of the problem as disabling the option just makes the bug very unlikely.
>
> I've also seen a couple of lockups in X. Might be a different expression of the same bug, but the effect here is a complete wedge of the user interface. It seems the rest of the machine also locks up, but I haven't confirmed this.
>
> Anyone else seeing these problems? Someone should as I've seen the problem on both a Lenovo and a HP laptop here.
I'm definitely seeing lockups here too. 2.6.24 is fine, 2.6.24-rc1 or
-rc2 locks up a minute or so after a successful boot (either to console
or to X).
Does the following shed any light?
http://lkml.org/lkml/2008/2/17/78
Jeff
next prev parent reply other threads:[~2008-02-19 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 18:10 random wedges with 2.6.25-rc* Pierre Ossman
2008-02-19 17:55 ` Jeff Garzik [this message]
2008-02-19 20:51 ` Pierre Ossman
2008-02-19 19:58 ` Alistair John Strachan
2008-02-19 20:25 ` David Rees
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=47BB1801.1000008@garzik.org \
--to=jeff@garzik.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.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.