On Sun, Sep 26, 1999 at 01:28:31PM -0700, Matthew Jacob wrote:
> -----------
> Things fixed:
[...]
Ok - works as far as booting - Then i am getting problems with
the raid stuff ... :(
Kernel 2.2.12 + qlogic + raid stuff ... (990824 0.90 2.2.11 patches +
raidutils (0.90 990724) syscall 140 patch)
--------------------------------------
qpti0: IRQ 53 SCSI ID 7 (Firmware v1.31.32)(Firmware 1.21 95/05/18) [Fast Wide, using
single ended interface]
qpti1: IRQ 53 SCSI ID 7 (Firmware v1.31.32)(Firmware 1.21 95/05/18) [Fast Wide, using
single ended interface]
qpti2: IRQ 53 SCSI ID 7 (Firmware v1.31.32)(Firmware 1.21 95/05/18) [Fast Wide, using
single ended interface]
QPTI: Total of 3 PTI Qlogic/ISP hosts found, 3 actually in use.
scsi0 : Sparc ESP100A-FAST
scsi1 : PTI Qlogic,ISP SBUS SCSI irq 53 regs at fd015000 PROM node ffd42428
scsi2 : PTI Qlogic,ISP SBUS SCSI irq 53 regs at fd016000 PROM node ffd4624c
scsi3 : PTI Qlogic,ISP SBUS SCSI irq 53 regs at fd017000 PROM node ffd4a070
--------------------------------------
The oops happens when
booting
autodetecting a raid (and start to rebuild)
raidstop /dev/md0
editing /etc/raidtab
mkraid /dev/md0 (with the non email representable parm)
Oops ... (After listing raid config verbose)
/proc/mdstat
Personalities : [raid5]
read_ahead 1024 sectors
md0 : active raid5 sdh1[5] sdg1[4] sdf1[3] sde1[2] sdd1[1]
sdc1[0] 20923840 blocks level 5, 32k chunk, algorithm 2 [6/6]
[UUUUUU] resync=0% finish=242243.4min
No disk activity - raid5syncd crashed ?
raidstop /dev/md0
interrupting MD-thread pid 0
<hang>
ps auxw | grep raid
root 130 0.0 0.0 0 0 ? SW< 00:14 0:00 (raid5d)
root 155 0.0 0.1 1224 396 S0 D 00:15 0:00 raidstop /dev/md0
--------------------------------------
WARNING: This version of ksymoops is obsolete.
WARNING: The current version can be obtained from ftp://ftp.ocs.com.au/pub/ksymoops
Options used: -V (default)
-o /lib/modules/2.2.12-flo/ (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-m /boot/System.map-2.2.12-flo (specified)
-c 1 (default)
Warning: mismatch on symbol ___f____xchg32 , ksyms_base says f01126d8, System.map
says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f___irq_itoa , ksyms_base says f00133d4, System.map
says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_disable_irq , ksyms_base says f001315c, System.map
says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_enable_irq , ksyms_base says f0013220, System.map
says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_mmu_get_scsi_one , ksyms_base says f0022990,
System.map says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_mmu_get_scsi_sgl , ksyms_base says f0022a0c,
System.map says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_mmu_lockarea , ksyms_base says f0022ce0, System.map
says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_mmu_release_scsi_one , ksyms_base says f0022ae0,
System.map says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_mmu_release_scsi_sgl , ksyms_base says f0022ae8,
System.map says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_mmu_unlockarea , ksyms_base says f0022ce8,
System.map says f0167cb4. Ignoring ksyms_base entry
Warning: mismatch on symbol ___f_mmu_v2p , ksyms_base says f0022548, System.map says
f0167cb4. Ignoring ksyms_base entry
Unable to handle kernel NULL pointer dereference<1>tsk->mm->context = ffffffff
tsk->mm->pgd = f0005000
\|/ ____ \|/
"@'/ ,. \`@"
/_| \__/ |_\
\__U_/
raid5syncd(131): Oops
PSR: 044010c5 PC: fe313e00 NPC: fe313e04 Y: 00000000
g0: 00000000 g1: 04401fe5 g2: 00000004 g3: fc652c00 g4: fe313bac g5: 0000008c g6:
fc4fc000 g7: 0000008c
o0: 00000000 o1: 00000002 o2: fc42a900 o3: 00000026 o4: 00000001 o5: f0171ec3 sp:
fc4fdc58 o7: fe313df0
l0: 00000900 l1: fc451800 l2: 00000021 l3: 00000000 l4: 00000002 l5: 00000000 l6:
00000000 l7: 0000000a
i0: fc652c00 i1: 00000000 i2: 00000002 i3: f037c9e8 i4: f0176af0 i5: 00000000 fp:
fc4fdcc0 i7: fe314804
Caller[fe314804]
Caller[fe315a2c]
Caller[f00c5b9c]
Caller[f00c0e48]
Caller[f00c6bd8]
Caller[fe315bfc]
Caller[f00c5cfc]
Caller[f0014a58]
Caller[f00c5e84]
Caller[f01722c0]
Instruction DUMP: a1342010 a4100008 90100019 <e6066024> 7c77f278 92102048 90100019
92100010 173f8c4f
Warning: trailing garbage ignored on Code: line
Text: 'Instruction DUMP: a1342010 a4100008 90100019 <e6066024> 7c77f278 92102048
90100019 92100010 173f8c4f '
Garbage: ' '
>>PC: fe313e00 <raid5_build_block+34/a0>
>>O7: fe313df0 <raid5_build_block+24/a0>
>>I7: fe314804 <add_stripe_bh+68/128>
Trace: fe314804 <add_stripe_bh+68/128>
Trace: fe315a2c <raid5_make_request+2a4/2bc>
Trace: f00c5b9c <md_make_request+e4/10c>
Trace: f00c0e48 <ll_rw_block+218/2f0>
Trace: f00c6bd8 <md_do_sync+3e4/b8c>
Trace: fe315bfc <raid5syncd+40/b4>
Trace: f00c5cfc <md_thread+120/21c>
Trace: f0014a58 <kernel_thread+2c/88>
Trace: f00c5e84 <md_register_thread+60/a8>
Trace: f01722c0 <log_buf+0/4000>
Code: fe313df4 <raid5_build_block+28/a0> 0000000000000000 <_PC>:
Code: fe313df4 <raid5_build_block+28/a0> 0: a1 34 20 10 srl %l0,
0x10, %l0
Code: fe313df8 <raid5_build_block+2c/a0> 4: a4 10 00 08 mov %o0, %l2
Code: fe313dfc <raid5_build_block+30/a0> 8: 90 10 00 19 mov %i1, %o0
Code: fe313e00 <raid5_build_block+34/a0> c: e6 06 60 24 ld [ %i1 +
0x24 ], %l3 <===
Code: fe313e04 <raid5_build_block+38/a0> 10: 7c 77 f2 78 call
f01107e4 <__bzero+0/144>
Code: fe313e08 <raid5_build_block+3c/a0> 14: 92 10 20 48 mov 0x48, %o1
Code: fe313e0c <raid5_build_block+40/a0> 18: 90 10 00 19 mov %i1, %o0
Code: fe313e10 <raid5_build_block+44/a0> 1c: 92 10 00 10 mov %l0, %o1
Code: fe313e14 <raid5_build_block+48/a0> 20: 17 3f 8c 4f sethi
%hi(0xfe313c00), %o3
14 warnings issued. Results may not be reliable.
--------------------------------------------
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-5241-470566
... The failure can be random; however, when it does occur, it is
catastrophic and is repeatable ... Cisco Field Notice
