Re: Anybody here using an SSD?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Does this extent to other makers

I believe it's primarily a problem with "some" AMD chipsets (it has to do with the Southbridge) and Samsung EVO paired together.

I'm sharing here two threads where I got help to troubleshoot problems with the Samsung and the AMD chipset. Some commenters make suggestions about what controllers are more trusted, etc.:

https://forums.opensuse.org/showthread.php/556066-Hibernate-with-Samsung-870-EVO-SSD

https://forums.suse.com/discussion/15435/hibernate-with-samsung-870-evo-ssd

If anyone runs into this problem, it is easy to disable NCQ, just add the following to the kernel parameters:

libata.force=noncq

it may slow down random IO a bit, but given that the Samsung 870 EVO is already so fast, it doesn't really bother me (still a lot faster than the previous machanical hard disk).

Also, some Samsung EVO SSDs like 840/850 have in general some problems with DMA (Direct Memory Access) in Linux (unrelated to the chipset):

https://github.com/torvalds/linux/blob/dbe69e43372212527abf48609aba7fc39a6daa27/drivers/ata/libata-core.c#L3774

I may try a Western Digital SSD in the future. WD bought SanDisk, there are some issues with bad sectors reported by users in Newegg reviews of WD SSDs, but not sure how it compares to other brands. Any experience with Seagate besides / in addition to what Kate ("Borg Labs") wrote?

Gianluca

On Thu, 5 Aug 2021, dep wrote:

said Gianluca Interlandi:

| I installed a Samsung 870 EVO 1TB in a laptop with a AMD chipset. I
| learned that Samsung EVO SSDs and AMD chipsets do not play well
| together. I had to disable NCQ in order to get rid of error messages
| that indicated the potential for data loss. Samsung (EVO) + Intel
| chipsets should be fine though. More reading here:
|
| https://bugzilla.kernel.org/show_bug.cgi?id=201693

Good to know, in that I'm running an AMD chipset on the machine in
question. Does this extent to other makers, or is it just a Samsung thing,
do you know? Wonder if the problem has gotten fixed in later kernels; the
report is from 2018.

Another question: I'm running ext4 exclusively here, but I wonder: is there
a particular advantage in one filesystem over another on an SSD?
--
dep

Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx

-----------------------------------------------------
Gianluca Interlandi, PhD gianluca@xxxxxxxxxxxxxxxx
                    +1 (206) 685 4435
                    http://gianluca.today/

Department of Bioengineering
University of Washington, Seattle WA U.S.A.
-----------------------------------------------------
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx

[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux