Re: Bug#333522: possible problem cause: wait4(-1)
- To: md@Linux.IT, 333522@bugs.debian.org, martin.wilck@fujitsu-siemens.com, kay.sievers@vrfy.org, debian-kernel@lists.debian.org, control@bugs.debian.org
- Subject: Re: Bug#333522: possible problem cause: wait4(-1)
- From: Horms <horms@debian.org>
- Date: Thu, 20 Oct 2005 10:40:26 +0900
- Message-id: <[🔎] 20051020014024.GE28032@debian.org>
- Mail-followup-to: md@Linux.IT, 333522@bugs.debian.org, martin.wilck@fujitsu-siemens.com, kay.sievers@vrfy.org, debian-kernel@lists.debian.org, control@bugs.debian.org
- In-reply-to: <[🔎] 20051019131453.GA9713@wonderland.linux.it>
- 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>
On Wed, Oct 19, 2005 at 03:14:53PM +0200, Marco d'Itri wrote:
> reassign 333522 linux-2.6
> thank
>
> On Oct 19, Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> > Right. It's not a modprobe bug then. Thanks, that makes sense.
> Oops... I did not read correctly Rusty's answer.
> If it's not a modprobe bug and not an udev bug (I checked udevd and it
> looks fine to me) then looks like it is a kernel bug.
Could you please point me to the part of the code where udevd calls
modprobe and handles the subsequent SIGCHLD? That will be a good starting poing
for further investigation.
--
Horms
Reply to: