Arch Linux

loneranger

Member

Registered: 2014-01-24

Posts: 6

Possible issues with my SATA3 SAMSUNG SSD drive

While investigating the issue with my SATA3 SSD drive being recognized as SATA2 (for some reason had to change SATA ports to fix it) I noticed the following messages when I run:

$ dmesg | grep ata3.00
[    0.980592] ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    0.980594] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    0.980596] ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    0.980712] ata3.00: supports DRM functions and may not be fully accessible
[    0.980795] ata3.00: failed to get NCQ Send/Recv Log Emask 0x1
[    0.980797] ata3.00: ATA-9: SAMSUNG MZ7PD128HAFV-000H7, XXXXXXX, max UDMA/133
[    0.980798] ata3.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[    0.981070] ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    0.981072] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    0.981073] ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    0.981174] ata3.00: supports DRM functions and may not be fully accessible
[    0.981225] ata3.00: failed to get NCQ Send/Recv Log Emask 0x1
[    0.981227] ata3.00: configured for UDMA/133

My architecture:

$ uname
3.13.8-1-ARCH

My concern is the line where it says that system failed to get NCQ Send/Recv Log Emask 0x1

Is this something I need to be concerned with?

My system is Asrock Extreme4 mb with SAMSUNG MZ7PD128HAFV-000H7 SSD SATA3 drive on Arch Linux OS.

Inxsible

Forum Fellow

From: Chicago

Registered: 2008-06-09

Posts: 9,183

Re: Possible issues with my SATA3 SAMSUNG SSD drive

as per this link the problem might be laptop-mode. http://forums.gentoo.org/viewtopic-p-7479792.html You might want to disable laptop-mode and verify.

And this link has a workaround https://forums.gentoo.org/viewtopic-t-9 … art-0.html

---

Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

loneranger

Member

Registered: 2014-01-24

Posts: 6

Re: Possible issues with my SATA3 SAMSUNG SSD drive

Thank you for the links!

I don't think I have this service installed on my machine...Could it be related to the following error messages I'm getting in .xsession-errors file?

[machine ~]$ cat .xsession-errors
Failed to run gnome-keyring-daemon: Failed to execute child process "gnome-keyring-daemon" (No such file or directory)
** Message: Initializing gksu extension...
** (caja:957): WARNING **: Failed to get the current CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
** (mate-power-manager:983): WARNING **: levels is 0!
(mate-panel:934): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mate-session[909]: WARNING: Child process 934 was already dead.
(caja:957): Caja-MDU-WARNING **: unable to query info: The specified location is not supported
(caja:957): Caja-MDU-WARNING **: unable to query info: The specified location is not supported
(caja:957): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x7fe66c00ad70' has no handler with id '2891'
(caja:957): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x295c260' has no handler with id '4370'

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Possible issues with my SATA3 SAMSUNG SSD drive

loneranger, have you solved the problem?
i got the same and only libata.force=noncq helped.

loneranger

Member

Registered: 2014-01-24

Posts: 6

Re: Possible issues with my SATA3 SAMSUNG SSD drive

Nope, I didn't. After a number of hours of investigation I just downgraded my kernel to 3.11 for now which resolved the problem. I noticed that, starting  with 3.12 this error message appears in the system logs.

volalto

Member

From: Italy

Registered: 2011-07-05

Posts: 10

Re: Possible issues with my SATA3 SAMSUNG SSD drive

I noticed this kernel message too.. and I also experienced several system hangs that could be possibly related to this.

libata.force=noncq seems to solve the crashes, but this problem needs to be better investigated..

Edit:
The crashes were related to some other issue with 3.15.5.

Last edited by volalto (2014-07-23 15:22:42)