From: Tejun Heo <tj@kernel.org>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: linux-ide@vger.kernel.org, Joseph Chan <JosephChan@via.com.tw>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] sata_via: Apply WD workaround only when needed
Date: Tue, 16 Feb 2016 16:42:53 -0500 [thread overview]
Message-ID: <20160216214253.GR3741@mtj.duckdns.org> (raw)
In-Reply-To: <1455570107-11520-1-git-send-email-linux@rainbow-software.org>
Hello, Ondrej.
On Mon, Feb 15, 2016 at 10:01:47PM +0100, Ondrej Zary wrote:
> The first hdparm is slower because of the error:
> [ 80.964060] ata5.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6
> [ 80.964095] ata5.00: BMDMA stat 0x5
> [ 80.964108] ata5: SError: { UnrecovData Proto TrStaTrns }
> [ 80.964125] ata5.00: failed command: READ DMA EXT
> [ 80.964143] ata5.00: cmd 25/00:90:00:00:00/00:04:00:00:00/e0 tag 0 dma 598016 in
> res 51/84:af:df:00:00/84:03:00:00:00/e0 Emask 0x12 (ATA bus error)
> [ 80.964173] ata5.00: status: { DRDY ERR }
> [ 80.964185] ata5.00: error: { ICRC ABRT }
> [ 80.964209] ata5: hard resetting link
> [ 81.284056] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> [ 81.300531] ata5.00: configured for UDMA/133
> [ 81.300569] ata5: Incompatible drive (WD?): enabling workaround
> [ 81.300598] ata5: EH complete
Hmm... I like the workaround but wish the kernel weren't generating
the above output. How about doing something like the following?
svia_error_handler()
{
if (workaround hasn't been applied yet &&
the conditions match for the workaround) {
apply the workaround;
mark as such;
print informational message;
set ATA_EHI_QUIET;
}
ata_sff_error_handler(ap);
}
--
tejun
next prev parent reply other threads:[~2016-02-16 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 21:01 Ondrej Zary
2016-02-16 21:42 ` Tejun Heo [this message]
2016-02-16 22:57 ` Ondrej Zary
2016-02-17 17:51 ` 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=20160216214253.GR3741@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=JosephChan@via.com.tw \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.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
all inboxes | Powered by JetHome®