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
[ 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)'?
--
David C. Rankin, J.D.,P.E.
