@Offtopic: Isn't it possible to edit previous posts? Because it feels like an monologue to post news comments all the time.
However I opened a thread on the Crucial forum [1] and a nice guy referred me to another thread [2] which tells that the bug is fixed with firmware MU05. And there a two link to kernel mailinglist posts which are blacklisting all Crucial SSDs for queued trim [3] and reverting this for MU05 [4]. Is this the same "whiteliste" the Ubuntu people are talking about? When I want to test trim with newest firmware MU05 is it enough to add "--no-model-check" or do I also have to use a special kernel?
@Offtopic: Isn't it possible to edit previous posts? Because it feels like an monologue to post news comments all the time.
However I opened a thread on the Crucial forum [1] and a nice guy referred me to another thread [2] which tells that the bug is fixed with firmware MU05. And there a two link to kernel mailinglist posts which are blacklisting all Crucial SSDs for queued trim [3] and reverting this for MU05 [4]. Is this the same "whiteliste" the Ubuntu people are talking about? When I want to test trim with newest firmware MU05 is it enough to add "--no-model-check" or do I also have to use a special kernel?
[1] http:// forum.crucial. com/t5/ Solid-State- Drives- SSD/M500- on-Linux- with-fstrim- or-discard- under-heavy- load-could/ td-p/151522 forum.crucial. com/t5/ Solid-State- Drives- SSD/M500- M5x0-QUEUED- TRIM-data- corruption- alert-mostly- for-Linux/ td-p/151028 comments. gmane.org/ gmane.linux. ide/56084 www.spinics. net/lists/ linux-ide/ msg48361. html
[2] http://
[3] http://
[4] http://