Re: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-11-16 Thread Jeff Garzik
On 11/16/2012 11:02 AM, Huang, Shane wrote: I tried word 78 bit 5(Hardware Feature Control) which does not work, it is 0 on my HDD sample with log 30h page 08h and DevSlp supported. Seems that word 78 bit 5 is only the sufficient condition, not the essential condition. Do you guys have suggestio

RE: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-11-16 Thread Huang, Shane
> I tried word 78 bit 5(Hardware Feature Control) which does not work, > it is 0 on my HDD sample with log 30h page 08h and DevSlp supported. > > Seems that word 78 bit 5 is only the sufficient condition, not the > essential condition. Do you guys have suggestion? Eventually I received the confir

RE: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-10-18 Thread Huang, Shane
> Agree. If NCQ does not imply support of this log page, we should > definitely refine the check condition used here. > > I suppose Shane will take care of this, but if he doesn't, I'll do that > at a later time. I tried word 78 bit 5(Hardware Feature Control) which does not work, it is 0 on my H

Re: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-10-16 Thread Aaron Lu
On 10/17/2012 12:50 PM, Robert Hancock wrote: > On 10/16/2012 07:38 PM, Aaron Lu wrote: >> On 10/16/2012 11:18 PM, Borislav Petkov wrote: >>> On Tue, Oct 16, 2012 at 03:58:24PM +0100, Alan Cox wrote: Can you check whether 3.6 works on them. I know 3.6 is horribly broken on several brands

Re: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-10-16 Thread Robert Hancock
On 10/16/2012 07:38 PM, Aaron Lu wrote: On 10/16/2012 11:18 PM, Borislav Petkov wrote: On Tue, Oct 16, 2012 at 03:58:24PM +0100, Alan Cox wrote: Can you check whether 3.6 works on them. I know 3.6 is horribly broken on several brands of AHCI controller (Jmicron for example). Dunno where Jeff is

Re: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-10-16 Thread Aaron Lu
On 10/16/2012 11:18 PM, Borislav Petkov wrote: > On Tue, Oct 16, 2012 at 03:58:24PM +0100, Alan Cox wrote: >> Can you check whether 3.6 works on them. I know 3.6 is horribly broken >> on several brands of AHCI controller (Jmicron for example). Dunno >> where Jeff is on fixing the regressions ? > >

Re: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-10-16 Thread Borislav Petkov
On Tue, Oct 16, 2012 at 03:58:24PM +0100, Alan Cox wrote: > Can you check whether 3.6 works on them. I know 3.6 is horribly broken > on several brands of AHCI controller (Jmicron for example). Dunno > where Jeff is on fixing the regressions ? If by "works" you mean I don't see the message there, t

Re: ata4.00: failed to get Identify Device Data, Emask 0x1

2012-10-16 Thread Alan Cox
On Tue, 16 Oct 2012 16:49:32 +0200 Borislav Petkov wrote: > Hi all, > > a bunch of my boxes started showing this on 3.7-rc1 (and maybe earlier): > > [4.667077] ata4.00: failed to get Identify Device Data, Emask 0x1 > [ 4.675071] ata4.00: failed to get Identify Devi

ata4.00: failed to get Identify Device Data, Emask 0x1

2012-10-16 Thread Borislav Petkov
Hi all, a bunch of my boxes started showing this on 3.7-rc1 (and maybe earlier): [4.667077] ata4.00: failed to get Identify Device Data, Emask 0x1 [4.675071] ata4.00: failed to get Identify Device Data, Emask 0x1 Another one: [3.325371] ata4.00: failed to get Identify Device Data