On 28.11.2014 14:35, Robert Milasan wrote: > On Fri, 28 Nov 2014 14:28:31 +0100 > "Harald Hoyer" <harald.ho...@gmail.com> wrote: > >> >> I think what we are seeing here is, that module loading saturates the >> udev workers here. So there are at least 16 modprobes (kmod) running >> and this hinders further processing of the uevents. >> >> In theory we could increase arg_children_max before builtin_kmod() >> and decrease it again afterwards. >> >> CC'ing Kay >> _______________________________________________ > > Ok, I've decreased the arg_children_max number from CPU_COUNT * 256 to > CPU_COUNT * 64. You where right, it was a bit too much. >
I doubt, that we need that much more workers for your bug report to boot faster. Try passing --children-max=<num> in the systemd-udevd.service file and then report the lowest number. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
