linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 205107] No HDD spindown/parking on shutdown
Date: Fri, 18 Oct 2019 20:51:00 +0000	[thread overview]
Message-ID: <bug-205107-11633-lkcuO4XXxv@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 #6 from Kaur Männamaa (kaurman@outlook.com) ---
Apologies for the delay. I have not had time for the research my current (and
rather limited) knowledge of the matter requires :) So far I have found quite a
few descriptions involving external drives but the problem certainly isn't as
massive as what we've had before
(https://bugzilla.kernel.org/show_bug.cgi?id=7674).

We know now that in your case the drives remain off during shutdown if turned
off manually beforehand. It's not much but it's a piece of the puzzle
nevertheless.

You are using usb2, I found some reports of usb3 causing this. True, I have no
idea (at least off the top of my head) about the kernel version that was used
in these cases. In other words, such a problem can have all kinds of causes.

But while we're at it, are you sure you are not overthinking the problem? I
mean, from what I understood from your previous post, your other drive (sda)
was not affected by the issue? What about the others? In order to do any bug
hunting & get some knowledgeable people involved we must know exactly which
drives are affected. Nailing down the basics is crucial in deciding how much
attention (if any) the bug will get.

Some further questions:

You said you tested with Mint. I assume the kernel version was the same?
Could you perhaps play around some more? Try with a live version of something
(different kernel), maybe even try different systems.


As for your temporary fix, I would say it's a start and during my brief
research on the issue I've seen quite a few versions of it used. Perhaps
convert it into a systemd service to make the process smoother. It turns out
udisksctl supports unmounting too, so you could even make it look nicer if you
wanted to:)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2019-10-18 20:51 UTC|newest]

Thread overview: 23+ 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 [this message]
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
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

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-lkcuO4XXxv@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).