From: firstname.lastname@example.org To: email@example.com Subject: [Bug 205107] No HDD spindown/parking on shutdown Date: Fri, 18 Oct 2019 20:51:00 +0000 Message-ID: <bug-205107-11633-lkcuO4XXxv@https.bugzilla.kernel.org/> (raw) In-Reply-To: <firstname.lastname@example.org/> https://bugzilla.kernel.org/show_bug.cgi?id=205107 --- Comment #6 from Kaur Männamaa (email@example.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.
next prev parent reply index Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-06 23:18 [Bug 205107] New: " 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
Reply instructions: You may reply publically 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/ \ --firstname.lastname@example.org \ --email@example.com \ /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
Linux-ide Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-ide/0 linux-ide/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-ide linux-ide/ https://lore.kernel.org/linux-ide \ firstname.lastname@example.org public-inbox-index linux-ide Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-ide AGPL code for this site: git clone https://public-inbox.org/public-inbox.git