Created attachment 875486 [details] Proposed patch Increase the firmware timeout of 60s seconds to 600s by writing into /sys/class/firmware/timeout. This should be done before any module is loaded. The timeout begins as soon as the module loaded. udev might work on the uevent any time later on, so the firmware can timeout before udev even looks at the uevent. Because of the modprobe locking patch, things get worse, because we serialize network related modprobes. If the maximum number of childs is reached, the timespan can even get longer or even deadlock. This patch should go along with a solution for bug 1028174
related: bug 1077186
Please test http://people.redhat.com/harald/downloads/udev/udev-147-2.53.el6/
ahem, which version is this fixed-in? I went down to udev-147-2.51.el6.i686, rebooted the system, and ... # cat /sys/class/firmware/timeout 600 so I cannot prove anything got fixed in udev-147-2.57.el6 as the value is the same or is there any other way to test?
It's also set in the initramfs, so that might have already set it.
(In reply to Harald Hoyer from comment #6) > It's also set in the initramfs, so that might have already set it. so I've run `dracut -f` and rebooted ... and the timeout is still set to 600
(In reply to Karel Volný from comment #7) > (In reply to Harald Hoyer from comment #6) > > It's also set in the initramfs, so that might have already set it. > > so I've run `dracut -f` and rebooted ... and the timeout is still set to 600 and you installed an old dracut and an old udev? The udev patch is in udev-147-2.53 and the dracut patch in dracut-004-347.
(In reply to Harald Hoyer from comment #8) > and you installed an old dracut and an old udev? > > The udev patch is in udev-147-2.53 and the dracut patch in dracut-004-347. old dracut? - I don't get it why, but anyways ... with udev-147-2.51.el6.i686 and dracut-004-336.el6.noarch: .live.[root@i386-6s-m1 ~]# cat /sys/class/firmware/timeout 60 with either of those updated: .qa.[root@i386-6s-m1 ~]# cat /sys/class/firmware/timeout 600
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1524.html