From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Michele Baldessari <michele@acksyn.org>
Cc: linux-ide@vger.kernel.org, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add ATA_HORKAGE_BROKEN_FPDMA_AA quirk for Seagate Momentus SpinPoint M8
Date: Mon, 25 Nov 2013 21:08:42 +0000 [thread overview]
Message-ID: <20131125210842.0c68ee92@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <1385406014-4877-1-git-send-email-michele@acksyn.org>
> Reported-by: Nicholas <arealityfarbetween@googlemail.com>
> Signed-off-by: Michele Baldessari <michele@acksyn.org>
> Tested-by: Nicholas <arealityfarbetween@googlemail.com>
Acked-by: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Going for a dig in google turns this up against multiple controllers,
multiple kernels, multiple distros..
> ---
> 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 81a94a3..f6b0892 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -4156,6 +4156,9 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
> { "ST3320[68]13AS", "SD1[5-9]", ATA_HORKAGE_NONCQ |
> ATA_HORKAGE_FIRMWARE_WARN },
>
> + /* Seagate Momentus SpinPoint M8 seem to have FPMDA_AA issues */
> + { "ST1000LM024 HN-M101MBB", "2AR10001", ATA_HORKAGE_BROKEN_FPDMA_AA },
> +
> /* Blacklist entries taken from Silicon Image 3124/3132
> Windows driver .inf file - also several Linux problem reports */
> { "HTS541060G9SA00", "MB3OC60D", ATA_HORKAGE_NONCQ, },
next prev parent reply other threads:[~2013-11-25 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:00 [PATCH] Add ATA_HORKAGE_BROKEN_FPDMA_AA quirk for Seagate Momentus SpinPoint M8 Michele Baldessari
2013-11-25 21:08 ` One Thousand Gnomes [this message]
2013-11-29 22:25 ` Tejun Heo
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=20131125210842.0c68ee92@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michele@acksyn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox