Samsung SSD 840 failed to get NCQ

[JohnShep]

[100700.464034] ata4.00: exception Emask 0x10 SAct 0x1f0000 SErr 0x400100 action 0x6 frozen
[100700.464040] ata4.00: irq_stat 0x08000000, interface fatal error
[100700.464043] ata4: SError: { UnrecovData Handshk }
[100700.464047] ata4.00: failed command: WRITE FPDMA QUEUED
[100700.464053] ata4.00: cmd 61/40:80:00:30:30/00:00:00:00:00/40 tag 16 ncq 32768 out
                         res 40/00:88:c0:30:30/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[100700.464056] ata4.00: status: { DRDY }
[100700.464058] ata4.00: failed command: WRITE FPDMA QUEUED
[100700.464063] ata4.00: cmd 61/40:88:c0:30:30/00:00:00:00:00/40 tag 17 ncq 32768 out
                         res 40/00:88:c0:30:30/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[100700.464066] ata4.00: status: { DRDY }
[100700.464068] ata4.00: failed command: WRITE FPDMA QUEUED
[100700.464073] ata4.00: cmd 61/c0:90:40:31:30/00:00:00:00:00/40 tag 18 ncq 98304 out
                         res 40/00:88:c0:30:30/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[100700.464076] ata4.00: status: { DRDY }
[100700.464078] ata4.00: failed command: WRITE FPDMA QUEUED
[100700.464083] ata4.00: cmd 61/80:98:68:bd:75/00:00:01:00:00/40 tag 19 ncq 65536 out
                         res 40/00:88:c0:30:30/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[100700.464086] ata4.00: status: { DRDY }
[100700.464088] ata4.00: failed command: WRITE FPDMA QUEUED
[100700.464093] ata4.00: cmd 61/40:a0:a8:bf:75/00:00:01:00:00/40 tag 20 ncq 32768 out
                         res 40/00:88:c0:30:30/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[100700.464095] ata4.00: status: { DRDY }
[100700.464099] ata4: hard resetting link
[100700.784026] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[100700.785561] ata4.00: supports DRM functions and may not be fully accessible
[100700.785683] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[100700.786069] ata4.00: supports DRM functions and may not be fully accessible
[100700.786138] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[100700.786237] ata4.00: configured for UDMA/133
[100700.786260] ata4: EH complete

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-22-generic 4.2.0-22.27
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: john 1370 F.... pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
Date: Fri Jan 1 19:52:28 2016
HibernationDevice: RESUME=UUID=dedbb189-ef72-4e7e-911e-047a87675597
InstallationDate: Installed on 2015-12-26 (6 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 enp0s25 no wireless extensions.

 lo no wireless extensions.
MachineType: Acer Aspire X3812
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=UUID=de0ff862-ed19-4927-bb3b-39775930e092 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-22-generic N/A
 linux-backports-modules-4.2.0-22-generic N/A
 linux-firmware 1.149.3
RfKill:

SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2009
dmi.bios.vendor: AMI
dmi.bios.version: P01-A0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: WG43M
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAMI:bvrP01-A0:bd08/16/2009:svnAcer:pnAspireX3812:pvr:rvnAcer:rnWG43M:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Aspire X3812
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[JohnShep (john-boxrec)]

Hi Chris,
I finally updated my bios (after six hours of frustration) and am now
using P01-A1, unfortunately the bug is still there :-(
Should I file a new report or would it be a lot easier for everyone if
I bought a new motherboard ?

[ 67.584037] ata4: limiting SATA link speed to 1.5 Gbps
[ 67.584043] ata4.00: exception Emask 0x10 SAct 0x40000001 SErr 0x0
action 0x6 frozen
[ 67.584047] ata4.00: irq_stat 0x08000000, interface fatal error
[ 67.584050] ata4.00: failed command: READ FPDMA QUEUED
[ 67.584056] ata4.00: cmd 60/78:00:c0:bb:96/00:00:03:00:00/40 tag 0
ncq 61440 in
                        res 40/00:00:c0:bb:96/00:00:03:00:00/40 Emask
0x10 (ATA bus error)
[ 67.584059] ata4.00: status: { DRDY }
[ 67.584062] ata4.00: failed command: READ FPDMA QUEUED
[ 67.584067] ata4.00: cmd 60/20:f0:10:ca:98/00:00:03:00:00/40 tag 30
ncq 16384 in
                        res 40/00:00:c0:bb:96/00:00:03:00:00/40 Emask
0x10 (ATA bus error)
[ 67.584069] ata4.00: status: { DRDY }
[ 67.584073] ata4: hard resetting link
[ 67.904017] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 67.904261] ata4.00: supports DRM functions and may not be fully accessible
[ 67.904392] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 67.904835] ata4.00: supports DRM functions and may not be fully accessible
[ 67.904912] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 67.905029] ata4.00: configured for UDMA/133
[ 67.905044] ata4: EH complete

On 1 January 2016 at 20:36, Christopher M. Penalver
<email address hidden> wrote:
> JohnShep, thank you for reporting this and helping make Ubuntu better.
>
> As per http://us.acer.com/ac/en/US/content/drivers an update to your
> computer's buggy and outdated BIOS is available (P01-A1). If you update
> to this following https://help.ubuntu.com/community/BIOSUpdate does it
> change anything?
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful. As well, you don't
> have to create a new bug report.
>
> Once the BIOS is updated, if the problem is still reproducible:
> 1) Please provide the output of the following terminal command (not perform an apport-collect):
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
> 2) Please make a comment specifically advising on if there was an improvement or not.
> 3) Please mark this report Status Confirmed. If it's not reproducible, please mark this as Invalid.
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-p01-a1
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1530459
>
> Title:
> Samsung SSD 840 failed to get NCQ
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530459/+subscriptions

[penalvch (penalvch)]

JohnShep, at your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]