© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
Here's an edited summary of the reply I got from the "please contact our firmware engineers at xxx@xxx" address; turns out there's no engineers there either, but at least we finally have a sane non-formletter reply which *for the first time* states that Samsung is aware of the issue and is working on a fix at the firmware level. Good news for everyone:
"We are just the SSD tech support. We are not the FW engineers. They are in Korea and have been aware of the issue since it first started being reported online.
The latest stable Linux Kernal 4.0.5 successfully blacklists the affected drive(s) from queued TRIM. Linux can still use Sequential TRIM, so you’re not losing out on anything.
We see that you are well aware that Marc Carino and Martin K. Petersen are in contact with Samsung on how to resolve the issue since it started.
All we can say to users at this moment is that Linux is the only operating system that has this issue with the Queued TRIM. Linux is open source and can be modified by anyone, as such we do not support the OS. We recommend updating to the new kernel, as we have seen that other users have done so and it alleviated their issue(s)."