(b) The systemd guys think that kernel module loading takes more than
30 seconds is a kernel module's bug. But Linux kernel guys won't
be able to fix it immediately. Also, solution by updating firmware
won't be acceptable because there will be users who can't update
firmware for some reason.
(d) I tried to rebuild systemd package with longer timeout but I was
unable to build it without build failures. Therefore, I opened a
bug report in order to ask for systemd package with longer
timeout, but no response so far.
Well, it is unlikely that this situation is solved within 7 days.
I think that applying the patch in comment #48 as a
"[trusty] UBUNTU: SAUCE:" patch is the safest choice for 14.04 LTS
kernel.
(a) Linux kernel guys think that a hardcoded timeout is a systemd bug.
https:/ /lkml.org/ lkml/2014/ 3/23/42
(b) The systemd guys think that kernel module loading takes more than
30 seconds is a kernel module's bug. But Linux kernel guys won't
be able to fix it immediately. Also, solution by updating firmware
won't be acceptable because there will be users who can't update
firmware for some reason.
http:// lists.freedeskt op.org/ archives/ systemd- devel/2014- March/018007. html
The systemd guys suggest that adding OPTIONS+ ="event_ timeout= 120"
to udev rules might help, but I don't think it will help.
https:/ /lkml.org/ lkml/2014/ 3/22/207
(c) The LVM guys added OPTIONS+ ="event_ timeout= 180" before
commit 786235ee was merged into Linux kernel.
http:// www.redhat. com/archives/ lvm-devel/ 2013-September/ msg00036. html
(d) I tried to rebuild systemd package with longer timeout but I was
unable to build it without build failures. Therefore, I opened a
bug report in order to ask for systemd package with longer
timeout, but no response so far.
https:/ /bugs.launchpad .net/ubuntu/ +source/ systemd/ +bug/1297248
Well, it is unlikely that this situation is solved within 7 days.
I think that applying the patch in comment #48 as a
"[trusty] UBUNTU: SAUCE:" patch is the safest choice for 14.04 LTS
kernel.