From: Borislav Petkov <bp@amd64.org>
To: linux-ide@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: ata4.00: failed to get Identify Device Data, Emask 0x1
Date: Tue, 16 Oct 2012 16:49:32 +0200 [thread overview]
Message-ID: <20121016144932.GA24044@aftab.osrc.amd.com> (raw)
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, Emask 0x1
[ 3.488602] ata4.00: failed to get Identify Device Data, Emask 0x1
This last one is a laptop which suspends/resumes so this message happens
each time the driver gets initialized.
[ 1.389734] ata1.00: failed to get Identify Device Data, Emask 0x1
[ 1.395031] ata1.00: failed to get Identify Device Data, Emask 0x1
[16825.339587] ata1.00: failed to get Identify Device Data, Emask 0x1
[16825.345835] ata1.00: failed to get Identify Device Data, Emask 0x1
[16842.294983] ata1.00: failed to get Identify Device Data, Emask 0x1
[16842.300513] ata1.00: failed to get Identify Device Data, Emask 0x1
[23628.820487] ata1.00: failed to get Identify Device Data, Emask 0x1
[23628.825556] ata1.00: failed to get Identify Device Data, Emask 0x1
[23661.555111] ata1.00: failed to get Identify Device Data, Emask 0x1
[23661.560745] ata1.00: failed to get Identify Device Data, Emask 0x1
Grepping points to:
/* Obtain SATA Settings page from Identify Device Data Log,
* which contains DevSlp timing variables etc.
* Exclude old devices with ata_id_has_ncq()
*/
if (ata_id_has_ncq(dev->id)) {
err_mask = ata_read_log_page(dev,
ATA_LOG_SATA_ID_DEV_DATA,
ATA_LOG_SATA_SETTINGS,
dev->sata_settings,
1);
if (err_mask)
ata_dev_dbg(dev,
"failed to get Identify Device Data, Emask 0x%x\n",
err_mask);
}
in ata_dev_configure().
Judging by the logs, it must've came in during this merge window:
Oct 4 11:08:13 kepek kernel: [ 4.670357] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 11:08:13 kepek kernel: [ 4.678833] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 11:29:23 kepek kernel: [ 4.690456] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 11:29:23 kepek kernel: [ 4.698473] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 11:54:20 kepek kernel: [ 4.706777] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 11:54:20 kepek kernel: [ 4.715194] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 14:30:17 kepek kernel: [ 4.666199] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 14:30:17 kepek kernel: [ 4.674742] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 15:30:17 kepek kernel: [ 4.686204] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 4 15:30:17 kepek kernel: [ 4.694194] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 10 13:09:40 kepek kernel: [ 4.670245] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 10 13:09:40 kepek kernel: [ 4.678429] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 10 15:28:56 kepek kernel: [ 4.658456] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 10 15:28:56 kepek kernel: [ 4.666485] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 12 10:38:17 kepek kernel: [ 4.694542] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 12 10:38:17 kepek kernel: [ 4.702561] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 16 14:30:26 kepek kernel: [ 4.667077] ata4.00: failed to get Identify Device Data, Emask 0x1
Oct 16 14:30:26 kepek kernel: [ 4.675071] ata4.00: failed to get Identify Device Data, Emask 0x1
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next reply other threads:[~2012-10-16 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:49 Borislav Petkov [this message]
2012-10-16 14:58 ` ata4.00: failed to get Identify Device Data, Emask 0x1 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
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=20121016144932.GA24044@aftab.osrc.amd.com \
--to=bp@amd64.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).