From: bugzilla-daemon@kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 205107] No HDD spindown/parking on shutdown
Date: Wed, 13 Nov 2024 12:28:07 +0000 [thread overview]
Message-ID: <bug-205107-11633-lREyd0OwsE@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 #23 from Dmitry Baranov (reagentoo@gmail.com) ---
(In reply to Li Jiajun from comment #22)
> Inspired by #21, we could solve this by add a new udev rule.
> I think this is a common issue for those people using usb2sata adapter.
Also discards should not be forgotten.
provisioning_mode=unmap is not enabled by default for external USB devices.
My current rules file for kernel 6.6:
---
$ cat /etc/genkernel.d/etc/udev/rules.d/10-usb-storage.rules
# ASMedia Technology Inc. ASM236X series
ACTION=="add", SUBSYSTEM=="scsi_disk", ATTRS{idVendor}=="174c",
ATTRS{idProduct}=="2364", ENV{LABEL}="edisk"
# JMicron Technology Corp. / JMicron USA Technology Corp. USB 3.1 Storage
Device
ACTION=="add", SUBSYSTEM=="scsi_disk", ATTRS{idVendor}=="152d",
ATTRS{idProduct}=="0580", ENV{LABEL}="edisk"
ENV{LABEL}=="edisk", DRIVERS=="uas", ATTR{provisioning_mode}="unmap"
ENV{LABEL}=="edisk", DRIVERS=="usb", ATTR{manage_system_start_stop}="1"
---
Can be mixed with ATTRS{serial}=="XXXXXXXXXXXXXX" to enable discards /
start_stop on unique devices.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2024-11-13 12:28 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
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 [this message]
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-lREyd0OwsE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).