devfs
[Top] [All Lists]

Re: Bug#145718: devfsd: invalid operand: 0000

To: Matt Zimmerman <mdz@xxxxxxxxxx>, 145718@xxxxxxxxxxxxxxx
Subject: Re: Bug#145718: devfsd: invalid operand: 0000
From: Russell Coker <russell@xxxxxxxxxxxx>
Date: Sat, 4 May 2002 09:07:48 +1000
Cc: devfs@xxxxxxxxxxx
In-reply-to: <20020503184119.GA15110@alcor.net>
References: <20020503184119.GA15110@alcor.net>
Reply-to: Russell Coker <russell@xxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx
On Sat, 4 May 2002 04:41, you wrote:
> I have a system which periodically issues this error, killing devfsd:
>
> invalid operand: 0000
> CPU:    1
> EIP:    0010:[<c0147871>]    Not tainted

Firstly, I'm not sure that the Debian BTS is an appropriate forum for such 
bugs.  Secondly it's definately not a devfsd issue, naturally if your kernel 
is correctly functioning then nothing devfsd will do will cause a panic.

> Details vary, of course, but the stack trace is pretty much the same
> always. The system is running a custom 2.4.17 kernel, the only substantial
> differences from the stock 686-smp kernel are CONFIG_HIGHMEM4G=y and
> CONFIG_MPENTIUMIII=y.
>
> I am about to upgrade to a similar 2.4.18 kernel, and will report as to
> whether I see this happen again (could take a few days).

Have you applied any devfs patches to 2.4.17?  I never got a 2.4.17 kernel to 
do devfs without a patch, and even with a patch there were some issues.

I recommend using 2.4.16 or 2.4.18 for devfs as both of them worked for me.


Russell Coker


PS  I would like to re-assign this to your kernel package, or close it.

PPS I'll forward your bug report to devfs@xxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>