Re: SCSI Kernel Problem - BAD

Steven S. Dick (ssd@nevets.oau.org)
Thu, 21 Mar 1996 09:37:51 EST


Well, 1.3.76 didn't fix my scsi timeout problem, but it has
at least made the memory corruption less severe. Also, the data
copy itself feels like it is MUCH faster than it was under 1.3.75.

This is the second crash I've caused this morning with the command:
dd if=/dev/sr6 of=/src/bigfile
It wrote out only 2M before crashing.

I also tried writing bigfile to my IDE drive--it wrote out 40M before
I got bored and killed it...so it at least works better there, although
if this is a race condtion, perhaps it is just less likely to occur
when only one scsi device is active.

In the messages below, 08:02 refers to the device that /src is on.
No filesystem corruption was found by ext2fs on reboot.
It seems to have actually recorded all the messages that appeared
on the screen this time.

Please let me know if there's anything additional I can try
besides just tickling this bug. (I can try to trigger it in
previous kernels as well, if you want.)

Steve
ssd@nevets.oau.org

aha1542_out failed(2): , lun 4
scsi : aborting command due to timeout : pid 23057, scsi0, channel 0, id 4, lun 0 0x0a 03 f8 74 02 00
SCSI host 0 abort (pid 23057) timed out - resetting
SCSI bus is being reset for host 0.
HACC aha1542.c: interrupt received, but no mail.
Sent BUS RESET to scsi host 0
Sending DID_RESET for target 4
last message repeated 7 times
aha1542_intr_handle: Unexpected interrupt
tarstat=2, hastat=0 idlun=90 ccb#=2
aha1542_intr_handle: Unexpected interrupt
tarstat=0, hastat=0 idlun=90 ccb#=3
aha1542_intr_handle: Unexpected interrupt
tarstat=0, hastat=0 idlun=90 ccb#=4
aha1542_intr_handle: Unexpected interrupt
tarstat=0, hastat=0 idlun=90 ccb#=5
aha1542_intr_handle: Unexpected interrupt
tarstat=0, hastat=0 idlun=90 ccb#=6
aha1542_intr_handle: Unexpected interrupt
tarstat=0, hastat=0 idlun=90 ccb#=7
EXT2-fs error (device 08:02): ext2_find_entry: bad entry in directory #40963: rec_len != 0 - offset=0, inode=3187269641, rec_len=24866, name_len=25775
EXT2-fs error (device 08:02): ext2_find_entry: bad entry in directory #40963: rec_len != 0 - offset=0, inode=3187269641, rec_len=24866, name_len=25775
EXT2-fs error (device 08:02): ext2_find_entry: bad entry in directory #2: rec_len != 0 - offset=0, inode=2272027851, rec_len=40245, name_len=62395
attempt to access beyond end of device
08:02: rw=0, want=380811536, limit=1024000
attempt to access beyond end of device
08:02: rw=0, want=753284404, limit=1024000
attempt to access beyond end of device
08:02: rw=0, want=652446697, limit=1024000
attempt to access beyond end of device
08:02: rw=0, want=869881728, limit=1024000
attempt to access beyond end of device
08:02: rw=0, want=1887993227, limit=1024000
attempt to access beyond end of device
08:02: rw=0, want=1549112020, limit=1024000
attempt to access beyond end of device
08:02: rw=0, want=496489794, limit=1024000
[I reset the machine here]