Thread (10 messages) flat view 10 messages, 7 authors, 2007-09-17

Re: 2.6.23-rc4-mm1 OOPS in forcedeth?

From: Satyam Sharma <hidden>
Date: 2007-09-02 00:41:48
Also in: lkml

Hi Jurriaan,

thunder7@xs4all.nl wrote:
quoted
From: Andrew Morton <akpm@linux-foundation.org>
Date: Fri, Aug 31, 2007 at 09:58:22PM -0700
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help