Hello All , Has anyone else had an occurance of hard lockup using a
Fusion lsi22320 . schema below & partial log output .
+-A-+[ sc933s2 jbod chassis ] With 7-FUJITSU-MAP3147NC
|
+-B-+[ sc933s2 jbod chassis ] With 7-FUJITSU-MAP3147NC
|
+ lsi22320 in pci-64-133 slot
[ system ] a SuperServer 6035B-8R
+ aic7902 on board
|
+-A-+[ internally ] With 2-Compaq/Seagate-18GB-u320 & 2-FUJITSU-MAP3147NC
|
+-B-+[ internally ] With 4-FUJITSU-MAP3147NC
lsi22320 is attached to the sc933s2 on channels A & B ,
cable lengths are ~ 4 feet on both channels .
aic7902 is attached internally thru 'system' , a SuperServer 6035B-8R .
Kernel: Linux 2.6.21-rc4 , With the 'Domain validation loops' patch .
root@(none):~ # ( time bonnie++-1.03a/bonnie++ -u0:0 -d /home -s 524288 ) 2>&1
| tee 512GB-bonnie++-run-ext3-200704181557.log
Using uid:0, gid:0.
Writing with putc()...mptscsih: ioc0: attempting task abort! (sc=d0795800)
sd 4:0:3:0:
command: <4>mptscsih: ioc1: attempting task abort! (sc=d8c28500)
sd 5:0:1:0:
command: Read(10): 28 00 00 1d d1 b9 00 00 08 00
Read(10): 28 00 00 1e 12 b9 00 00 08 00
mptscsih: ioc1: WARNING - TM Handler for type=1: IOC Not operational (0xffffffff)!
sd 1:0:3:0: Attempting to queue an A
<System Hung hard>
You can get the whole log here .
http://www.baby-dragons.com/new-sc933s2-coming-online-to-linux-scsi.log
Any help is greatly appreciated .
JimL
--
+-----------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | 663 Beaumont Blvd | Give me Linux |
| babydr@xxxxxxxxxxxxxxxx | Pacifica, CA. 94044 | only on AXP |
+-----------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
