xfs
[Top] [All Lists]

Kernel oops in 2.4.22-1.2174.nptl_37.rhfc1.atsmp

To: linux-xfs@xxxxxxxxxxx
Subject: Kernel oops in 2.4.22-1.2174.nptl_37.rhfc1.atsmp
From: Kjell Randa <Kjell.Randa@xxxxxxxxxxxx>
Date: Mon, 22 Mar 2004 00:13:30 +0100
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114
Hi,

I have been using XFS for more than two years without any problems, but 
lately I have started to get oops messages during time of heavy I/O 
load. The system survives and seems healty afterwords. This may be 
related to upgrade to the current kernel.

System is a dual P3 866 MHz on av Via board using 4 Western Digital ide 
disks (2x160 Mb + 2x80GB) connect to a IDE PCI controller from HighPoint 
(Rocket133 with a Silicon Image chip SiI680)

The disks are configured in raid1 (software), lvm and filesystems 
formatted with XFS.

System is running Fedore Core1 with kernel downloaded from 
http://atrpms.physik.fu-berlin.de/dist/fc1/

This kernel conains the following patches:
    * base kernel sources: Taken from Fedora Core 1
    * XFS: merged patches found in 1.3.1
    * i2c-2.8.4 and lm_sensors-2.8.4. You should also get the updated 
userland tools and updated kernel modules.
    * Linux Extended Attributes and ACLs 0.8.65.
    * LVM 1.0.7 (courtesy of Komoriya Takeru)
    * v4l2-api (from http://bytesex.org/v4l/)
    * PlanetCCRMA caps patches: capabilities, drm low latency and others.
    * linux-ntfs 2.1.4c
    * bootsplash

kernet is tainted by the Nividia binary driver.

I am not shure if this is a XFS problems or could be related to some 
other patches (lvm), but not beeing a kernel hacker I hope somebody can 
take take look on the ksymoops output and give their opinion.


ksymoops 2.4.5 on i686 2.4.22-1.2174.nptl_37.rhfc1.atsmp.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.22-1.2174.nptl_37.rhfc1.atsmp/ (default)
     -m /boot/System.map-2.4.22-1.2174.nptl_37.rhfc1.atsmp (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Error (expand_objects): cannot stat(/lib/ext3.o) for ext3
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/jbd.o) for jbd
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/raid1.o) for raid1
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/lvm-mod.o) for lvm-mod
ksymoops: No such file or directory
Warning (compare_maps): ksyms_base symbol dmi_broken_R__ver_dmi_broken 
not found in System.map.  Ignoring ksyms_base entry
Warning (map_ksym_to_module): cannot match loaded module ext3 to a 
unique module object.  Trace may not be reliable.
Mar 21 04:07:16 eagle nmbd[1089]:   Got SIGHUP dumping debug info.
Mar 21 04:46:17 eagle kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 00000006
Mar 21 04:46:17 eagle kernel: f0a00b70
Mar 21 04:46:17 eagle kernel: *pde = 00000000
Mar 21 04:46:17 eagle kernel: Oops: 0000
Mar 21 04:46:17 eagle kernel: CPU:    1
Mar 21 04:46:17 eagle kernel: EIP:    0060:[<f0a00b70>]    Tainted: P
Using defaults from ksymoops -t elf32-i386 -a i386
Mar 21 04:46:17 eagle kernel: EFLAGS: 00010256
Mar 21 04:46:17 eagle kernel: eax: 00000000   ebx: 00000002   ecx: 
c9325dbc   edx: ffffffff
Mar 21 04:46:17 eagle kernel: esi: ec557900   edi: 00000000   ebp: 
00000000   esp: c9325d84
Mar 21 04:46:17 eagle kernel: ds: 0068   es: 0068   ss: 0068
Mar 21 04:46:17 eagle kernel: Process f-prot (pid: 28833, 
stackpage=c9325000)
Mar 21 04:46:17 eagle kernel: Stack: df460b14 00000000 00000000 00001000 
00000001 c9325dc0 c9325dbc d2a01380
Mar 21 04:46:17 eagle kernel:        ef85b000 00000246 d2a01394 00000002 
ffffffff ffffffff 00000001 ffffffff
Mar 21 04:46:17 eagle kernel:        ffffffff 00000000 00000000 00000000 
00000000 00001000 00000002 ec557900
Mar 21 04:46:17 eagle kernel: Call Trace:   [<f0a00c57>] 
linvfs_get_block [xfs] 0x37 (0xc9325df0)
Mar 21 04:46:17 eagle kernel: [<c0153f26>] block_read_full_page [kernel] 
0x2b6 (0xc9325e0c)
Mar 21 04:46:18 eagle kernel: [<c013e179>] do_generic_file_read [kernel] 
0x239 (0xc9325e70)
Mar 21 04:46:18 eagle kernel: [<f0a00c20>] linvfs_get_block [xfs] 0x0 
(0xc9325e78)
Mar 21 04:46:18 eagle kernel: [<c013e7c0>] file_read_actor [kernel] 0x0 
(0xc9325ea0)
Mar 21 04:46:18 eagle kernel: [<c013e985>] generic_file_new_read 
[kernel] 0xc5 (0xc9325ec0)
Mar 21 04:46:18 eagle kernel: [<c013e7c0>] file_read_actor [kernel] 0x0 
(0xc9325ed0)
Mar 21 04:46:18 eagle kernel: [<c0167b20>] dput [kernel] 0x30 (0xc9325ed8)
Mar 21 04:46:18 eagle kernel: [<c013eaaf>] generic_file_read [kernel] 
0x2f (0xc9325f0c)
Mar 21 04:46:18 eagle kernel: [<f0a06e53>] xfs_read [xfs] 0x133 (0xc9325f24)
Mar 21 04:46:18 eagle kernel: [<f0a015e2>] linvfs_read [xfs] 0x72 
(0xc9325f64)
Mar 21 04:46:18 eagle kernel: [<c01504f7>] sys_read [kernel] 0x97 
(0xc9325f94)
Mar 21 04:46:18 eagle kernel: [<c0109b27>] system_call [kernel] 0x33 
(0xc9325fc0)
Mar 21 04:46:18 eagle kernel: Code: 0f b7 40 06 66 89 46 0c 8b 44 24 7c 
85 c0 74 2e f7 46 18 11


 >>EIP; f0a00b70 <[xfs]linvfs_get_block_core+1c0/270>   <=====

 >>ecx; c9325dbc <_end+8e63944/3034cbe8>
 >>edx; ffffffff <END_OF_CODE+e2013d0/????>
 >>esi; ec557900 <_end+2c095488/3034cbe8>
 >>esp; c9325d84 <_end+8e6390c/3034cbe8>

Trace; f0a00c57 <[xfs]linvfs_get_block+37/40>
Trace; c0153f26 <block_read_full_page+2b6/300>
Trace; c013e179 <do_generic_file_read+239/5a0>
Trace; f0a00c20 <[xfs]linvfs_get_block+0/40>
Trace; c013e7c0 <file_read_actor+0/100>
Trace; c013e985 <generic_file_new_read+c5/1c0>
Trace; c013e7c0 <file_read_actor+0/100>
Trace; c0167b20 <dput+30/1b0>
Trace; c013eaaf <generic_file_read+2f/40>
Trace; f0a06e53 <[xfs]xfs_read+133/2f0>
Trace; f0a015e2 <[xfs]linvfs_read+72/f0>
Trace; c01504f7 <sys_read+97/140>
Trace; c0109b27 <system_call+33/38>

Code;  f0a00b70 <[xfs]linvfs_get_block_core+1c0/270>
00000000 <_EIP>:
Code;  f0a00b70 <[xfs]linvfs_get_block_core+1c0/270>   <=====
   0:   0f b7 40 06               movzwl 0x6(%eax),%eax   <=====
Code;  f0a00b74 <[xfs]linvfs_get_block_core+1c4/270>
   4:   66 89 46 0c               mov    %ax,0xc(%esi)
Code;  f0a00b78 <[xfs]linvfs_get_block_core+1c8/270>
   8:   8b 44 24 7c               mov    0x7c(%esp,1),%eax
Code;  f0a00b7c <[xfs]linvfs_get_block_core+1cc/270>
   c:   85 c0                     test   %eax,%eax
Code;  f0a00b7e <[xfs]linvfs_get_block_core+1ce/270>
   e:   74 2e                     je     3e <_EIP+0x3e>
Code;  f0a00b80 <[xfs]linvfs_get_block_core+1d0/270>
  10:   f7 46 18 11 00 00 00      testl  $0x11,0x18(%esi)


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



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