ext3 related oops in 2.4.{18,20} on sparc

ext3 related oops in 2.4.{18,20} on sparc

[Noah L. Meyerhans]

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

I consistantly get a kernel oops in 2.4.18 and 2.4.20 on my SPARC Ultra
1 when copying lots of data between two filesystems on the same disk.
The latest command I've been using is: "cd /mnt && rsync -var /usr/ ."
The command runs for a while, copying data, but then, before it
completes, rsync dies with the following error:
rsync: error writing 25 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
rsync: error writing 69 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)

and an oops is generated.  The machine still seems to run OK, though I
can't unmount the destination filesystem.

The oops message is attached, having been decoded with ksymoops.  I
don't have any reason to believe there are hardware issues with this
machine.  It has been very reliable for quite some time, and there are
no signs of problems up to the very instant that the oops is generated,
which seems to happen at a different point in the copying process each
time.

Thanks for any help you can offer.  Let me know if you need more info.

noah

-- 
 _______________________________________________________
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: ext3 related oops in 2.4.{18,20} on sparc

[Noah L. Meyerhans]

[-- Attachment #1.1: Type: text/plain, Size: 236 bytes --]

Ahh!  I forgot to attach the oops!  It is attached here.  Sorry!

noah

-- 
 _______________________________________________________
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html 

[-- Attachment #1.2: oops.decoded --]
[-- Type: text/plain, Size: 5060 bytes --]

ksymoops 2.4.5 on sparc64 2.4.20.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.20/ (default)
     -m /boot/System.map-2.4.20 (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.

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Jan  6 22:16:02 mantis kernel: Unable to handle kernel NULL pointer dereference
Jan  6 22:16:02 mantis kernel: tsk->{mm,active_mm}->context = 0000000000000534
Jan  6 22:16:02 mantis kernel: tsk->{mm,active_mm}->pgd = fffff800207c0000
Jan  6 22:16:02 mantis kernel:               \|/ ____ \|/
Jan  6 22:16:02 mantis kernel:               "@'/ .. \`@"
Jan  6 22:16:02 mantis kernel:               /_| \__/ |_\
Jan  6 22:16:02 mantis kernel:                  \__U_/
Jan  6 22:16:02 mantis kernel: rsync(320): Oops
Jan  6 22:16:02 mantis kernel: TSTATE: 0000004411009605 TPC: 000000000048c93c TNPC: 000000000048c940 Y: 00000000    Not tainted
Using defaults from ksymoops -t elf32-sparc -a sparc
Jan  6 22:16:02 mantis kernel: g0: fffff800022d9760 g1: 000000000048c760 g2: 0000000000000002 g3: 0000000000000000
Jan  6 22:16:02 mantis kernel: g4: fffff80000000000 g5: 0000000000000002 g6: fffff80002494000 g7: 0000000000000002
Jan  6 22:16:02 mantis kernel: o0: fffff80002494000 o1: 0000000000000000 o2: 0000000000ff0000 o3: 000000000000ff00
Jan  6 22:16:02 mantis kernel: o4: 0000000000000001 o5: 0000000000000001 sp: fffff800024972d1 ret_pc: 000000000048c920
Jan  6 22:16:02 mantis kernel: l0: fffff8000206cc20 l1: fffff800019b0060 l2: 00000000006b0800 l3: fffff800101f103c
Jan  6 22:16:02 mantis kernel: l4: 0000000000000010 l5: 0000000000000000 l6: 0000000000000000 l7: 0000000000000000
Jan  6 22:16:02 mantis kernel: i0: fffffffffffffff3 i1: fffff8000206cc20 i2: 000000000060cdb8 i3: 000000000048c900
Jan  6 22:16:02 mantis kernel: i4: 0000000000000048 i5: 00000000700e9428 i6: fffff800024973a1 i7: 0000000000469a6c
Jan  6 22:16:02 mantis kernel: Caller[0000000000469a6c]
Jan  6 22:16:02 mantis kernel: Caller[0000000000469d50]
Jan  6 22:16:02 mantis kernel: Caller[000000000045cb3c]
Jan  6 22:16:02 mantis kernel: Caller[000000000042ba30]
Jan  6 22:16:02 mantis kernel: Caller[00000000004107f4]
Jan  6 22:16:02 mantis kernel: Caller[0000000070136090]
Jan  6 22:16:02 mantis kernel: Instruction DUMP: 94102000  15003fc0  d25fa7e7 <d6024000> 1300003f  a12ae018  92126300  920ac009  940ac00a 


>>PC;  0048c93c <ext3_lookup+3c/c0>   <=====

>>g0; fffff800022d9760 <END_OF_CODE+fffff80001bed820/????>
>>g1; 0048c760 <ext3_find_entry+1a0/340>
>>g4; fffff80000000000 <END_OF_CODE+fffff7ffff9140c0/????>
>>g6; fffff80002494000 <END_OF_CODE+fffff80001da80c0/????>
>>o0; fffff80002494000 <END_OF_CODE+fffff80001da80c0/????>
>>o2; 00ff0000 <END_OF_CODE+9040c0/????>
>>o3; 0000ff00 Before first symbol
>>sp; fffff800024972d1 <END_OF_CODE+fffff80001dab391/????>
>>ret_pc; 0048c920 <ext3_lookup+20/c0>
>>l0; fffff8000206cc20 <END_OF_CODE+fffff80001980ce0/????>
>>l1; fffff800019b0060 <END_OF_CODE+fffff800012c4120/????>
>>l2; 006b0800 <cdev_hashtable+3c8/400>
>>l3; fffff800101f103c <END_OF_CODE+fffff8000fb050fc/????>
>>i0; fffffffffffffff3 <END_OF_CODE+ffffffffff9140b3/????>
>>i1; fffff8000206cc20 <END_OF_CODE+fffff80001980ce0/????>
>>i2; 0060cdb8 <ext3_dir_inode_operations+0/a0>
>>i3; 0048c900 <ext3_lookup+0/c0>
>>i5; 700e9428 <END_OF_CODE+6f9fd4e8/????>
>>i6; fffff800024973a1 <END_OF_CODE+fffff80001dab461/????>
>>i7; 00469a6c <lookup_hash+8c/c0>

Trace; 00469a6c <lookup_hash+8c/c0>
Trace; 00469d50 <open_namei+b0/640>
Trace; 0045cb3c <filp_open+3c/80>
Trace; 0042ba30 <sparc32_open+50/100>
Trace; 004107f4 <linux_sparc_syscall32+34/40>
Trace; 70136090 <END_OF_CODE+6fa4a150/????>

Code;  0048c930 <ext3_lookup+30/c0>
00000000 <_PC>:
Code;  0048c930 <ext3_lookup+30/c0>
   0:   94 10 20 00       clr  %o2
Code;  0048c934 <ext3_lookup+34/c0>
   4:   15 00 3f c0       sethi  %hi(0xff0000), %o2
Code;  0048c938 <ext3_lookup+38/c0>
   8:   d2 5f a7 e7       unknown
Code;  0048c93c <ext3_lookup+3c/c0>   <=====
   c:   d6 02 40 00       ld  [ %o1 ], %o3   <=====
Code;  0048c940 <ext3_lookup+40/c0>
  10:   13 00 00 3f       sethi  %hi(0xfc00), %o1
Code;  0048c944 <ext3_lookup+44/c0>
  14:   a1 2a e0 18       sll  %o3, 0x18, %l0
Code;  0048c948 <ext3_lookup+48/c0>
  18:   92 12 63 00       or  %o1, 0x300, %o1
Code;  0048c94c <ext3_lookup+4c/c0>
  1c:   92 0a c0 09       and  %o3, %o1, %o1
Code;  0048c950 <ext3_lookup+50/c0>
  20:   94 0a c0 0a       and  %o3, %o2, %o2


2 warnings issued.  Results may not be reliable.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]