lkml.org 
[lkml]   [2013]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
Subject[3.8-{rc1,rc2}] ata1.00: failed to get Identify Device Data, Emask 0x1
From
Hi,

I noticed messages like the following in my syslogs with Linux
v3.8-rc1 and v3.8-rc2:

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

In this Samsung ultrabook there exists a small SSD and a 500GiB HDD.
I had no look which of the two is "ata1" or "ata2".
NOTE: With ata2 I do not see the messages.
I haven't checked older Linux-kernel versions.

I followed the thread in [1] a bit and Aaron Lu pointed to the commit
which causes these messages.
Shane wanted to submit a patch [3] which I first didn't found.
But I guess it's the one from [4], building right now...

Hope this helps a bit to narrow down the problem.

Regards,
- Sedat -

[1] https://lkml.org/lkml/2012/10/16/557
[2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=65fe1f0f66a57380229a4ced844188103135f37b
[3] https://lkml.org/lkml/2012/11/16/369
[4] http://git.kernel.org/?p=linux/kernel/git/jgarzik/libata-dev.git;a=patch;h=de90cd71f68e947d3bd6c3f2ef5731ead010a768

P.S.: Excerpts from the quoted commit:

[ drivers/ata/libata-core.c ]
...
+ /* check and mark DevSlp capability */
+ if (ata_id_has_devslp(dev->id))
+ dev->flags |= ATA_DFLAG_DEVSLP;
+
+
+ /* 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);
+ }
+
- EOT -


\
 
 \ /
  Last update: 2013-01-04 17:01    [W:0.059 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site