From: Johannes Maibaum <jmaibaum@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: HD is powered off too early during shutdown/reboot (4.8 regression?)
Date: Thu, 24 Nov 2016 18:24:16 +0100 [thread overview]
Message-ID: <ec2c184d-ca59-eb67-8a3f-2d46c157d400@gmail.com> (raw)
Hi,
this is my first posting on a Linux kernel related list, and I hope that
this is the correct place. If not, I'd be glad if you could point me to
the right place. People on the Arch Linux forums [1] and on the
systemd-devel mailing list [2] suggested to report this issue to the
kernel community.
I try to be as specific as I can, but unfortunately I'm not a low-level
Linux expert.
Since installing kernel 4.8, I have a problem with my MacBook Pro
running Arch Linux on a second HD installed in a HD caddy [1]. The root
and /home file systems are on this HD (/dev/sdb, see below), while /boot
is on the first HD alongside macOS (/dev/sda).
On shutdown/reboot, it seems that the HD (or the caddy?) gets powered
off too early, which is clearly audible ('clank!'). Shortly afterwards,
the following errors appears on screen (transcribed from a photo):
ata2: exception Emask 0x10 SAct 0x0 SErr 0x1990000 action 0xe
frozenbd204ed5c
ata2: irq_stat 0x00400000, PHY RDY changed
ata2: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns }
The machine shuts down or reboots a few seconds later, but I've never
seen the above errors on another kernel before (kernel 4.4 through 4.7
were installed on this machine and all worked OK), so it seems to be a
regression.
Unfortunately, I haven't yet succeeded in gathering more verbose debug
information from late shutdown. I tried to follow the guide in the
systemd docs [4], but the script failed (probably, since the hd is
already gone when the script tries to run). But I will happily try to
provide you with more information if needed.
Here's some more information about my setup:
$ dmesg | grep ata2 | head
[ 2.508533] ata2: SATA max UDMA/133 abar m8192@0xd3484000 port
0xd3484180 irq 26
[ 2.824504] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.825383] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES)
filtered out
[ 2.825543] ata2.00: ATA-8: Hitachi HTS545032B9SA02, PB3AC60W, max
UDMA/133
[ 2.825545] ata2.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 2.826577] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES)
filtered out
[ 2.826745] ata2.00: configured for UDMA/133
$ readlink /dev/disk/by-id/*HTS545032B9SA02* | head -n1
../../sdb
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 298,1G 0 disk
├─sdb2 8:18 0 268,1G 0 part /home
└─sdb1 8:17 0 30G 0 part /
sda 8:0 0 931,5G 0 disk
├─sda2 8:2 0 930,7G 0 part
├─sda3 8:3 0 619,9M 0 part
└─sda1 8:1 0 200M 0 part /boot
Best,
Johannes
[1] Here's a link to the HD caddy: https://www.amazon.com/dp/B0090KFOYS
[2] Arch Linux forum thread:
https://bbs.archlinux.org/viewtopic.php?pid=1668277
[3] Systemd-devel thread:
https://lists.freedesktop.org/archives/systemd-devel/2016-November/037882.html
[4] https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
next reply other threads:[~2016-11-24 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 17:24 Johannes Maibaum [this message]
2016-12-06 14:31 ` HD is powered off too early during shutdown/reboot (4.8 regression?) Johannes Maibaum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec2c184d-ca59-eb67-8a3f-2d46c157d400@gmail.com \
--to=jmaibaum@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).