Error from aic7xxx
tmuller at agora.rdrop.com
tmuller at agora.rdrop.com
Mon Aug 9 02:03:50 PDT 1999
Hello,
I'm not sure that I'm subscribed to this list anylonger, so please cc: me
if you reply to this message.
I've recently installed a WDE 4360 UW drive into my system. After a low
level format of the drive, media verification, a reboot, installation of
a couple paritions, I found the following errors during bootup that
stream by:
--------------dmesg------------
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
SCSI host 0 abort (pid 44) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
(scsi0:0:3:0) Synchronous at 20.0 Mbyte/sec, offset 8.
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
Have seen Data Phase. Length=255, NumSGs=1.
sg[0] - Addr 0x7fe96e0 : Length 255
scsi : aborting command due to timeout : pid 45, scsi0, channel 0, id 3, lun 0 Read Capacity 00 00 00 00 00 00 00 00 00
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 8515173 [4157 MB] [4.2 GB]
eth0: Intel EtherExpress Pro 10/100 at 0xfce0, 00:A0:C9:61:15:A6, IRQ 19.
Board assembly 000000-000, Physical connectors present: RJ45
Primary interface chip unknown-11 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x49caa8d6).
Receiver lock-up workaround activated.
Partition check:
sda: sda1 sda2 < sda5 >
sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 >
sdc: sdc1 sdc2 < sdc5 >
sdd: sdd1 < sdd5 sdd6 >
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 44k freed
Adding Swap: 128484k swap-space (priority -1)
Adding Swap: 265036k swap-space (priority -2)
--------------------dmesg---------------
As you can see, the partitions show up and the drive seems to function normally.
My concern is that something is wrong and I don't want to take chances with the
drive if this is a serious problem.
Any ideas or suggestions?
--
Thanks,
Troy
----------------------------------------------------------------
email: tmuller at agora.rdrop.com
PGP 5.0 key: hkp://pgp.ai.mit.edu
helpful suggestion:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
----------------------------------------------------------------
To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
More information about the aic7xxx
mailing list