libata error after upgrading to Kernel 4.10.8-1-ARCH

gururise · 2017-04-03 15:30:09

Everything worked fine on my previous 4.9.8 kernel, but after upgrading to 4.10.8-1-ARCH, my machine fails to boot and prints these messages:

ata1.00: exception Emask 0x20 SAct 0x20 SErr 0x0 action 0x6 frozen
ata1.00: irq_stat 0x20000000, host bus error
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/28:28:78:a5:11/00:00:06:00:00/40 tag 5 ncq dma 2048 ...
               res 40/00:20:18:b9:06/00:00:06:00:00/40 Emask 0x20 (host bus error)
ata1.00: status: { DRDY }
ata1.00: revalidation failed {errno=-5}

I've tried adding pci=nomsi to the grub options, but that doesn't help and my machine still fails to boot. The only way I'm able to boot is by disabling NCQ on my SSD using the libata.force=noncq option.

My drive is not failing, and I'm able to boot and use the drive perfectly by using the old kernel or by disabling NCQ on the new kernel. Here is the output of smartctl -a /dev/sda:

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.8-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     OCZ-OCTANE
Serial Number:    OCZ-RR53158TS3V1912S
Firmware Version: 1.13
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS (minor revision not indicated)
Local Time is:    Mon Apr  3 08:14:29 2017 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x1d) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Abort Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x00)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   0) minutes.
Extended self-test routine
recommended polling time: 	 (   0) minutes.

SMART Attributes Data Structure revision number: 18
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0000   007   000   000    Old_age   Offline      -       7
  3 Spin_Up_Time            0x0000   100   100   000    Old_age   Offline      -       0
  4 Start_Stop_Count        0x0000   100   100   000    Old_age   Offline      -       0
  5 Reallocated_Sector_Ct   0x0000   100   100   000    Old_age   Offline      -       0
  9 Power_On_Hours          0x0000   100   100   000    Old_age   Offline      -       0
 12 Power_Cycle_Count       0x0000   100   100   000    Old_age   Offline      -       2441
232 Available_Reservd_Space 0x0000   100   100   000    Old_age   Offline      -       160
233 Media_Wearout_Indicator 0x0000   100   000   000    Old_age   Offline      -       100

SMART Error Log not supported

SMART Self-test Log not supported

Selective Self-tests/Logging not supported

There was a similar bug hitting Samsung SSD's that was fixed a while back; however, this one seems to affect my OCZ Octane drive and disabling MSI does not help.

Something must have changed on the new kernel.... Any suggestions??

Last edited by gururise (2017-04-03 15:31:32)

R00KIE · 2017-04-03 16:23:43

If anything I would try libata.force=noncqtrim or libata.force=noncq first.

I would also try installing linux-lts and see if it works properly, that would at least give you a starting point if you want to bisect the kernel and try to find the commit that breaks things.

Arch Linux

#1 2017-04-03 15:30:09

libata error after upgrading to Kernel 4.10.8-1-ARCH

#2 2017-04-03 16:23:43

Re: libata error after upgrading to Kernel 4.10.8-1-ARCH

Board footer