netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: thunder7@xs4all.nl
To: Satyam Sharma <satyam@infradead.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	thunder7@xs4all.nl, Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.23-rc4-mm1 OOPS in forcedeth?
Date: Sun, 2 Sep 2007 08:19:00 +0200	[thread overview]
Message-ID: <20070902061900.GA5595@amd64.of.nowhere> (raw)
In-Reply-To: <alpine.LFD.0.999.0709020610590.20781@enigma.security.iitk.ac.in>

From: Satyam Sharma <satyam@infradead.org>
Date: Sun, Sep 02, 2007 at 06:24:29AM +0530
> 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.
> 
There are 4 pictures of oopses here:

http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_1.jpg
http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_2.jpg
http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_3.jpg
http://www.xs4all.nl/~thunder7/oops_2623rc4mm1_4.jpg

image quality, well, they're readable.

Good luck,
Jurriaan
-- 
management n.
1. Corporate power elites distinguished primarily by their distance from
actual productive work and their chronic failure to manage (see also suit).
Spoken derisively, as in "Management decided that ...". 2. Mythically, a
vast bureaucracy responsible for all the world's minor irritations.
Hackers' satirical public notices are often signed `The Mgt'; this derives
from the "Illuminatus" novels (see the Bibliography in Appendix C).
Debian (Unstable) GNU/Linux 2.6.23-rc1-mm2 2x2010 bogomips load 0.43
the Jack Vance Integral Edition: http://www.integralarchive.org

  parent reply	other threads:[~2007-09-02  6:19 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070831215822.26e1432b.akpm@linux-foundation.org>
     [not found] ` <20070901155353.8a09db69.kamezawa.hiroyu@jp.fujitsu.com>
2007-09-01  6:58   ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-01  8:54     ` 2.6.23-rc4-mm1 Herbert Xu
2007-09-01 11:55     ` 2.6.23-rc4-mm1 Kamalesh Babulal
     [not found] ` <20070901181352.GA4156@amd64.of.nowhere>
2007-09-01 19:05   ` 2.6.23-rc4-mm1 OOPS in forcedeth? Jeff Garzik
2007-09-02  0:54     ` Satyam Sharma
2007-09-02  5:36       ` thunder7
2007-09-02  6:19       ` thunder7 [this message]
2007-09-02  9:55         ` Satyam Sharma
2007-09-14  3:51           ` Andrew James Wade
2007-09-17 13:57             ` Dhaval Giani
2007-09-17 14:07               ` Denis V. Lunev
2007-09-17 21:00                 ` Vlad Yasevich
2007-09-17 23:56                 ` Satyam Sharma
2007-09-01 22:06 ` 2.6.23-rc4-mm1 "no CRC" MODPOST warnings Satyam Sharma
2007-09-01 22:40   ` Adrian Bunk
2007-09-01 23:15   ` Sam Ravnborg
2007-09-02  1:30 ` [PATCH -mm] net/sched/sch_cbq.c: Shut up uninitialized variable warning Satyam Sharma
2007-09-02 11:36   ` Patrick McHardy
2007-09-02  2:36 ` 2.6.23-rc4-mm1: unpingable box and NULL dereference at tcp_rto_min() Alexey Dobriyan
2007-09-02  5:02   ` Satyam Sharma
2007-09-02 20:52   ` Andrew Morton
2007-09-02 21:19     ` Alexey Dobriyan
2007-09-02  9:14 ` 2.6.23-rc4-mm1 net bitops compile error Adrian Bunk
2007-09-04 17:53   ` Jiri Slaby
2007-09-02 11:25 ` [-mm patch] IPV6 must select XFRM Adrian Bunk
2007-09-03 10:43   ` Masahide NAKAMURA
2007-09-06 10:01     ` net-26.24 broken with XFRM off Noriaki TAKAMIYA
2007-09-04 17:54 ` 2.6.23-rc4-mm1 Zach Carter
2007-09-04 21:36   ` 2.6.23-rc4-mm1 Stephen Hemminger
2007-09-09 20:25 ` [-mm patch] really unexport do_softirq Adrian Bunk
2007-09-12 13:14   ` David Miller
2007-09-09 20:25 ` [-mm patch] unexport raise_softirq_irqoff Adrian Bunk
2007-09-09 20:41   ` Christoph Hellwig
2007-09-12 13:15     ` David Miller
2007-09-09 20:25 ` [-mm patch] net/sctp/socket.c: make 3 variables static Adrian Bunk
2007-09-10 14:05   ` [Lksctp-developers] " Neil Horman
2007-09-12 13:18   ` David Miller
2007-09-09 20:25 ` [-mm patch] make tcp_splice_data_recv() static Adrian Bunk
2007-09-12 13:21   ` David Miller
2007-09-12 17:44     ` Jens Axboe
2007-09-06  7:25 net-26.24 broken with XFRM off Divy Le Ray
2007-09-06  8:13 ` Eric Dumazet
2007-09-06  9:50   ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070902061900.GA5595@amd64.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=satyam@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).