Re: "seeing minute plus hangs during boot" - 2.6.12 and 2.6.13

From: Andrew Morton
Date: Sun Jul 31 2005 - 00:46:46 EST


"Francisco Figueiredo Jr." <fxjrlists@xxxxxxxxxxxx> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andrew Morton wrote:
> > "Francisco Figueiredo Jr." <fxjrlists@xxxxxxxxxxxx> wrote:
> >
> >>udev S 00000002 0 1312 1 1224 (NOTLB)
> >> c1653f4c 00000082 c1653f3c 00000002 00000001 00000040 c1653f64 c1653f0c
> >> c016611b bfec96a8 c1653f0c 00000040 00000000 00000361 000241ed
> >> c13fb520
> >> 00000001 00001a7e 98f9769f 00000002 c146e520 df5da020 df5da148
> >> c13fbf60
> >> Call Trace:
> >> [<c016611b>] cp_new_stat+0x15f/0x17a
> >> [<c0352a74>] schedule_timeout+0x54/0xa2
> >> [<c01274ce>] process_timeout+0x0/0x9
> >> [<c01275c4>] sys_nanosleep+0xdd/0x18e
> >> [<c0102e85>] syscall_call+0x7/0xb
> >
> >
> > Well there's your delay: you've started running userspace and udev is
> > running. Yes, it takes a long time.
> >
> > What makes you think this isn't normal behaviour? Do other kernels behave
> > differently with the same userspace setup?
> >
>
>
> That's the point. On kernel 2.6.11 on same box I have no delay. It is
> instantaneous. On 2.6.12-rc1 it was instantaneous but I didn't use it
> much because I had drm problems. Later I tried 2.6.12 final and it was
> hanging. I saw the "seeing a minute plugs hangs" on 2.6.13-rc1 release
> notes and thought this could be the problem, but I compiled it and tried
> with no luck :(
>
> Now, I'm thinking it could be something like the udev hang which
> disapeared with udev update to 058.
>
> I don't know what can be happening. I think it is because of some type
> of timeout.
>
> If you think there is something else I can do, please let me know.
>

Greg said in another thread: "older versions of udev (< 058) can work
_really slow_ with 2.6.12. Please upgrade your version of udev and see if
that solves the issue or not.".

What version are you running? Looks like 058, yes?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/