devfs
[Top] [All Lists]

Re: Kernel-oops with devfsd on 2.4.17-SMP

To: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Subject: Re: Kernel-oops with devfsd on 2.4.17-SMP
From: Raoul Borenius <borenius@xxxxxxxxxx>
Date: Wed, 9 Jan 2002 11:59:53 +0100
Cc: devfs@xxxxxxxxxxx
In-reply-to: <200201090606.g0966HZ29892@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <20020107093548.GA763@xxxxxxxxxxxxxxxx> <200201090606.g0966HZ29892@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx
User-agent: Mutt/1.3.25i
Hi Richard,

thanks for the reply.

For the moment I'm going to disable the NV-Driver with the current
kernel and see if the oops is gone.

If not I'll cook a new kernel with debug.

Regards

Raoul

On Tue, Jan 08, 2002 at 11:06:17PM -0700, Richard Gooch wrote:
> Raoul Borenius writes:
> > devfsd gives me random kernel-oopses on my box. Attached ist the output
> > from ksymoops and from 'dmesg' since boot. I'm running Debian/Sid with
> > a self-compiled Kernel from the Debian kernel-source-package.
> > 
> > If there is some more testing required, please tell me what I can do.
> 
> Unfortunately, you're running the NVidia driver, to which we don't
> have the complete source code, so diagnosis is impossible. If you can
> temporarily move that module and reboot with "devfs=dall", that might
> provide helpful information. Note that you need to enable these DEBUG
> options when compiling the kernel:
> CONFIG_DEVFS_DEBUG=y
> CONFIG_DEBUG_KERNEL=y
> CONFIG_DEBUG_HIGHMEM=y
> CONFIG_DEBUG_SLAB=y
> CONFIG_DEBUG_IOVIRT=y
> CONFIG_DEBUG_SPINLOCK=y
> CONFIG_DEBUG_BUGVERBOSE=y
> 
> You'll want to use -s65536 when running dmesg, to get as much debug
> information as possible. And another decoded Oops will be required.
> 
>                               Regards,
> 
>                                       Richard....
> Permanent: rgooch@xxxxxxxxxxxxx
> Current:   rgooch@xxxxxxxxxxxxxxx

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