Bug#333052: Bug#333522: possible problem cause: wait4(-1)
- To: Horms <horms@debian.org>
- Cc: 333052@bugs.debian.org
- Subject: Bug#333052: Bug#333522: possible problem cause: wait4(-1)
- From: md@Linux.IT (Marco d'Itri)
- Date: Wed, 26 Oct 2005 09:37:54 +0200
- Message-id: <20051026073754.GB4537@wonderland.linux.it>
- Reply-to: md@Linux.IT (Marco d'Itri), 333052@bugs.debian.org
- In-reply-to: <20051026042337.GN6423@verge.net.au>
- References: <20051013210709.GA14583@wonderland.linux.it> <1129528496.32584.39.camel@localhost.localdomain> <4354FAEF.7040502@fujitsu-siemens.com> <1129683244.18557.4.camel@localhost.localdomain> <20051019131453.GA9713@wonderland.linux.it> <20051020014024.GE28032@debian.org> <20051020074407.GA4830@wonderland.linux.it> <20051021092615.GC9453@debian.org> <20051021145435.GA9472@wonderland.linux.it> <20051026042337.GN6423@verge.net.au>
On Oct 26, Horms <horms@debian.org> wrote:
> Just to clarify, udevd gets a bunch of events and tries to
> serialise them into modprobe calls, right? Do you think there
There is no serialization, only some throttling (IIRC it tries to run up
to 10 child processes in parallel).
> is any chance it might be calling modprobe out of order
> for some reason.
The point is the dependencies are handled by modprobe, so the order in
which udevd loads the modules at the top of the dependency tree is not
relevant.
As Rusty suggested I wrapped /sbin/modprobe in a logger script, but so
far I have not been able to reproduce the bug again (which may or may
not be related, I need a few more reboots).
--
ciao,
Marco
Attachment:
signature.asc
Description: Digital signature
Reply to: