linux-kernel - Re: 2.6.29-rc libata sff 32bit PIO regression

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]

Message-ID: <20090121214746.2b15d1de@lxorguk.ukuu.org.uk>
Date:	Wed, 21 Jan 2009 21:47:46 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	Hugh Dickins <hugh@...itas.com>, Jeff Garzik <jgarzik@...hat.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>, linux-ide@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29-rc libata sff 32bit PIO regression

On Wed, 21 Jan 2009 21:11:05 +0100
Mikael Pettersson <mikpe@...uu.se> wrote:

> Hugh Dickins writes:
>  > I've a Dell Precision 670 here (four-year-old EM64T Xeon with ata_piix)
>  > which doesn't like your commit 871af1210f13966ab911ed2166e4ab2ce775b99d
>  > libata: Add 32bit PIO support.  Full dmesg (and .config) attached, but
>  > here's an extract showing the start of the error messages on ata2:

Cool - so we need two different 32bit PIO methods - at least according to
the docs for the AMD we should use entirely 32bit I/O there. Fun fun


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/