xfs
[Top] [All Lists]

RE: Oops on XFs 2.4.3

To: "'Tad Dolphay'" <tbd@xxxxxxx>
Subject: RE: Oops on XFs 2.4.3
From: "Christian, Chip" <chip_christian@xxxxxx>
Date: Thu, 29 Nov 2001 10:31:43 -0500
Cc: linux-xfs@xxxxxxxxxxx, nfs@xxxxxxxxxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Cool, thanks for the quick response!  Looks to me like it's in /proc.  Any idea 
what the bug is?  No sweat if not...

        -Chip

-----Original Message-----
From: Tad Dolphay [mailto:tbd@xxxxxxx]
Sent: Wednesday, November 28, 2001 17:26
To: chip_christian@xxxxxx
Cc: linux-xfs@xxxxxxxxxxx; nfs@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: Oops on XFs 2.4.3


There were several reports of similar oops on XFS 1.0 and XFS 1.0.1. 
In the cases I know of, the problems went away in 2.4.9+xfs.

Tad
> 
> Greetings,
> 
> I have a customer who is running RedHat 7.1 w/ kernel built from XFS 
> kernel-source-2.4.3-SGI_XFS_1.0.1.i386.rpm as an NFS server.  They got
> the following Oops...  Any guidance?
> 
>       -Chip
> 
> 
> Oct 30 16:34:01 nas2 kernel: Unable to handle kernel NULL pointer dereference 
> at virtual address 00000015
> Oct 30 16:34:01 nas2 kernel: 8014e832
> Oct 30 16:34:01 nas2 kernel: Oops: 0002
> Oct 30 16:34:01 nas2 kernel: CPU:    0
> Oct 30 16:34:01 nas2 kernel: EIP:    0010:[proc_delete_inode+50/80]
> Oct 30 16:34:01 nas2 kernel: EIP:    0010:[<8014e832>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> Oct 30 16:34:01 nas2 kernel: EFLAGS: 00010206
> Oct 30 16:34:01 nas2 kernel: eax: 00000005   ebx: b4f864a0   ecx: 00000020   
> edx: a080e000
> Oct 30 16:34:01 nas2 kernel: esi: 803016a0   edi: b4f864a0   ebp: a14bcae0   
> esp: a572df34
> Oct 30 16:34:01 nas2 kernel: ds: 0018   es: 0018   ss: 0018
> Oct 30 16:34:01 nas2 kernel: Process ps (pid: 15910, stackpage=a572d000)
> Oct 30 16:34:01 nas2 kernel: Stack: 80147b25 b4f864a0 81044010 802ff0ec 
> 00000246 a14bcae0 a14bcae0 b4f864a0
> Oct 30 16:34:01 nas2 kernel:        801450f6 b4f864a0 8d799000 8014f2ef 
> 00000000 00000000 b88b2380 827dc5a0
> Oct 30 16:34:01 nas2 kernel:        80132b14 a14bcae0 b88b2380 b88b2380 
> 00000000 7ffffaf8 801319ed b88b2380
> Oct 30 16:34:01 nas2 kernel: Call Trace: [iput_free+181/336] [dput+246/368] 
> [proc_info_read+143/256] [fput+116/208] [filp_close+141/160]
> Oct 30 16:34:01 nas2 kernel: Call Trace: [<80147b25>] [<801450f6>] 
> [<8014f2ef>] [<80132b14>] [<801319ed>]
> Oct 30 16:34:01 nas2 kernel:    [<80131a5b>] [<80106e5b>] [<8010002b>]
> Oct 30 16:34:01 nas2 kernel: Code: f0 ff 48 10 8b 42 24 83 48 14 08 52 e8 1d 
> ff ff ff 5a c3 8d
> 
> >>EIP; 8014e832 <proc_delete_inode+32/50>   <=====
> Trace; 80147b25 <iput_free+b5/150>
> Trace; 801450f6 <dput+f6/170>
> Trace; 8014f2ef <proc_info_read+8f/100>
> Trace; 80132b14 <fput+74/d0>
> Trace; 801319ed <filp_close+8d/a0>
> Trace; 80131a5b <sys_close+5b/70>
> Trace; 80106e5b <system_call+33/38>
> Trace; 8010002b <startup_32+2b/cb>
> Code;  8014e832 <proc_delete_inode+32/50>
> 00000000 <_EIP>:
> Code;  8014e832 <proc_delete_inode+32/50>   <=====
>    0:   f0 ff 48 10               lock decl 0x10(%eax)   <=====
> Code;  8014e836 <proc_delete_inode+36/50>
>    4:   8b 42 24                  mov    0x24(%edx),%eax
> Code;  8014e839 <proc_delete_inode+39/50>
>    7:   83 48 14 08               orl    $0x8,0x14(%eax)
> Code;  8014e83d <proc_delete_inode+3d/50>
>    b:   52                        push   %edx
> Code;  8014e83e <proc_delete_inode+3e/50>
>    c:   e8 1d ff ff ff            call   ffffff2e <_EIP+0xffffff2e> 8014e760 
> <de_put+0/a0>
> Code;  8014e843 <proc_delete_inode+43/50>
>   11:   5a                        pop    %edx
> Code;  8014e844 <proc_delete_inode+44/50>
>   12:   c3                        ret
> Code;  8014e845 <proc_delete_inode+45/50>
>   13:   8d 00                     lea    (%eax),%eax
> 


<Prev in Thread] Current Thread [Next in Thread>