xfs
[Top] [All Lists]

[Bug 195] New: xfs_fsr results in oops

To: xfs-master@xxxxxxxxxxx
Subject: [Bug 195] New: xfs_fsr results in oops
From: bugzilla-daemon@xxxxxxxxxxx
Date: Sat, 16 Nov 2002 01:31:59 -0800
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=195

           Summary: xfs_fsr results in oops
           Product: Linux XFS
           Version: Current
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: High
         Component: XFS kernel code
        AssignedTo: xfs-master@xxxxxxxxxxx
        ReportedBy: c.pascoe@xxxxxxxxxxxxxx


If this is a userspace bug, what version of the package are you using:

xfs_fsr, CVS 15/Oct/2002


What kernel are you using:

2.4.20-rc1


Where did the XFS code come from?  (CVS, Linus, your distribution, etc):

SGI XFS CVS-2002-11-08_06:00_UTC with ACLs, quota, no debug enabled


Description of Problem:

Running xfs_fsr results in an invalid paging request, similar to below.

Unable to handle kernel paging request at virtual address 028b080c
f89a94a5
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<f89a94a5>]    Tainted: P
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010283
eax: 028b0804   ebx: 00020002   ecx: 00080000   edx: df11bd7c
esi: f6b96220   edi: f89c31a0   ebp: df11bd80   esp: df11bd68
ds: 0018   es: 0018   ss: 0018
Process xfs_fsr (pid: 2142, stackpage=df11b000)
Stack: 000000a3 00000001 f89c31a0 f4b04320 df11bd7c 00000001 df11be0c f89aa25e
       f6b96240 00000000 00000000 00080000 df11bdec 00020002 00000000 00000001
       f89c31a0 c012a6bf f78fde40 401e2000 00000000 00000080 00000000 00000000
Call Trace:    [<f89c31a0>] [<f89aa25e>] [<f89c31a0>] [<c012a6bf>] [<c012e979>]
  [<f89c31a0>] [<c01308ff>] [<c012e5b0>] [<c012e78f>] [<f89afce2>] [<f89afcfa>]
  [<f89aa6ae>] [<f89aa5f8>] [<c013d070>] [<c0108f6b>]
Code: 8b 48 08 89 4d f4 52 8b 4d 18 51 53 8b 55 14 52 8b 55 0c 8b


>>EIP; f89a94a5 <[xfs]map_blocks+25/9c>   <=====

>>eax; 028b0804 Before first symbol
>>ebx; 00020002 Before first symbol
>>ecx; 00080000 Before first symbol
>>edx; df11bd7c <_end+1edb7d9c/3849c020>
>>esi; f6b96220 <_end+36832240/3849c020>
>>edi; f89c31a0 <[xfs]linvfs_aops+0/40>
>>ebp; df11bd80 <_end+1edb7da0/3849c020>
>>esp; df11bd68 <_end+1edb7d88/3849c020>

Trace; f89c31a0 <[xfs]linvfs_aops+0/40>
Trace; f89aa25e <[xfs]linvfs_direct_IO+e6/2fc>
Trace; f89c31a0 <[xfs]linvfs_aops+0/40>
Trace; c012a6bf <get_user_pages+117/1c0>
Trace; c012e979 <generic_file_direct_IO+1dd/254>
Trace; f89c31a0 <[xfs]linvfs_aops+0/40>
Trace; c01308ff <generic_file_write_nolock+673/720>
Trace; c012e5b0 <do_generic_file_read+22c/418>
Trace; c012e78f <do_generic_file_read+40b/418>
Trace; f89afce2 <[xfs]xfs_write+2aa/4d0>
Trace; f89afcfa <[xfs]xfs_write+2c2/4d0>
Trace; f89aa6ae <[xfs]linvfs_write+b6/e8>
Trace; f89aa5f8 <[xfs]linvfs_write+0/e8>
Trace; c013d070 <sys_write+a0/11c>
Trace; c0108f6b <system_call+33/38>

Code;  f89a94a5 <[xfs]map_blocks+25/9c>
00000000 <_EIP>:
Code;  f89a94a5 <[xfs]map_blocks+25/9c>   <=====
   0:   8b 48 08                  mov    0x8(%eax),%ecx   <=====
Code;  f89a94a8 <[xfs]map_blocks+28/9c>
   3:   89 4d f4                  mov    %ecx,0xfffffff4(%ebp)
Code;  f89a94ab <[xfs]map_blocks+2b/9c>
   6:   52                        push   %edx
Code;  f89a94ac <[xfs]map_blocks+2c/9c>
   7:   8b 4d 18                  mov    0x18(%ebp),%ecx
Code;  f89a94af <[xfs]map_blocks+2f/9c>
   a:   51                        push   %ecx
Code;  f89a94b0 <[xfs]map_blocks+30/9c>
   b:   53                        push   %ebx
Code;  f89a94b1 <[xfs]map_blocks+31/9c>
   c:   8b 55 14                  mov    0x14(%ebp),%edx
Code;  f89a94b4 <[xfs]map_blocks+34/9c>
   f:   52                        push   %edx
Code;  f89a94b5 <[xfs]map_blocks+35/9c>
  10:   8b 55 0c                  mov    0xc(%ebp),%edx
Code;  f89a94b8 <[xfs]map_blocks+38/9c>
  13:   8b 00                     mov    (%eax),%eax


3 warnings and 7 errors issued.  Results may not be reliable.

NB, this still occurs if I do not load the module that taints the kernel (a Dell
ESM module).

How Reproducible:

Every time (well, 3 times - this system is in production).


Steps to Reproduce:

1. Run xfs_fsr

Additional Information:

The system which xfs_fsr was run on exports two large filesystems (500GB w/v1
log, 250GB w/v2 log) via samba and NFS.  LVM is not installed on this system. 
It is Dual CPU SMP w/ megaraid hardware RAID.  The Oops also occurs on another
system without a v2 filesystem and with different SCSI hardware.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>
  • [Bug 195] New: xfs_fsr results in oops, bugzilla-daemon <=