xfs
[Top] [All Lists]

XFS internal error: RH 2.4.20-20.9 & XFS 1.3.0 & others

To: linux-xfs@xxxxxxxxxxx
Subject: XFS internal error: RH 2.4.20-20.9 & XFS 1.3.0 & others
From: Axel Thimm <Axel.Thimm@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 26 Aug 2003 19:43:14 +0300
Cc: radus@xxxxxxxx
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
Hi,

I got a bug report by radus using the atrpms kernels on Debian (the
kernels are for RedHat and he takes the kernel-source rpm and uses it
for building on Debian with some workarounds for gcc 3.3).

The kernel in question has
o Red Hat 2.4.20-20.9 base sources
o XFS 1.3.0 merged in
o Updated lvm to 1.0.7

also some further patches that should not overlap with XFS:

o i2c/lm_sensors 2.8.0
o v4l2 api
o 3ware driver updates.

Here is the user's oops:
> Aug 26 06:25:14 stark kernel: Filesystem "ide0(3,2)": XFS internal error
> xfs_iformat(6) at line 544 of file xfs_inode.c.  Caller 0xc01b8472
> Aug 26 06:25:14 stark kernel: c09dfd0c c01b6f11 c02d37d0 00000001 c1ad4c00
> c02d3790 00000220 c01b8472
> Aug 26 06:25:14 stark kernel:        c3c95a16 00000008 c1ad4c00 99a49e15
> 159e4e82 00000000 00000000 00000000
> Aug 26 06:25:14 stark kernel:        00000000 c1ad4c00 c671ac00 c01b8472
> c671ac00 c3c95a00 00000001 00000000
> 
> Trace; c01b6f11 <xfs_iformat+121/640>
> Trace; c01b8472 <xfs_iread+1c2/210>
> Trace; c01b8472 <xfs_iread+1c2/210>
> Trace; c01b5ac6 <xfs_iget_core+b6/4a0>
> Trace; c01b5ff3 <xfs_iget+143/190>
> Trace; c01cfb64 <xfs_dir_lookup_int+b4/130>
> Trace; c01d54b5 <xfs_lookup+65/90>
> Trace; c01e3ff7 <linvfs_lookup+67/b0>
> Trace; c014f857 <real_lookup+c7/f0>
> Trace; c014fda9 <link_path_walk+3f9/6e0>
> Trace; c0150249 <path_lookup+39/40>
> Trace; c01504d9 <__user_walk+49/60>
> Trace; c014bf5f <vfs_lstat+1f/60>
> Trace; c014c59b <sys_lstat64+1b/40>
> Trace; c0140001 <shmem_file_write+41/3a0>
> Trace; c010939f <system_call+33/38>
> Trace; c01b6f11 <xfs_iformat+121/640>
> Trace; c01b8472 <xfs_iread+1c2/210>
> Trace; c01b8472 <xfs_iread+1c2/210>
> Trace; c01b5ac6 <xfs_iget_core+b6/4a0>
> Trace; c01b5ff3 <xfs_iget+143/190>
> Trace; c01cfb64 <xfs_dir_lookup_int+b4/130>
> Trace; c01d54b5 <xfs_lookup+65/90>
> Trace; c01e3ff7 <linvfs_lookup+67/b0>
> Trace; c014f857 <real_lookup+c7/f0>
> Trace; c014fda9 <link_path_walk+3f9/6e0>
> Trace; c0150249 <path_lookup+39/40>
> Trace; c01504d9 <__user_walk+49/60>
> Trace; c014bf5f <vfs_lstat+1f/60>
> Trace; c014eaf2 <pipe_write+1b2/2b0>
> Trace; c014c59b <sys_lstat64+1b/40>
> Trace; c0144859 <sys_write+e9/130>
> Trace; c010939f <system_call+33/38>

Any idea what caused the oops?
Thanks!
-- 
Axel.Thimm@xxxxxxxxxxxxxxxxxxx
 

Attachment: pgpCIzp2IIQvF.pgp
Description: PGP signature

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