From: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: linux-ide@vger.kernel.org,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2 2/2] ata: libata-core: Disable READ LOG DMA EXT for Samsung 840 EVOs
Date: Sat, 19 Mar 2022 21:31:56 +0100 [thread overview]
Message-ID: <771F724E-8E00-4CFA-A39E-91EEFADE132E@gmx.de> (raw)
In-Reply-To: <fe2ff41a52ce2647fd12f69a0d6eba8e3cf05b06.1647720651.git.chunkeey@gmail.com>
> On 19 Mar 2022, at 21:11, Christian Lamparter <chunkeey@gmail.com> wrote:
>
> Samsung' 840 EVO with the latest firmware (EXT0DB6Q) locks up with
> the a message: "READ LOG DMA EXT failed, trying PIO" during boot.
I don't see any info on which kernel this happened with anywhere.
Because there was a bug that tried to use READ LOG DMA EXT even though DMA was not enabled.
That was fixed by a patch from me for 5.16 (and backports).
The behaviour you describe matches the possible symptoms of that bug.
So it would be good to know we're not blaming the drive for an already fixed bug in the kernel...
(I am still seeing some issues that READ LOG EXT - the non-DMA version - times out with interrupt lost for some device/controller combinations, but at least that "only" adds an extra 15 seconds to the boot. It's still a bit silly because in combination with e.g. IDE controllers READ LOG provides absolutely no useful functionality as far as I can tell).
Best regards,
Reimar
next prev parent reply other threads:[~2022-03-19 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 20:11 [PATCH v2 1/2] ata: sata_dwc_460ex: Fix crash due to OOB write Christian Lamparter
2022-03-19 20:11 ` [PATCH v2 2/2] ata: libata-core: Disable READ LOG DMA EXT for Samsung 840 EVOs Christian Lamparter
2022-03-19 20:31 ` Reimar Döffinger [this message]
2022-03-19 20:42 ` Reimar Döffinger
2022-03-21 12:48 ` Damien Le Moal
2022-03-21 8:00 ` Sergey Shtylyov
2022-03-21 10:43 ` Andy Shevchenko
2022-03-21 12:38 ` Damien Le Moal
2022-04-04 1:00 ` Damien Le Moal
2022-04-04 1:00 ` [PATCH v2 1/2] ata: sata_dwc_460ex: Fix crash due to OOB write Damien Le Moal
[not found] <3D5F418D-D612-49A9-80DF-E61313FE006B () gmx ! de>
2022-03-19 21:38 ` [PATCH v2 2/2] ata: libata-core: Disable READ LOG DMA EXT for Samsung 840 EVOs Christian Lamparter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=771F724E-8E00-4CFA-A39E-91EEFADE132E@gmx.de \
--to=reimar.doeffinger@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=chunkeey@gmail.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.