Hello! On 3/19/22 11:11 PM, Christian Lamparter wrote: > Samsung' 840 EVO with the latest firmware (EXT0DB6Q) locks up with > the a message: "READ LOG DMA EXT failed, trying PIO" during boot. > > Initially this was discovered because it caused a crash > with the sata_dwc_460ex controller on a WD MyBook Live DUO. > > The reporter "Tice Rex" which has the unique opportunity that he > has two Samsung 840 EVO SSD! One with the older firmware "EXT0BB0Q" > which booted fine and didn't expose "READ LOG DMA EXT". But the > newer/latest firmware "EXT0DB6Q" caused the headaches. > > BugLink: https://github.com/openwrt/openwrt/issues/9505 > Signed-off-by: Christian Lamparter <chunkeey@xxxxxxxxx> > --- > v1 -> v2: removed Reported-by Tag (Damien) > opened up a issue + added BugLink (Andy) > --- > drivers/ata/libata-core.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c > index 0c854aebfe0b..760c0d81d148 100644 > --- a/drivers/ata/libata-core.c > +++ b/drivers/ata/libata-core.c > @@ -4014,6 +4014,9 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = { > ATA_HORKAGE_ZERO_AFTER_TRIM, }, > { "Crucial_CT*MX100*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM | > ATA_HORKAGE_ZERO_AFTER_TRIM, }, > + { "Samsung SSD 840 EVO*", NULL, ATA_HORKAGE_NO_NCQ_TRIM | > + ATA_HORKAGE_NO_DMA_LOG | > + ATA_HORKAGE_ZERO_AFTER_TRIM, }, > { "Samsung SSD 840*", NULL, ATA_HORKAGE_NO_NCQ_TRIM | > ATA_HORKAGE_ZERO_AFTER_TRIM, }, Shouldn't this entry be modified instead? [...] MBR, Sergey
