From: Robert Hancock <hancockrwd@gmail.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-ide@vger.kernel.org, saeed@marvell.com, mlord@pobox.com,
mail@g-radtke.name, avbidder@fortytwo.ch
Subject: Re: sata-mv: Unable to stop eDMA
Date: Thu, 03 Dec 2009 18:25:45 -0600 [thread overview]
Message-ID: <4B185709.2030700@gmail.com> (raw)
In-Reply-To: <20091203191232.GA5382@deprecation.cyrius.com>
On 12/03/2009 01:12 PM, Martin Michlmayr wrote:
> Two users of Debian on the QNAP TS-419P have seen the following
> "Unable to stop eDMA" error in dmesg. Rebooting makes the problem go
> away. Can someone explain what this problem is about and whether this
> might be a bug in the kernel?
>
> The QNAP TS-419P uses the Marvell Kirkwood SoC and offers 4 SATA ports
> via an 88SX7042 chip connected via PCIE (the SATA on the SoC is used
> for 2 eSATA ports).
>
> [ 673.000000] ata1: Unable to stop eDMA
> [ 673.100000] ata1.00: exception Emask 0x52 SAct 0x1 SErr 0xffffffff action 0xe frozen
> [ 673.100000] ata1: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt
> CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
> [ 673.100000] ata1.00: cmd 60/08:00:6e:b6:34/00:00:03:00:00/40 tag 0 ncq 4096 in
> [ 673.100000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
> [ 673.100000] ata1.00: status: { DRDY }
> [ 673.100000] ata1: hard resetting link
The SError being set to all 1s suggests something strange has happened,
like the hardware going cuckoo and returning PCI master aborts..
prev parent reply other threads:[~2009-12-04 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 19:12 sata-mv: Unable to stop eDMA Martin Michlmayr
2009-12-04 0:25 ` Robert Hancock [this message]
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=4B185709.2030700@gmail.com \
--to=hancockrwd@gmail.com \
--cc=avbidder@fortytwo.ch \
--cc=linux-ide@vger.kernel.org \
--cc=mail@g-radtke.name \
--cc=mlord@pobox.com \
--cc=saeed@marvell.com \
--cc=tbm@cyrius.com \
/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;
as well as URLs for NNTP newsgroup(s).