On Fri, 2005-09-23 at 15:42 -0400, Brett Russ wrote:
> This is my libata compatible low level driver for the Marvell SATA
> family. Currently it runs in DMA mode on a 6081 chip with caveats
> (see below).
>
> The 5xxx series parts are not yet DMA capable in this driver because
> the registers have differences that haven't been accounted for yet.
> Basically, I'm focused on the 6xxx series right now. There are
> numerous improvements in the driver that will affect PIO mode for all
> parts, so it's worth running the new driver for all users.
>
> Caveats...there is an outstanding panic in the scsi layer when hitting
> error conditions. I've also seen a hang, also apparently during error
> conditions. I will reply to this message with details of the panics
> and will cc the scsi list as well. Basically, error handling has a
> bug.
>
> All failures are under active debug but I wanted to get this out for
> review sooner rather than later.
>
> Thank you,
> BR
Hi Brett,
Here are the results of a quick test of the driver patch applied to
2.6.14-rc2. Both tests were performed on a dual Xeon with
hyperthreading enabled. A single Western Digital WD360 raptor drive was
attached to the controller:
MV88SX5081 8-port SATA I PCI-X Controller:
CPU 3: Machine Check Exception: 0000000000000004
CPU 2: Machine Check Exception: 0000000000000004
There are no other messages, and the machine locks up solid.
MV88SX6081 8-port SATA II PCI-X Controller (rev 09):
libata version 1.12 loaded.
sata_mv version 0.19
ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 28 (level, low) -> IRQ 209
sata_mv(0000:03:03.0) 32 slots 8 ports SCSI mode IRQ via MSI
ata1: SATA max UDMA/133 cmd 0x0 ctl 0xF8BA2120 bmdma 0x0 irq 209
ata2: SATA max UDMA/133 cmd 0x0 ctl 0xF8BA4120 bmdma 0x0 irq 209
ata3: SATA max UDMA/133 cmd 0x0 ctl 0xF8BA6120 bmdma 0x0 irq 209
ata4: SATA max UDMA/133 cmd 0x0 ctl 0xF8BA8120 bmdma 0x0 irq 209
ata5: SATA max UDMA/133 cmd 0x0 ctl 0xF8BB2120 bmdma 0x0 irq 209
ata6: SATA max UDMA/133 cmd 0x0 ctl 0xF8BB4120 bmdma 0x0 irq 209
ata7: SATA max UDMA/133 cmd 0x0 ctl 0xF8BB6120 bmdma 0x0 irq 209
ata8: SATA max UDMA/133 cmd 0x0 ctl 0xF8BB8120 bmdma 0x0 irq 209
ata1: no device found (phy stat 00000000)
scsi0 : sata_mv
ata2: no device found (phy stat 00000000)
scsi1 : sata_mv
ata3: no device found (phy stat 00000000)
scsi2 : sata_mv
ata4: no device found (phy stat 00000000)
scsi3 : sata_mv
ATA: abnormal status 0x80 on port 0xF8BB211C
ATA: abnormal status 0x80 on port 0xF8BB211C
ATA: abnormal status 0x80 on port 0xF8BB211C
ATA: abnormal status 0x80 on port 0xF8BB211C
ATA: abnormal status 0x80 on port 0xF8BB211C
ATA: abnormal status 0x80 on port 0xF8BB211C
ata5: PIO error, drv_stat 0x50
ata5: dev 0 cfg 49:0000 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000
88:0000
ata5: no dma/lba
ata5: dev 0 not supported, ignoring
scsi4 : sata_mv
ata6: no device found (phy stat 00000000)
scsi5 : sata_mv
ata7: no device found (phy stat 00000000)
scsi6 : sata_mv
ata8: no device found (phy stat 00000000)
scsi7 : sata_mv
Mike
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |