Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

FYI: caution with udev 165 in -current

18 views
Skip to first unread message

Douglas Mayne

unread,
Dec 29, 2010, 12:15:43 PM12/29/10
to
I am running -current with a self compiled kernel, 2.6.35.9 on a test
box. This is the first time in a while that I decided to try -current,
and it is bit "bleeding" edge. I started experiencing bootup kernel oops
and random crashes after applying a series of the latest patches on Dec
24. I see others are having similar problems as reported on Linux
Questions:
http://preview.tinyurl.com/2b8mjqn

I can confirm that the oops seems very much related to when udev is
loaded in the initrd.

This was noted in the changelog on Dec 19:
a/udev-165-i486-1.txz

I am going to test rolling back to udev-164, if I can find it in my
repository.

--
Douglas Mayne

Douglas Mayne

unread,
Dec 29, 2010, 4:34:46 PM12/29/10
to

I rolled back to the last version I could find, udev-164-i486-3.

So far, it is working fine. That gives some circumstantial confirmation
that it is udev that is at fault, and not mdadm, lvm2, or another package
of the set of updates issued on the same time interval.

--
Douglas Mayne

Grant

unread,
Dec 30, 2010, 3:40:31 AM12/30/10
to
On Wed, 29 Dec 2010 17:15:43 +0000 (UTC), Douglas Mayne <no...@invalid.com> wrote:

>I am running -current with a self compiled kernel, 2.6.35.9 on a test
>box.

Did you notice 2.6.35.10 in it's new home on kernel.org?

I'm no help with udev...

Grant.

Petri Kaukasoina

unread,
Dec 30, 2010, 4:34:35 AM12/30/10
to
Douglas Mayne <no...@invalid.com> wrote:
>I rolled back to the last version I could find, udev-164-i486-3.

Here I have the latest with version number 4, in case someone needs it:
http://butler.cc.tut.fi/~kaukasoi/slackware/

0 new messages