From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Frank Tornack <f-tornack@t-online.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux NVMe <linux-nvme@lists.infradead.org>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
Guenter Roeck <linux@roeck-us.net>,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: Western Digital SSD freezes on power saving
Date: Sun, 28 Jan 2024 21:04:20 +0700 [thread overview]
Message-ID: <ZbZe5OPlqhwi_erM@archie.me> (raw)
In-Reply-To: <dfe9213bb86939ca4502b5b3fdd3ab77ef1b6f1b.camel@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
On Sun, Jan 28, 2024 at 01:26:23PM +0100, Frank Tornack wrote:
> 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.
>
What well-known bug?
> 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.
>
Confused...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-28 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 12:26 Frank Tornack
2024-01-28 14:04 ` Bagas Sanjaya [this message]
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=ZbZe5OPlqhwi_erM@archie.me \
--to=bagasdotme@gmail.com \
--cc=axboe@fb.com \
--cc=dlemoal@kernel.org \
--cc=f-tornack@t-online.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=sagi@grimberg.me \
/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®