Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-21 Thread Horms
I did a bit of a poke around this symbols problem. I puzzeled over it for a while. I began to wonder if it might be caused byudevsynthesize[1] which seems to be the major change between -2 and -4, and I completely failed in all my attempts to reproduce the problem. [1] http://marc.theaimsgroup.com

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-21 Thread Marco d'Itri
On Oct 21, Horms <[EMAIL PROTECTED]> wrote: > I did a bit of a poke around this symbols problem. > I puzzeled over it for a while. I began to wonder > if it might be caused byudevsynthesize[1] which seems > to be the major change between -2 and -4, and I completely > failed in all my attempts to r

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-25 Thread Horms
On Fri, Oct 21, 2005 at 04:54:35PM +0200, Marco d'Itri wrote: > On Oct 21, Horms <[EMAIL PROTECTED]> wrote: > > > I did a bit of a poke around this symbols problem. > > I puzzeled over it for a while. I began to wonder > > if it might be caused byudevsynthesize[1] which seems > > to be the major c

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-26 Thread Marco d'Itri
On Oct 26, Horms <[EMAIL PROTECTED]> 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

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-26 Thread Horms
On Wed, Oct 26, 2005 at 09:37:54AM +0200, Marco d'Itri wrote: > On Oct 26, Horms <[EMAIL PROTECTED]> 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

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-27 Thread Marco d'Itri
On Oct 27, Horms <[EMAIL PROTECTED]> wrote: > > There is no serialization, only some throttling (IIRC it tries to run up > > to 10 child processes in parallel). > Ok, but it runs modprobe, not ismod, right? Yes. > > As Rusty suggested I wrapped /sbin/modprobe in a logger script, but so > > far I

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-28 Thread Rusty Russell
On Thu, 2005-10-27 at 10:10 +0200, Marco d'Itri wrote: > And then it fails for ehci-hcd too (which is not loaded at all). > Rusty, do you have other ideas for debugging? I have reread the bug reports, and meditated on this issue some more. This is a possibility I was aware of when I changed to cod

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-28 Thread Horms
On Fri, Oct 28, 2005 at 05:24:44PM +1000, Rusty Russell wrote: > On Thu, 2005-10-27 at 10:10 +0200, Marco d'Itri wrote: > > And then it fails for ehci-hcd too (which is not loaded at all). > > Rusty, do you have other ideas for debugging? > > I have reread the bug reports, and meditated on this is

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-28 Thread Marco d'Itri
On Oct 28, Rusty Russell <[EMAIL PROTECTED]> wrote: > The latter is the simplest option. Please try this patch (it will be in > the next release, too). If it seems to work, please ack. No luck. -- ciao, Marco signature.asc Description: Digital signature

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-28 Thread Rusty Russell
On Fri, 2005-10-28 at 15:08 +0200, Marco d'Itri wrote: > On Oct 28, Rusty Russell <[EMAIL PROTECTED]> wrote: > > > The latter is the simplest option. Please try this patch (it will be in > > the next release, too). If it seems to work, please ack. > No luck. Please send complete log. I might n

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-31 Thread Marco d'Itri
On Oct 29, Rusty Russell <[EMAIL PROTECTED]> wrote: > Please send complete log. Here it is. I can reproduce the bug even with a script like: while read m; do /sbin/modprobe.real $m & done < LIST (Each command was logged to different files which have been sorted by PID and reassembled.) =[ pi

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-10-31 Thread Rusty Russell
On Mon, 2005-10-31 at 19:53 +0100, Marco d'Itri wrote: > On Oct 29, Rusty Russell <[EMAIL PROTECTED]> wrote: > > > Please send complete log. > Here it is. I can reproduce the bug even with a script like: > > while read m; do > /sbin/modprobe.real $m & > done < LIST > > > (Each command was log

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-11-01 Thread Marco d'Itri
On Nov 01, Rusty Russell <[EMAIL PROTECTED]> wrote: > Hmm, if the root filesystem is read-only, then the locking will fail > (you need to open a file read/write to get an exclusive fcntl lock). > Perhaps this is happening to you? If not, please check again that you Sure, all of this happens when

Bug#333052: Bug#333522: possible problem cause: wait4(-1)

2005-11-01 Thread Horms
On Tue, Nov 01, 2005 at 09:35:35AM +0100, Marco d'Itri wrote: > On Nov 01, Rusty Russell <[EMAIL PROTECTED]> wrote: > > > Hmm, if the root filesystem is read-only, then the locking will fail > > (you need to open a file read/write to get an exclusive fcntl lock). > > Perhaps this is happening to y