From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 205107] No HDD spindown/parking on shutdown
Date: Tue, 04 Feb 2020 01:41:00 +0000 [thread overview]
Message-ID: <bug-205107-11633-4628UQGPgW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205107-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205107
--- Comment #16 from Kaur Männamaa (kaurman@outlook.com) ---
Did some additional testing & asked Mark's opinion and here's what we found.
First, I must say that one's ears do not seem to be a trustworthy source of
information. I tested with another drive where accessing SMART data was not a
problem and found that on many occasions the count didn't actually increase
although I would have presumed so judging by what I heard.
Now, as for what is actually going on, it is Mark's view that the kernel is
probably not to blame here. Rather systemd or one of its services acting up,
for example, which is where you started from...
It is worth pointing out, however that Mark found the presence of the bug to be
dependent on whether the drive had been previously mounted. This is something
that differs from your observations, unless I'm mistaken.
True, it appears that you didn't test with a drive that had never been mounted
after connecting but rather with one that you had unmounted. Who knows, maybe
even that can make a difference but that's just speculation by me at the
moment.
Do note, however, what I said about relying on your ears. IF you have based
some of your recent reporting on what you heard instead of checking the actual
count then this is something to consider.
If, on the other hand, you have checked the count and can still confirm that
the bug doesn't care if the drive has been previously mounted or not then you
are probably seeing something similar to what I'm seeing on my system, i.e
shutting down without ever mounting does not seem to make a difference (meaning
the problem is present *sometimes*). Yet, the kernel still seems to do what is
expected (at least according to the basic tests Mark helped to arrange). I.e
the drive does get flagged for start & stop management by the kernel, as it
should.
What I ran into was similar to what is described here:
https://www.toradex.com/community/questions/22373/udisk-unable-to-detach-device-after-unmount.html
In other words, I started the system, connected the drive and tried to unmount
(if mounted) & power-off manually but did not always succeed as for powering
off. If that happens, shutdown always results in the count increasing, which
makes sense, after all.
The scenario described in the report I linked to cannot be the problem in my
case, as the material is old and the packages, including the kernel, I use are
newer. It does indicate, however, that the problem as such has been noticed
before. I have some thoughts on what could be happening in my case but I
haven't had the time to test my hypothesis yet. I will let you know should I
find anything relevant.
K
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-02-04 1:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 23:18 [Bug 205107] New: No HDD spindown/parking on shutdown bugzilla-daemon
2019-10-10 3:49 ` [Bug 205107] " bugzilla-daemon
2019-10-11 23:31 ` bugzilla-daemon
2019-10-11 23:32 ` bugzilla-daemon
2019-10-11 23:35 ` bugzilla-daemon
2019-10-11 23:45 ` bugzilla-daemon
2019-10-18 20:16 ` bugzilla-daemon
2019-10-18 20:51 ` bugzilla-daemon
2019-10-18 21:38 ` bugzilla-daemon
2020-01-06 21:31 ` bugzilla-daemon
2020-01-16 22:37 ` bugzilla-daemon
2020-01-17 14:20 ` bugzilla-daemon
2020-01-17 23:14 ` bugzilla-daemon
2020-01-18 23:39 ` bugzilla-daemon
2020-01-18 23:45 ` bugzilla-daemon
2020-01-18 23:47 ` bugzilla-daemon
2020-01-19 0:27 ` bugzilla-daemon
2020-02-04 1:41 ` bugzilla-daemon [this message]
2020-11-09 22:18 ` bugzilla-daemon
2020-11-09 22:33 ` bugzilla-daemon
2020-11-09 22:34 ` bugzilla-daemon
2020-11-09 22:39 ` bugzilla-daemon
2020-12-23 11:46 ` bugzilla-daemon
2024-11-13 11:53 ` bugzilla-daemon
2024-11-13 12:28 ` 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-205107-11633-4628UQGPgW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@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).