linux-kernel - Re: 2.6.24-rc2: Reported regressions from 2.6.23 (updated)

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: <3d08dbff0711130609u462619c9n5f87e9c0e55eb46@mail.gmail.com>
Date:	Tue, 13 Nov 2007 15:09:04 +0100
From:	"Thomas Lindroth" <thomas.lindroth@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.24-rc2: Reported regressions from 2.6.23 (updated)

> > > [PATCH] pata_amd/pata_via: de-couple programming of PIO/MWDMA and UDMA timings
> > >
> > > * Don't program UDMA timings when programming PIO or MWDMA modes.
> > >
> > >   This has also a nice side-effect of fixing regression added by commit
> > >   681c80b5d96076f447e8101ac4325c82d8dce508 ("libata: correct handling of
> > >   SRST reset sequences") (->set_piomode method for PIO0 is called before
> > >   ->cable_detect method which checks UDMA timings to get the cable type).
> >
> > I'm not sure this helps as if the ACPI _GTF method is looking at the
> > flags and stuff but it has to be worth a try.
> >
> >
> > Works for me as a 2.6.24 band aid
>
> I'm looking at that "Untested, please don't merge until it is confirmed to
> fix the problem." comment..
>
> Thomas, can you please give it a try, let us know?
>
> Thanks
>

I can confirm that the patch "pata_amd/pata_via: de-couple programming
of PIO/MWDMA and UDMA timings" does fix my issue "pata_amd fails to
detect 80-pin wire".
-
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/