-----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 <[email protected]>
Privat
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQSKs5ZJ/d3p8HqrcSZVreqZ0wXqzQUCZbZH7wAKCRBVreqZ0wXq
zcQkAPwMA+J3eO/S6T92Gsz9YBamYVHhwLlcUAG3qsYM2g8sRAD/UY+If8RlsT5V
uKg89rhH2bnWrVF9PKGU4ZamfHo8eQ0=
=gfie
-----END PGP SIGNATURE-----
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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi
I am trying to explain the bug, which I understand also existed with
other manufacturers and could be solved with an update for many
devices, but there was no update for my SSD.
As far as I know, the SSD does not wake up or wakes up too late after
the deepest APST sleep state. As far as I know, this could be because
the values in the firmware for the wake-up time are given to the OS too
optimistically or because the SSD does not wake up at all.
I found the same problem for Kingston
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=538e4a8c571efdf131834431e0c14808bcfb1004
And what I had used to get it working on my old device:
https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Controller_failure_due_to_broken_APST_support
Would you please describe what else confuses you? Then I'll try to
clarify it.
Am Sonntag, dem 28.01.2024 um 21:04 +0700 schrieb Bagas Sanjaya:
> 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...
>
- --
Frank Tornack <[email protected]>
Privat
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQSKs5ZJ/d3p8HqrcSZVreqZ0wXqzQUCZbZj3QAKCRBVreqZ0wXq
zff8AP41lex8G8esRL+tIpXu1xVYO19r00riIAhX9IrydNSIjgEAlHgb/KuvrFvv
RLYITrfzXE5R+Iuh0cUtDVcIfD3xsgM=
=w6Ge
-----END PGP SIGNATURE-----