Like to know how I would determine what is causing udev to delay boot 3 minutes. Recently added another video card with detail listed below. Since I suspect that the cause is the video card I have used the instructions in https://en.opensuse.org/SDB:Configuring_graphics_cards to obtain data on the parts installed. Board is an ASUS P5KPL-CM with 4 gig ram and q6600 cpu OS administrator@linux-ywdy:~> cat /etc/os-release NAME=openSUSE VERSION=“13.2 (Harlequin)” VERSION_ID=“13.2” PRETTY_NAME=“openSUSE 13.2 (Harlequin) (x86_64)” ID=opensuse ANSI_COLOR=“0;32” CPE_NAME=“cpe:/o:opensuse:opensuse:13.2” BUG_REPORT_URL=“https://bugs.opensuse.org” HOME_URL=“https://opensuse.org/” ID_LIKE=“suse” Video Data administrator@linux-ywdy:~> /sbin/lspci -nnk | grep VGA -A2 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) Subsystem: eVga.com. Corp. Device [3842:1450] Kernel driver in use: nouveau Any suggested diagnostic help would be appreciated.
Not sure why you think the delay is in any way related to the video card???
Generally long delays nay be caused by several thing none of them video.
- mounting a partition across a network which is slow or does not respond
- connection to the net slow
- other hardware that is slow to respond or broken or removed
show us systemd-analyze blame
Thanks for your note. I have been unable to repeat the problem of three minute delay. The data you requested is listed below but it was obtained without the 3 min udev delay: 17.008s wicked.service 3.480s ModemManager.service 3.351s display-manager.service 2.913s systemd-logind.service 2.897s SuSEfirewall2_init.service 1.737s lvm2-activation-early.service 1.301s systemd-tmpfiles-setup-dev.service 1.187s rtkit-daemon.service 1.054s dev-hugepages.mount 1.052s sys-kernel-debug.mount 1.052s dev-mqueue.mount 951ms home.mount 941ms systemd-udev-settle.service 899ms systemd-fsck@dev-disk-by\x2duuid-c3e79fae\x2d1f29\x2d406f\x2d8f02\x2d8ddc65350aea.service 896ms systemd-fsck-root.service 785ms lvm2-activation.service 781ms systemd-journald.service 671ms apparmor.service 473ms systemd-tmpfiles-setup.service 461ms systemd-udev-trigger.service 451ms lvm2-lvmetad.service 450ms dm-event.service 440ms postfix.service 377ms systemd-modules-load.service 372ms wickedd-dhcp4.service 365ms polkit.service 365ms systemd-sysctl.service 282ms systemd-random-seed.service 268ms SuSEfirewall2.service 229ms dev-disk-by\x2duuid-fdc701b3\x2d29b4\x2d460d\x2db227\x2df95f2927bbf5.swap 213ms alsa-restore.service 208ms systemd-user-sessions.service I will let the machine cool down and look for the 3 min delay then. The boot message I have been getting just after /home is mounted is: * ]A start job is running for udevWait for Complete Device Initialization (xx sec/2min58s I will post more data as soon as I can replicate the problem.
Thank you for your note. I have been unable to repeat the 3 min delay on udev but have posted
results from /usr/bin/systemd-analyze blame
17.008s wicked.service
3.480s ModemManager.service
3.351s display-manager.service
2.913s systemd-logind.service
2.897s SuSEfirewall2_init.service
1.737s lvm2-activation-early.service
1.301s systemd-tmpfiles-setup-dev.service
1.187s rtkit-daemon.service
1.054s dev-hugepages.mount
1.052s sys-kernel-debug.mount
1.052s dev-mqueue.mount
951ms home.mount
941ms systemd-udev-settle.service
899ms systemd-fsck@dev-disk-by\x2duuid-c3e79fae\x2d1f29\x2d406f\x2d8f02\x2d8ddc65350aea.service
896ms systemd-fsck-root.service
785ms lvm2-activation.service
781ms systemd-journald.service
671ms apparmor.service
473ms systemd-tmpfiles-setup.service
461ms systemd-udev-trigger.service
451ms lvm2-lvmetad.service
450ms dm-event.service
440ms postfix.service
377ms systemd-modules-load.service
372ms wickedd-dhcp4.service
365ms polkit.service
365ms systemd-sysctl.service
282ms systemd-random-seed.service
268ms SuSEfirewall2.service
229ms dev-disk-by\x2duuid-fdc701b3\x2d29b4\x2d460d\x2db227\x2df95f2927bbf5.swap
213ms alsa-restore.service
208ms systemd-user-sessions.service
I will let the machine cool down and try to reproduce the udev 3 min delay. I will send revised data when this happens.
Note that sometime after an update booting can be slow due to new package or perhaps hardware changes being adjusted to. But it is generally a one time thing.
I have been able to reproduce the 3 min delay after the machine cooled down. The message I get on the boot screen is
- ] A start job is running for udev Wait for Complete Device Initialization (xxs/2min58sec)
the results of /usr/bin/systemd-analyzer blame are listed below:
3min 149ms systemd-udev-settle.service
15.529s wicked.service
1.430s systemd-fsck-root.service
1.089s systemd-journald.service
920ms dev-hugepages.mount
919ms dev-mqueue.mount
918ms sys-kernel-debug.mount
842ms ModemManager.service
764ms alsa-restore.service
760ms systemd-user-sessions.service
753ms nscd.service
752ms rc-local.service
750ms avahi-daemon.service
746ms wpa_supplicant.service
594ms systemd-tmpfiles-setup-dev.service
509ms home.mount
494ms systemd-modules-load.service
489ms systemd-udev-trigger.service
473ms [EMAIL="systemd-fsck@dev-disk-by\x2duuid-c3e79fae\x2d1f29\x2d406f\x2d8f02\x2d8ddc65350aea.servic"]systemd-fsck@dev-disk-by\x2duuid-c3e79fae\x2d1f29\x2d406f\x2d8f02\x2d8ddc65350aea.servic[/EMAIL]e
418ms systemd-udevd.service
401ms apparmor.service
320ms SuSEfirewall2_init.service
312ms postfix.service
287ms lvm2-lvmetad.service
287ms dm-event.service
248ms systemd-sysctl.service
227ms SuSEfirewall2.service
181ms display-manager.service
171ms systemd-readahead-replay.service
121ms udisks2.service
120ms systemd-remount-fs.service
100ms [EMAIL="user@1000.servic"]user@1000.servic[/EMAIL]e
86ms lvm2-activation-early.service
69ms polkit.service
66ms systemd-readahead-collect.service
65ms plymouth-read-write.service
59ms systemd-tmpfiles-setup.service
42ms cycle.service
36ms rtkit-daemon.service
36ms systemd-update-utmp.service
26ms kmod-static-nodes.service
22ms ntpd.service
15ms plymouth-start.service
12ms systemd-udev-root-symlink.service
11ms systemd-vconsole-setup.service
11ms wickedd-dhcp4.service
8ms lvm2-activation.service
6ms wickedd-auto4.service
6ms upower.service
5ms systemd-logind.service
5ms systemd-journal-flush.service
5ms dev-disk-by\x2duuid-fdc701b3\x2d29b4\x2d460d\x2db227\x2df95f2927bbf5.swap
4ms iscsi.service
4ms wickedd-dhcp6.service
4ms systemd-update-utmp-runlevel.service
3ms wickedd.service
3ms bluetooth.service
3ms auditd.service
3ms wickedd-nanny.service
2ms systemd-readahead-done.service
1ms systemd-random-seed.service
Please let me know what the cause might be for the delay
The cause is obviously systemd-udev-settle.service
All this service does is execute “udevadm settle” with a timeout of 3 minutes.
I am not sure if it is safe to mask/disable systemd-udev-settle.service, but doing so will probably speed up the boot process.
And why is it only when the machine is cold??? Sounds like a reverse thermal problem. I doubt any software changes will fix the problem some piece of hardware is not functioning right when it is cold. You do need Udev for a properly functioning system. Do you have any USB drives or other hardware plugged (other then keyboard and or mouse)???
He could post some udev logs, but the point is that udev times out (it’s not a coincidence that the service exits after exactly 3 minutes), so no, even after that time the boot process ends while udev is still processing events.
Nothing extra. No USB’s. Motherboard is ASUS P5KPL-CM running a q6600 cpu with 4 gigs of ram. The only recent change has been the video card.
Maybe the best next step is to pull the video card and use the on board Intel GMA 3100 to see if the problem repeats.
Thanks again for your comments.
When you added the card did you turn off the Intel GPU???
Should do that in the BIOS
Solved the problem. Gogalthorp indicated that I should check for usb drives and other equipment. I responded by stating that there were none. That was incorrect. There were two usb scanners connected to the machine. These are HPScanJet G3110 and 6300C.
When either one of the scanners is connected on boot there are no excess delays but when two of them are connected udev holds the boot for three minutes waitng. At the end of the three minutes it proceeds with boot and lists a failure to initialize.
Thanks to all for the suggestions and help.
On 2015-04-19 23:56, newbuilder wrote:
>
> Solved the problem. Gogalthorp indicated that I should check for usb
> drives and other equipment. I responded by stating that there were none.
> That was incorrect. There were two usb scanners connected to the
> machine. These are HPScanJet G3110 and 6300C.
A scanner can take a long time to initialize, because it waits for the
lamp to warm up (the colour of fluorescent lamps changes a bit over the
first minute or two). So the scanner waits that time before reporting
ready to take a scan.
Why that should delay booting, I can not imagine.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))