Re: pata_it821x completely broken

On Friday 04 July 2008 23:46:36 Alan Cox wrote:
It complains pretty loudly - something like 3 screens (with framebuffer
at 1024x768) of errors like this:

Interesting. I need to have a poke at that - it used to work fine but
I've not tested the 821x recently and the HPA code has changed. It
shouldn't be issuing HPA commands in the first place. Added to the TODO
list. The HPA is supposed to be cleared by the driver setup code but if
the newer firmware is faking it then I wonder what it does if we allow
the command through.

It's BIOS v1.7.1.94, firmware 02093030. Haven't tried waiting for the
rebuild to complete. It will probably take ages for 400GB drives. I'll
try with some much smaller drives (something <1GB).

Thanks

Tested with various drives connected as slaves (in addidion to the two 400GB
Samsungs). Seems like any drive that can't do UDMA fails (looks like MWDMA is
broken). The controller BIOS creates the array fine but it doesn't work in
Linux. In smart mode, it fails to identify (this is probably the same problem
as with any other RAID array):

pata_it821x: controller in smart mode.
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKC] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:00:12.0 to 64
scsi2 : pata_it821x
scsi3 : pata_it821x
ata3: PATA max MWDMA2 cmd 0x6800 ctl 0x6c00 bmdma 0x7800 irq 11
ata4: PATA max MWDMA2 cmd 0x7000 ctl 0x7400 bmdma 0x7808 irq 11
ata3.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.00: ATA-7: SAMSUNG HD400LD, WQ100-15, max UDMA/100
ata3.00: 781422768 sectors, multi 0: LBA48
ata3.00: configured for DMA
ata4.00: ATA-7: SAMSUNG HD400LD, WQ100-15, max UDMA/100
ata4.00: 781422768 sectors, multi 0: LBA48
ata4.00: configured for DMA

When I force the pass-through mode, it oopses (haven't captured it yet as it's
too long). Forcing pass-through mode works fine with UDMA-capable drives:

pata_it821x: forcing bypass mode.
pata_it821x: controller in pass through mode.
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKC] -> GSI 11 (level, low) ->
IRQ 11
scsi2 : pata_it821x
scsi3 : pata_it821x
ata3: PATA max UDMA/133 cmd 0x6800 ctl 0x6c00 bmdma 0x7800 irq 11
ata4: PATA max UDMA/133 cmd 0x7000 ctl 0x7400 bmdma 0x7808 irq 11
ata3.00: ATA-7: SAMSUNG HD400LD, WQ100-15, max UDMA/100
ata3.00: 781422768 sectors, multi 0: LBA48
ata3.01: ATA-4: ST36531A, 3.11, max UDMA/33
ata3.01: 12706470 sectors, multi 0: LBA
ata3.00: configured for UDMA/100
ata3.01: configured for UDMA/33
ata4.00: ATA-7: SAMSUNG HD400LD, WQ100-15, max UDMA/100
ata4.00: 781422768 sectors, multi 0: LBA48
ata4.01: ATA-4: QUANTUM FIREBALL EL2.5A, A08.1100, max UDMA/33
ata4.01: 5008500 sectors, multi 0: LBA
ata4.00: limited to UDMA/33 due to 40-wire cable
ata4.00: configured for UDMA/33
ata4.01: configured for UDMA/33


Then I created RAID 1 from the Seagate and Quantum drives. No matter if the
rebuild process is running or not, the result is the same - the drives that
form RAID aren't accessible, the other drives work:

pata_it821x: controller in smart mode.
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKC] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:00:12.0 to 64
scsi2 : pata_it821x
scsi3 : pata_it821x
ata3: PATA max MWDMA2 cmd 0x6800 ctl 0x6c00 bmdma 0x7800 irq 11
ata4: PATA max MWDMA2 cmd 0x7000 ctl 0x7400 bmdma 0x7808 irq 11
ata3.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.00: ATA-7: SAMSUNG HD400LD, WQ100-15, max UDMA/100
ata3.00: 781422768 sectors, multi 0: LBA48
ata3.00: configured for DMA
ata4.00: ATA-7: SAMSUNG HD400LD, WQ100-15, max UDMA/100
ata4.00: 781422768 sectors, multi 0: LBA48
ata4.00: configured for DMA


(the secondary slave is missing - interesting)


--
Ondrej Zary
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • sata_mv hotplug flaky?
    ... Pulled a couple drives and re-added. ... Dec 11 16:51:10 saga kernel: ata8: failed to recover some devices, retrying in 5 secs ...
    (Linux-Kernel)
  • Re: ata1: soft resetting port
    ... ata1.00: configured for UDMA/33 ... ata3: failed to recover some devices, retrying in 5 secs ...
    (Linux-Kernel)
  • Issues with large drives going back to PIO
    ... drives, as I have run tests on them and stuck them in another FreeBSD ... of 198898911-198899166 retrying ... UDMA ICRC error cmd=write fsbn 198898911 of 198898911-198899166 ...
    (freebsd-hackers)
  • Re: Hmm...
    ... US Government could recover the data from the drives. ... you worry about destroying it to ...
    (comp.security.misc)
  • Re: USB 1 to USB 2 corruption
    ... The problem is the slave drive,it has become corrupt to the point that it cannot be read.This has occured several times in the past with different comp.I have a theory how it got corrupt....It is not a virus or malware,I know this for a fact,my system is clean.My theory involves the USB Interface.Especially with going from USB 1 to USB 2 or vice versa.I have a external box that I have the drive in,it is a USB 2 devise,and as long as I keep it attached to a comp.that has USB 2,no problems.The problems start to occur when the external is attached to a comp. ... wants to do a check disk operation at startup,then finally the drive itself cannot be read.This does not happen over few hours, rather a few months.This last time it happened,the drive was fine till I plugged it up to another comp.When I realized that it was a USB 1 port I unplugged it,that was 7 weeks ago,now as of this morning the drive cannot be read.I almost have the 1T drive full,I really don't want to loose 3 years of work.Oh I also might add that the drive cannot be formatted by any XP means,or by any tools that I had,the last time this happened I had to send the drive off to be formatted.Even my computer guru had a very hard time formatting the drive.As I mentioned both drives are sata...but it has also happened with IDE drives.Like I said before main drive still boots normally .I know this is a bit long winded, but maybe something here will help.This is not only limited to XP,it has also happened on '98,me.,2000,and also vista. ... To recover the data, you need enough space to put the recovered files. ...
    (microsoft.public.windowsxp.general)