[arch-general] What causes the 3-5 sec delay before :: running early hooks (udev)?

[Leonid Isaev]

On Wed, 20 Jun 2012 14:44:53 -0500
"David C. Rankin" <drankinatty at suddenlinkmail.com> wrote:

> On 06/20/2012 01:10 PM, Tom Gundersen wrote:
> > It is either the kernel or the initramfs. Your dmesg might tell you more
> > (possibly some misbehaving kernel module?). Also, what modules/hooks do you
> > have in your initramfs?
> >
> > Tom
> 
> Thanks Arno, Tom,
> 
>    There are no non-default hooks on the desktops. They all have:
> 
> HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"
> 
>    On my 2 server boxes, I have dmraid in this order:
> 
> MODULES="dm_mod dm_mirror"
> HOOKS="base udev autodetect pata scsi sata dmraid filesystems usbinput fsck"
> 
>    I do note that fsck was added at some point in time, but that was a
> default and not something I added.
> 
>    Looking at dmesg, I see the following delays > 2 sec:
> 
> [    7.957888] EXT4-fs (sdc5): mounting ext3 file system using the ext4
> subsystem [    8.016583] EXT4-fs (sdc5): mounted filesystem with ordered
> data mode. Opts: (null)
> [   10.236553] udevd[140]: starting version 185

No, you need logs much before that. Udev should be noted twice in dmesg: one
is when initramfs is unpacked (with low PID ~ 40); and you posted another.

> 
> [   13.895401] vgaarb: device changed decodes: 
> PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
> [   13.942931] NVRM: loading NVIDIA UNIX x86 Kernel Module  302.17  Tue Jun
> 12 18:37:51 PDT 2012
> [   31.985912] EXT4-fs (sdc5): re-mounted. Opts: (null)
> [   32.049154] EXT4-fs (sdc7): mounted filesystem with ordered data mode. 
> Opts: (null)
> 
> There is 19 sec for NVIDIA.
> 
> [   35.656087] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [   46.656677] eth0: no IPv6 routers present
> 
> 11 secs for network init.
> 
> [   46.656677] eth0: no IPv6 routers present
> [  144.443911] vboxdrv: Found 2 processor cores.
> 
> 98 sec courtesy of dkms and a new kernel.
> 
>    I don't know, but the delay I see before the ':: running early hooks 
> (udev)' message does not seem to correlate to these entries in dmesg. Is
> dmesg logging even active before the ':: running early hooks (udev)'?
> 

Yes, everything is in dmesg.log and kernel.log (unless you have reconfigured
syslog).

-- 
Leonid Isaev
GnuPG key: 0x164B5A6D
Fingerprint: C0DF 20D0 C075 C3F1 E1BE  775A A7AE F6CB 164B 5A6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20120620/e2c96a26/attachment.asc>