]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ata: libata-core: Disable READ LOG DMA EXT for Samsung 840 EVOs
authorChristian Lamparter <chunkeey@gmail.com>
Sat, 19 Mar 2022 20:11:03 +0000 (21:11 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 20 Apr 2022 07:08:32 +0000 (09:08 +0200)
commit9599f3668d2e479388daf5b9a57ab31abcb7e2fe
tree1233c21a9a913d143bea7cb53b76235421b2a085
parent84ddee4ea320411fa038d4f1fd9a0161f989b482
ata: libata-core: Disable READ LOG DMA EXT for Samsung 840 EVOs

[ Upstream commit 5399752299396a3c9df6617f4b3c907d7aa4ded8 ]

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@gmail.com>
Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/ata/libata-core.c