From: Ondrej Zary <linux@rainbow-software.org>
To: alan@redhat.com
Cc: LKML <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: pata_it821x completely broken
Date: Fri, 4 Jul 2008 21:53:54 +0200 [thread overview]
Message-ID: <200807042153.56644.linux@rainbow-software.org> (raw)
Hello,
after a total hard disk failure, I decided to build RAID1 using a cheap card
with it8212 chip and two Samsung HD400LD drives. I thought that the
pata_it821x driver is mature and should work fine (it does not depend on
EXPERIMENTAL). However, it seems to be broken in several ways (in 2.6.25.3).
When I don't have any RAID array created, both drives are detected but it
appears to work only in MWDMA2 mode:
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.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
But in fact, it's running faster:
hdparm --direct -t /dev/sdc
/dev/sdc:
Timing O_DIRECT disk reads: 188 MB in 3.01 seconds = 62.48 MB/sec
Also I get some errors about HPA when rebooting but haven't captured them yet.
But the more interesting thing is that once I create a RAID1 array (and run
background rebuild), the driver does not work anymore:
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 MWDMA2 cmd 0x6800 ctl 0x6c00 bmdma 0x7800 irq 11
ata4: PATA max MWDMA2 cmd 0x7000 ctl 0x7400 bmdma 0x7808 irq 11
ata3.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_masl=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_masl=0x80)
ata3: failed to recover some devices, retrying in 5 secs
ata3.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_masl=0x80)
ata3: failed to recover some devices, retrying in 5 secs
I'm going to start debugging, suggestions are welcome.
--
Ondrej Zary
next reply other threads:[~2008-07-04 19:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 19:53 Ondrej Zary [this message]
2008-07-04 20:22 ` pata_it821x completely broken Alan Cox
2008-07-04 21:39 ` Ondrej Zary
2008-07-04 21:46 ` Alan Cox
2008-07-05 10:41 ` Ondrej Zary
2008-07-05 15:49 ` Alan Cox
2008-07-06 21:03 ` Ondrej Zary
2008-07-06 20:51 ` Alan Cox
2008-07-06 21:46 ` Ondrej Zary
2008-07-06 19:37 ` Alan Cox
2008-07-06 21:50 ` Ondrej Zary
2008-07-06 23:01 ` Alan Cox
2008-07-07 18:07 ` Ondrej Zary
2008-07-10 20:35 ` Ondrej Zary
2008-07-11 18:43 ` Ondrej Zary
2008-07-11 20:14 ` Alan Cox
2008-07-12 21:42 ` Ondrej Zary
2008-07-13 11:47 ` Ondrej Zary
2008-07-13 11:35 ` Alan Cox
2008-07-13 12:10 ` Ondrej Zary
2008-07-13 14:08 ` Alan Cox
2008-07-22 17:59 ` Ondrej Zary
2008-07-22 18:10 ` Alan Cox
2008-07-22 19:16 ` Ondrej Zary
2008-07-22 19:35 ` Rene Herman
2008-07-22 20:39 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200807042153.56644.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=alan@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).