Re: ATA mkIII first official patches - please test!

From: Søren Schmidt <sos_at_DeepCore.dk>
Date: Mon, 07 Feb 2005 23:49:33 +0100
Derek Tattersall wrote:
> In order to keep the thread going with a newish problem:
> 
> I cvsup'ed my system yesterday, and before I appled the ata MK III patches
> Feb  6 13:14:50 lorne kernel: ad0: 78167MB <Maxtor 6Y080P0/YAR41BW0> [158816/16/63] at ata0-master UDMA133
> Feb  6 13:14:50 lorne kernel: ad1: 194481MB <Maxtor 6B200P0/BAH41B70> [395136/16/63] at ata0-slave UDMA133
> Feb  6 13:14:50 lorne kernel: acd0: DVDR <Memorex DVD+/-RW True8XI/UWS3> at ata1-master UDMA33
> 
> After applying the patches:
> Feb  6 18:35:56 lorne kernel: ad0: DMA limited to UDMA33, non-ATA66 cable or device
> Feb  6 18:35:56 lorne kernel: ad0: 78167MB <Maxtor 6Y080P0 YAR41BW0> at ata0-master UDMA33
> Feb  6 18:35:56 lorne kernel: ad1: 194481MB <Maxtor 6B200P0 BAH41B70> at ata0-slave UDMA133
> Feb  6 18:35:56 lorne kernel: acd0: CDROM <Memorex DVD+/-RW True8XI/UWS3> at ata1-master UDMA33
> 
> The hardware wasn't changed between the first and second reboots.  Why
> would the patches cause not recognize the cable type?

Because of the ordering of the identify calls the cable detection fails. 
It needs to probe the slave first then the master, but that screws up 
device numbering with newbus. I have it on my list and a couble of 
solutions, just not made up my mind yet...


-- 

-Søren
Received on Mon Feb 07 2005 - 21:49:59 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:27 UTC