mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank Tornack <f-tornack@t-online.de>
To: linux-kernel@vger.kernel.org
Cc: f-tornack@t-online.de
Subject: Western Digital SSD freezes on power saving
Date: Sun, 28 Jan 2024 13:26:23 +0100	[thread overview]
Message-ID: <dfe9213bb86939ca4502b5b3fdd3ab77ef1b6f1b.camel@t-online.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello Linux kernel developers and experts,

I have a question that I think is not tied to a specific distribution
and goes pretty deep into the Linux kernel. I hope you can help me
without subscribing to the mailing list and remember to include me in
the answer discussion. 

In my old notebook I used an nvme-ssd from WD (wds500g1b0c-00s6u0),
which is affected by a well-known bug. I currently use the parameter
`nvme_core.default_ps_max_latency_us=0` to prevent the system from
freezing. 

I would like to use a new SSD in my new notebook. However, as it is
difficult to sell used SSDs, I would like to continue using the old SSD
affected by the bug. I plan to move the SSD to a Thunderbolt enclosure
for this purpose. I think since Thunderbolt is based on PCIe, the same
energy saving measures and the associated bugs will probably apply.

In the hope that my new SSD doesn't have the same bug, I would prefer
not to disable the Powersafe in the laptop. Is there a way to set this
flag only for a specific SSD? By identifying it by name or serial
number? 

I apologise prophylactically if my question is completely out of place
and thank you for your help. As a long-time Linux user, I would also
like to thank you in general. If you have any follow-up questions,
please do not hesitate to contact me.

- -- 
Frank Tornack <f-tornack@t-online.de>
Privat
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSKs5ZJ/d3p8HqrcSZVreqZ0wXqzQUCZbZH7wAKCRBVreqZ0wXq
zcQkAPwMA+J3eO/S6T92Gsz9YBamYVHhwLlcUAG3qsYM2g8sRAD/UY+If8RlsT5V
uKg89rhH2bnWrVF9PKGU4ZamfHo8eQ0=
=gfie
-----END PGP SIGNATURE-----

             reply	other threads:[~2024-01-28 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28 12:26 Frank Tornack [this message]
2024-01-28 14:04 ` Bagas Sanjaya
2024-01-28 14:25   ` Frank Tornack

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=dfe9213bb86939ca4502b5b3fdd3ab77ef1b6f1b.camel@t-online.de \
    --to=f-tornack@t-online.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®