linux-kernel - Re: pata_it821x completely broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 4 Jul 2008 21:22:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ondrej Zary <linux@...nbow-software.org>
Cc:	alan@...hat.com, LKML <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org
Subject: Re: pata_it821x completely broken

> When I don't have any RAID array created, both drives are detected but it 
> appears to work only in MWDMA2 mode:

The speed is meaningless in hardware RAID mode. Its also btw usually
faster (except for some cases of RAID1 with high PCI bus utilisation like
video capture boxes) in non RAID mode ;)

> ata3: PATA max MWDMA2 cmd 0x6800 ctl 0x6c00 bmdma 0x7800 irq 11
> ata4: PATA max MWDMA2 cmd 0x7000 ctl 0x7400 bmdma 0x7808 irq 11

I'll have a poke at that, see if I can make it lie more meaningfully

> ata4.00: configured for DMA

as it does here.

> Also I get some errors about HPA when rebooting but haven't captured them yet. 

IT821x does not support the HPA in 'raid' mode, only in non RAID mode so
it would complain about the HPA.


> But the more interesting thing is that once I create a RAID1 array (and run 
> background rebuild), the driver does not work anymore:

Ok that is a bug I've not met. What firmware revision is this and does it
work after the rebuild is done ?

> 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

It seems to have decided to be indefinitely busy from that.

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