Hello,
There's a weird behavior we are experiencing with the Marvell
6081 controller, which I though you might have also experienced
or might find interesting.
Basically, the problem involves sporadic device disconnection
during driver load time and sometimes during continuous use. It
was seen both with sata_mv and the driver provided by Marvell
(version 3.6.1), so I have a reason to believe it's an hardware
problem (to which we can find good software-based workarounds,
hopefully).
The system seen below has 2 Marvell 6081 controllers harboring
a total of 14 hard-drives.
Once in every a few hundreds-or-so insmods of sata_mv the
controller "misses" one of the drives, as seen below:
Mar 31 10:41:10 14.10.240.6 kernel: ata10: dev 0 ATA-7, max UDMA/133, 976773168 sectors: LBA48
Mar 31 10:41:10 14.10.240.6 kernel: ata10: dev 0 configured for UDMA/133
Mar 31 10:41:10 14.10.240.6 kernel: scsi9 : sata_mv
Mar 31 10:41:11 14.10.240.6 kernel: ata11: dev 0 ATA-7, max UDMA/133, 976773168 sectors: LBA48
Mar 31 10:41:11 14.10.240.6 kernel: ata11: dev 0 configured for UDMA/133
Mar 31 10:41:11 14.10.240.6 kernel: scsi10 : sata_mv
Mar 31 10:41:12 14.10.240.6 kernel: ata12: no device found (phy stat 00000000)
Mar 31 10:41:12 14.10.240.6 kernel: ata12: no device found (phy stat 00000101)
Mar 31 10:41:12 14.10.240.6 kernel: ATA: abnormal status 0x7F on port 0xFFFFC200106A811C
Mar 31 10:41:12 14.10.240.6 kernel: ata12: dev 0 failed to IDENTIFY (I/O error)
Mar 31 10:41:12 14.10.240.6 kernel: ATA: abnormal status 0x7F on port 0xFFFFC200106A811C
Mar 31 10:41:12 14.10.240.6 kernel: ata12: dev 0 failed to IDENTIFY (I/O error)
Mar 31 10:41:12 14.10.240.6 kernel: ATA: abnormal status 0x7F on port 0xFFFFC200106A811C
Mar 31 10:41:12 14.10.240.6 kernel: ata12: dev 0 failed to IDENTIFY (I/O error)
Mar 31 10:41:12 14.10.240.6 kernel: scsi11 : sata_mv
Mar 31 10:41:13 14.10.240.6 kernel: ata13: dev 0 ATA-7, max UDMA/133, 976773168 sectors: LBA48
Mar 31 10:41:13 14.10.240.6 kernel: ata13: dev 0 configured for UDMA/133
Mar 31 10:41:13 14.10.240.6 kernel: scsi12 : sata_mv
Mar 31 10:41:14 14.10.240.6 kernel: ata14: dev 0 ATA-7, max UDMA/133, 976773168 sectors: LBA48
Mar 31 10:41:14 14.10.240.6 kernel: ata14: dev 0 configured for UDMA/133
Mar 31 10:41:14 14.10.240.6 kernel: scsi13 : sata_mv
Rest assured that drive is there, we haven't pulled it out.
On Linux 2.4.27 with the Marvell driver (3.6.1), using the
add-single-device command on the (now depricated) /proc/scsi/scsi
interface, we managed to bring the drive back to life...
The drives are the 500GB from Maxtor. This problem has occured
with drives from a different manufacturer.
Mar 31 10:41:09 14.10.240.6 kernel: Vendor: ATA Model: Maxtor 7H500F0 Rev: HA43
Mar 31 10:41:09 14.10.240.6 kernel: Type: Direct-Access ANSI SCSI revision: 05
--
Dan Aloni, Linux specialist
XIV LTD, http://www.xivstorage.com
[email protected], [email protected], [email protected], [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
