Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#51501 - [linux] Kernel 4.8 causes ATA exception Emask 0x0 [...] frozen errors on shutdown
Attached to Project:
Arch Linux
Opened by Razvan Cojocaru (rc) - Saturday, 22 October 2016, 19:10 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 21 January 2017, 05:52 GMT
Opened by Razvan Cojocaru (rc) - Saturday, 22 October 2016, 19:10 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 21 January 2017, 05:52 GMT
|
DetailsOn a Dell Latitude E5440 laptop running an up-to-date Arch Linux, on shutdown I get an ATA exception Emask 0x0 [...] frozen error. Arch Linux is set up as LVM on LUKS, as per the Arch Wiki instructions (maybe this has something to do with it?). There's also something about 0x4 (timeout) in there. The hard drive is a Seagate SSHD. I've ran smartctl on it and it's perfectly healthy.
When I shut it down, it stalls for maybe a minute, then it spits the error out to me too fast to get it completely, then the computer shuts down with the hard drive LED blinking (this is what has attracted my attention). The system is dual-boot with Windows - Windows works fine with no issues on shutdown. I've downgraded the kernel to the latest 4.7 kernel available, and this has solved the issue, so this doesn't appear to be a hardware issue. |
This task depends upon
system SVP1321C5E
cpu@0 processor Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz
scsi@0:0.0.0 /dev/sda disk 256GB SAMSUNG MZHPU256
4.7.x kernels worked fine. Curiously my business laptop (Fujitsu E754) also running zfs on LUKS, eg. almost similar configuration, runs without any issue.
I attached the bootup log showing the ata.1 errors.
In short: upgrading to a kernel >= 4.9.0 solves the problem for me. I tested today using linux-4.9.4-1 from testing.
(On the way to this bug entry I noticed this bug entry (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172) which mentions the CONFIG_HARDENED_USERCOPY kernel config but as it is still defined in 4.9.x I assume it is either a combination of this setting with something else or unrelated.)
Nevertheless it would be nice to know the real cause.