From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 151631] "Synchronizing SCSI cache" fails during(and delays) reboot/shutdown
Date: Sat, 06 Aug 2016 19:20:57 +0000 [thread overview]
Message-ID: <bug-151631-11613-HPdGeKXB47@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-151631-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=151631
icanrealizeum <icanrealizeum+bugzillakernelorg@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |icanrealizeum+bugzillakerne
| |lorg@gmail.com
--- Comment #1 from icanrealizeum <icanrealizeum+bugzillakernelorg@gmail.com> ---
I tried one shutdown, and after the above it did shutdown, as expected,
however, on poweron, SSD was not detected by BIOS unless I did one ctrl+alt+del
from POST's attempt to boot from LAN, and this second time it was detected.
This happens usually after I powerdown from button(hold 4 sec) because I
imagine SSD is busy recovering from sudden-power-loss internally, so I can only
conclude that the kernel didn't safely powerdown the SSD(aside from the above
failure to flush cache). (Was definitely ok in 4.7.0-rc6-ga99cde4)
I did however have a debug.sh script in
/usr/lib/systemd/system-shutdown/debug.sh
which did these:
sync && sdparm --command=sync /dev/sda && sleep 1
mount -o remount,ro /
hdparm -F /dev/sda
hdparm -f /dev/sda
sleep 1
So in a way, that ssd cache was supposedly flushed regardless; and it doesn't
seem to me that something else ever tried to remount,rw or do writes after
this.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-08-06 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 17:17 [Bug 151631] New: "Synchronizing SCSI cache" fails during(and delays) reboot/shutdown bugzilla-daemon
2016-08-06 19:20 ` bugzilla-daemon [this message]
2016-08-06 19:57 ` [Bug 151631] " bugzilla-daemon
2016-08-07 0:29 ` bugzilla-daemon
2016-08-07 15:06 ` bugzilla-daemon
2016-08-07 15:06 ` bugzilla-daemon
2016-11-08 8:11 ` bugzilla-daemon
2016-11-10 6:54 ` bugzilla-daemon
2016-12-04 20:22 ` bugzilla-daemon
2016-12-04 20:26 ` bugzilla-daemon
2017-01-17 20:29 ` bugzilla-daemon
2017-01-17 20:56 ` bugzilla-daemon
2024-01-04 11:45 ` bugzilla-daemon
2024-01-22 8:40 ` bugzilla-daemon
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=bug-151631-11613-HPdGeKXB47@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).