From: Chris Pascoe Subject: Re: nfsd oops - exiting?? Date: Fri, 17 May 2002 16:31:09 +1000 (EST) Sender: nfs-admin@lists.sourceforge.net Message-ID: References: <00f301c1faec$fe0dd5f0$47426682@csee.uq.edu.au> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from gum.csee.uq.edu.au ([130.102.66.1]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 178bGp-0005PH-00 for ; Thu, 16 May 2002 23:31:19 -0700 Received: from luma.csee.uq.edu.au (luma.csee.uq.edu.au [130.102.66.14]) by gum.csee.uq.edu.au (8.11.6/8.11.6) with ESMTP id g4H6VA722103 for ; Fri, 17 May 2002 16:31:10 +1000 (EST) Received: from mango.csee.uq.edu.au (mango.csee.uq.edu.au [130.102.66.4]) by luma.csee.uq.edu.au (8.11.6/8.11.6) with ESMTP id g4H6V9n14166 for ; Fri, 17 May 2002 16:31:09 +1000 (EST) To: nfs@lists.sourceforge.net In-Reply-To: <00f301c1faec$fe0dd5f0$47426682@csee.uq.edu.au> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: And another oops with the same backtrace today - nobody has any ideas/suggestions where to look? Chris On Tue, 14 May 2002, Chris Pascoe wrote: > Hi, > > After about 5 days of uptime on my SMP NFS server running 2.4.18+(CVS) XFS I > have experienced the following oops. At least once before I have seen other > oopses that have occurred containing do_exit and sys_wait4, but I can't > obviously see how this code path was taken. It goes without saying that I > can't reproduce the crash on demand.. > > Has anyone else seen similar traces and/or can suggest how the nfsd code got > to this point so I can attempt to investigate further? > > The kernel is tainted by the Intel e1000 driver in the oops that follows. > > Thanks, > Chris > > --8<-- oops starts > Unable to handle kernel NULL pointer dereference at virtual address 00000286 > c011be54 > *pde = 00000000 > Oops: 0002 > CPU: 0 > EIP: 0010:[] Tainted: P > Using defaults from ksymoops -t elf32-i386 -a i386 > EFLAGS: 00010286 > eax: 00000000 ebx: f71ec000 ecx: 00000001 edx: 00000286 > esi: 00000000 edi: 00000286 ebp: f71edf94 esp: f71edf84 > ds: 0018 es: 0018 ss: 0018 > Process nfsd (pid: 889, stackpage=f71ed000) > Stack: f71ec000 00000000 00000000 f71ec000 f71edfac c011c6d6 00000286 > f71ec000 > f7245ed4 f741ce00 f71edfb8 c011c84c 00000000 f7245edc c010722b > 00000100 > c200b800 0000001f f7245ed4 f741ce00 f7245edc 00000001 f7440018 > f71b0018 > Call Trace: [] [] [] [] > Code: f0 ff 0f 0f 94 c0 84 c0 0f 84 9e 00 00 00 c7 45 fc 00 00 00 > > >>EIP; c011be54 <===== > Trace; c011c6d6 > Trace; c011c84c > Trace; c010722b > Trace; c010588e > Code; c011be54 > 00000000 <_EIP>: > Code; c011be54 <===== > 0: f0 ff 0f lock decl (%edi) <===== > Code; c011be57 > 3: 0f 94 c0 sete %al > Code; c011be5a > 6: 84 c0 test %al,%al > Code; c011be5c > 8: 0f 84 9e 00 00 00 je ac <_EIP+0xac> c011bf00 > > Code; c011be62 > e: c7 45 fc 00 00 00 00 movl $0x0,0xfffffffc(%ebp) _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs