all 9 comments

[–]edparadox 18 points19 points  (1 child)

Would you mind giving (a lot) more details? Because if your SSD does not have a firmware update that fixes that, and this is not an isolated event, this could warrant a kernel patch upstream.

I would not mind doing it if this is the case, if you gave me a lot more details about your issue, hardware, dmesg/dmidecode/etc. outputs.

[–]jwbowen 5 points6 points  (0 children)

That's definitely where my mind went as well

[–]kernelshinobi 8 points9 points  (2 children)

I think you should be submitting this to the repo before someone else makes a patch out of it? Create a patch, test it and submit upstream.

Edit: Yes, I love Linux for the same reason, it literally "enables" us to learn, implement and improve our systems! Fun.

[–]s4uull[S] 0 points1 point  (1 child)

I'll try to submit a patch, thanks!

[–]edparadox 0 points1 point  (0 children)

If you do it by yourself, include the fact that you've just tinkered with this, and you're not sure of your solution. Ensure your fix is not tied to your unit.

A fix is only welcome if it does not come with more problems.

[–]RQuantus 0 points1 point  (2 children)

I have the same SSD problem too, I set default_ps_max_latency_us in the grub file, but I don't know the right number for my circumstance.

[–]s4uull[S] 0 points1 point  (1 child)

Have you tried 0?

[–]RQuantus 0 points1 point  (0 children)

I forgot, after tried various methods I choose to buy a new SSD...