On Tue, Jul 27, 2004 at 03:01:45PM +0200, Javier wrote:
>
> > Hopefully 2.4.26-4 will make it into sarge shortly.
> > Please let me know how you go with this bug.
>
> Still hasn't reproduced (crossing fingers). Isn't the debug information
> sufficient to determine which part of the kernel might be broken?
Perhaps, though the kernel is a complex beast and if the bug
can't reliably be reproduced it hard to know exactly where
the problem lies.
I noticed in your trace that signal handling functions featured,
notably in the first oops in the trace you sent yesterday. This
makes me syspect CAN-2004-0554. Certainly that seems to be
the only relevant change since 2.4.26-2.
On Tue, Jul 27, 2004 at 03:01:45PM +0200, Javier wrote:
>
> > Hopefully 2.4.26-4 will make it into sarge shortly.
> > Please let me know how you go with this bug.
>
> Still hasn't reproduced (crossing fingers). Isn't the debug information
> sufficient to determine which part of the kernel might be broken?
Perhaps, though the kernel is a complex beast and if the bug
can't reliably be reproduced it hard to know exactly where
the problem lies.
I noticed in your trace that signal handling functions featured,
notably in the first oops in the trace you sent yesterday. This
makes me syspect CAN-2004-0554. Certainly that seems to be
the only relevant change since 2.4.26-2.
--
Horms