From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266599AbUBLVGY (ORCPT ); Thu, 12 Feb 2004 16:06:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266600AbUBLVGX (ORCPT ); Thu, 12 Feb 2004 16:06:23 -0500 Received: from intra.cyclades.com ([64.186.161.6]:13755 "EHLO intra.cyclades.com") by vger.kernel.org with ESMTP id S266599AbUBLVFI (ORCPT ); Thu, 12 Feb 2004 16:05:08 -0500 Date: Thu, 12 Feb 2004 18:49:26 -0200 (BRST) From: Marcelo Tosatti X-X-Sender: marcelo@logos.cnet To: Wakko Warner Cc: linux-kernel@vger.kernel.org Subject: Re: knfsd oops 2.4.24 In-Reply-To: <20040210210432.A2880@animx.eu.org> Message-ID: References: <20040210210432.A2880@animx.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cyclades-MailScanner-Information: Please contact the ISP for more information X-Cyclades-MailScanner: Found to be clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 10 Feb 2004, Wakko Warner wrote: > I was burning a cd over nfs (glad I have burnproof =) when knfsd crashed on > me. 2 kjourneld oopses followed (sorry, wasn't able to capture). > > Disk is SCSI on an AHA2940UW controller. I'm considering going to 2.6.x, > but I'm simply not convinced of 2.6's stability and I've noticed a few knfsd > problems there as well (minor problems). > > I'm sure I'll beable to capture the other oopses. > > The machine is an ms6163 pIII700 384mb ram (FYI, this used to be in another > machine running 2.6 and did not actually have these problems). > > Any more information required will be given. > > Keep me in CC > > ksymoops 2.4.5 on i686 2.4.24. Options used > -v /vegeta/usr/src/linux/nail/2.4.24/vmlinux (specified) > -k /proc/ksyms (default) > -l /proc/modules (default) > -o /lib/modules/2.4.24/ (default) > -m /boot/System.map-2.4.24 (default) > > Unable to handle kernel paging request at virtual address fc3e2f3a > printing eip: > c0115c6b > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[] Not tainted > EFLAGS: 00010086 > eax: cd9a5948 ebx: fc3e2f3a ecx: 00000001 edx: 00000003 > esi: cd9a5948 edi: 00000003 ebp: d5515d14 esp: d5515cf8 > ds: 0018 es: 0018 ss: 0018 > Process nfsd (pid: 324, stackpage=d5515000) > Stack: cd9a5900 c013b835 00000001 00000286 cd9a5900 00000008 00000000 00001000 > c01924af 00000000 cd9a5900 00000000 d7a9a400 00000030 cd9a5900 00000000 > 00000031 cd9a5900 c013c32c 00000000 cd9a5900 cd9a5900 00000000 00000010 > Call Trace: [] [] [] [] [] > [] [] [] [] [] [] > [] [] [] [] [] [] > [] [] [] [] [] [] > [] [] [] [] > > Code: 8b 13 0f 18 02 39 c3 74 22 8d b6 00 00 00 00 8d bf 00 00 00 > Reading Oops report from the terminal > Unable to handle kernel paging request at virtual address fc3e2f3a > c0115c6b > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[] Not tainted > Using defaults from ksymoops -t elf32-i386 -a i386 > EFLAGS: 00010086 > eax: cd9a5948 ebx: fc3e2f3a ecx: 00000001 edx: 00000003 > esi: cd9a5948 edi: 00000003 ebp: d5515d14 esp: d5515cf8 > ds: 0018 es: 0018 ss: 0018 > Process nfsd (pid: 324, stackpage=d5515000) > Stack: cd9a5900 c013b835 00000001 00000286 cd9a5900 00000008 00000000 00001000 > c01924af 00000000 cd9a5900 00000000 d7a9a400 00000030 cd9a5900 00000000 > 00000031 cd9a5900 c013c32c 00000000 cd9a5900 cd9a5900 00000000 00000010 > Call Trace: [] [] [] [] [] > [] [] [] [] [] [] > [] [] [] [] [] [] > [] [] [] [] [] [] > [] [] [] [] > Code: 8b 13 0f 18 02 39 c3 74 22 8d b6 00 00 00 00 8d bf 00 00 00 > > > >>EIP; c0115c6b <__wake_up+1b/90> <===== > > >>eax; cd9a5948 <_end+d72851c/18582bd4> > >>ebx; fc3e2f3a > >>esi; cd9a5948 <_end+d72851c/18582bd4> > >>ebp; d5515d14 <_end+152988e8/18582bd4> > >>esp; d5515cf8 <_end+152988cc/18582bd4> > > Trace; c013b835 > Trace; c01924af > Trace; c013c32c > Trace; c0131213 > Trace; c012a54d __wake_up() is not called by get_unused_buffer_head(), so this trace looks odd. I hope someone corrects me.