Re: 2.6.23-rc4-mm1 OOPS in forcedeth?

[Satyam Sharma <satyam@infradead.org>]

Hi Jurriaan,


> thunder7@xs4all.nl wrote:
> > From: Andrew Morton <akpm@linux-foundation.org>
> > Date: Fri, Aug 31, 2007 at 09:58:22PM -0700
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc4/2.6.23-rc4-mm1/
> > > 
> > On this machine (Athlon 64 X2 4600, 4 GiB memory, lots of disks),
> > 2.6.23-rc1-mm2 runs fine. 2.6.23-rc4-mm1 reproducably dies within seconds of
> > starting
> > a rsync session on another PC against this machine.
> > 
> > NULL pointer dereference
> > code:	nv_napi_poll+0x108
> > trace:	net_rx_action+0xab
> > 	__do_softirq+0x74
> > 	call_softirq+0x1c
> > 	do_softirq+0x3d
> > 	irq_exit+0x85
> > 	do_IRQ+0x85
> > 	ret_from_intr+0x0

The dmesg you posted below doesn't cover the messages from this oops
itself. As you mentioned you can reproduce this oops easily, please do so,
and post the *full* oops log (if it doesn't get logged to disk, you can
try taking digicam photo, or write down *all* the messages and post here).
I built an x86_64 kernel as per your .config, but don't see any memory
dereference at nv_napi_poll+0x108 -- could be toolchain differences.

Else, can you run:
$ gdb ./vmlinux

and then:
(gdb) l *nv_napi_poll+0x108

and send us the output?


Satyam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/