All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org, trelane@digitasaru.net
Subject: Re: ata error message exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Date: Thu, 17 Jul 2008 19:17:49 -0600	[thread overview]
Message-ID: <487FEF3D.3060709@shaw.ca> (raw)
In-Reply-To: <fa.nKgr6Ih9+hsUpOTCrIh8muNF7MY@ifi.uio.no>

Joseph Pingenot wrote:
> Hi all.
> 
> Anyone know what is causing the following troubles:
> Jul 16 16:16:27 cruftix kernel: [12538.998440] ata5.00: exception Emask
> 0x0 SAct 0x0 SErr 0x0 action 0x2
> Jul 16 16:16:27 cruftix kernel: [12538.998450] ata5.00: irq_stat
> 0x00020002, device error via D2H FIS
> Jul 16 16:16:27 cruftix kernel: [12538.998457] ata5.00: cmd
> 35/00:08:87:17:58/00:00:59:00:00/e0 tag 0 dma 4096 out
> Jul 16 16:16:27 cruftix kernel: [12538.998459]          res
> 51/84:00:8e:17:58/00:00:59:00:00/e0 Emask 0x10 (ATA bus error)
> Jul 16 16:16:27 cruftix kernel: [12538.998464] ata5.00: status: { DRDY
> ERR }
> Jul 16 16:16:27 cruftix kernel: [12538.998466] ata5.00: error: { ICRC
> ABRT }

..

> (just a sampling)
> I'm transferring data to an ext3 filesystem on a Seagate FreeAgent Pro
>   1TB disk with an eSATA connector (Norco 4618 eSATA card with SiI 3124:

Looks like you're getting errors on the SATA link. It sounds like a lot 
of eSATA cables are crap and don't connect properly, etc. so that would 
be the first thing to try swapping out.

       reply	other threads:[~2008-07-18  1:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.nKgr6Ih9+hsUpOTCrIh8muNF7MY@ifi.uio.no>
2008-07-18  1:17 ` Robert Hancock [this message]
2008-07-16 21:26 ata error message exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 Joseph Pingenot
2008-07-17 19:09 ` Jeff Garzik

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=487FEF3D.3060709@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trelane@digitasaru.net \
    /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.