From: Aaron Lu <aaron.lu@intel.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Borislav Petkov <bp@amd64.org>, Shane Huang <shane.huang@amd.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: ata4.00: failed to get Identify Device Data, Emask 0x1
Date: Wed, 17 Oct 2012 14:55:45 +0800 [thread overview]
Message-ID: <507E5671.6070504@intel.com> (raw)
In-Reply-To: <507E392E.2010305@gmail.com>
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 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, then yes, it does.
>>> Logs say the message started appearing on Oct 4th after me building
>>> Linus master after the merge window started.
>>>
>>> Ok, let me test 3.6.2 just in case ...<tests>... yes, no error message
>>> there.
>>
>> This is brought by commit: 65fe1f0f66a57380229a4ced844188103135f37b,
>> ahci: implement aggressive SATA device sleep support.
>>
>> Shane, got time to take a look? This debug message made people
>> uncomfortable :-)
>
> I don't have whatever version of ATA command set defines this command,
> but surely there's some identify bit which lists whether this log page
> is supported. Right now checking for it is only conditional on NCQ support.
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.
Thanks,
Aaron
next prev parent reply other threads:[~2012-10-17 6:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:49 ata4.00: failed to get Identify Device Data, Emask 0x1 Borislav Petkov
2012-10-16 14:58 ` Alan Cox
2012-10-16 15:18 ` Borislav Petkov
2012-10-17 1:38 ` Aaron Lu
2012-10-17 4:50 ` Robert Hancock
2012-10-17 6:55 ` Aaron Lu [this message]
2012-10-18 9:11 ` Huang, Shane
2012-11-16 16:02 ` Huang, Shane
2012-11-16 17:44 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=507E5671.6070504@intel.com \
--to=aaron.lu@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bp@amd64.org \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shane.huang@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).