mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gerhard Mack <gmack@innerfire.net>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: [2.6.21.1] SATA freeze
Date: Thu, 10 May 2007 07:40:00 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705100739280.31317@mtl.rackplans.net> (raw)
In-Reply-To: <46425DCE.1070001@shaw.ca>

On Wed, 9 May 2007, Robert Hancock wrote:
> Gerhard Mack wrote:
> > On Wed, 9 May 2007, Jeff Garzik wrote:
> > > Gerhard Mack wrote:
> > > > May  9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
> > > > SErr
> > > > 0x1800000 action 0x2 frozen
> > > > May  9 14:51:35 mgerhard kernel: ata1.00: cmd
> > > > 35/00:00:80:6d:c8/00:04:09:00:00/e0 tag 0 cdb 0x0 data 524288 out
> > > > May  9 14:51:35 mgerhard kernel:          res
> > > > 40/00:c8:68:65:c8/84:00:09:00:00/e0 Emask 0x4 (timeout)
> > > > May  9 14:51:42 mgerhard kernel: ata1: port is slow to respond, please
> > > > be
> > > > patient (Status 0xd0)
> > > > 
> > > > Anything I can do to figgure out what's causing this?
> 
> You're showing various flags set in the SError register, which suggests you're
> having SATA communication problems with the drive. A bad SATA cable or power
> problems would be a strong possibility.
> 
> It really would be nice if we decoded these things more usefully for the user
> (same with the regular ATA errors, like drivers/ide does), but in general
> SError showing up as non-zero is a bad thing:
> 
> 0x400000 = "Handshake error: When set to one, this bit indicates that one or
> more R_ERR handshake response was received in response to frame transmission.
> Such errors may be the result of a CRC error detected by the recipient, a
> disparity or 10b/8b decoding error, or other error condition leading to a
> negative handshake on a transmitted frame."
> 
> 0x1800000 = "Link Sequence Error: When set to one, this bit indicates that one
> or more Link state machine error conditions was encountered since the last
> time this bit was cleared. The Link Layer state machine defines the conditions
> under which the link layer detects an erroneous transition."
> 
> and
> 
> "Transport state transition error: When set to one, this bit indicates that an
> error has occurred in the transition from one state to another within the
> Transport layer since the last time this bit was cleared."


Just out of curiosity how often is that bit cleared?

	Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

  reply	other threads:[~2007-05-10 11:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.Ngs+g4HBWK5JUzEhRMjcVQVR448@ifi.uio.no>
     [not found] ` <fa.xHed6JNWpYYFYmDy7FY+p6HTjPw@ifi.uio.no>
     [not found]   ` <fa.I0i3SlPzvZnxCYuJNFL3tixqEJU@ifi.uio.no>
2007-05-09 23:48     ` Robert Hancock
2007-05-10 11:40       ` Gerhard Mack [this message]
2007-06-04 12:59 Tomasz Chmielewski
     [not found] <fa.zU1kuoSgByTYCYqY+iCQ5rMJy34@ifi.uio.no>
2007-05-12 18:48 ` Robert Hancock
2007-05-12 19:09   ` Fred Moyer
2007-05-13  1:02     ` Robert Hancock
2007-05-13  1:52       ` Fred Moyer
2007-05-13  1:20   ` Robin H. Johnson
2007-05-13 18:18     ` Jim Paris
     [not found] <fa.nl0Mcy44vzL27dQ8CsLG/+SfNO0@ifi.uio.no>
     [not found] ` <fa.Odn/BmbDLGQp4kzhwqs6TScgkdE@ifi.uio.no>
     [not found]   ` <fa.QtdEc9oISM5NdAmikW4kWhdGDeM@ifi.uio.no>
     [not found]     ` <fa.YyeTl86xaR6Y3MLVL7vUm5SgUzc@ifi.uio.no>
     [not found]       ` <fa.9rF0YSLySQV/+6iXNTOmlASflXA@ifi.uio.no>
2007-05-12 18:34         ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2007-05-09 18:54 Gerhard Mack
2007-05-09 19:53 ` Jeff Garzik
2007-05-09 21:43   ` Gerhard Mack
2007-05-09 22:58     ` Chuck Ebbert
2007-05-10  8:51     ` Mikael Pettersson
2007-05-10 11:27       ` Gerhard Mack

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=Pine.LNX.4.64.0705100739280.31317@mtl.rackplans.net \
    --to=gmack@innerfire.net \
    --cc=hancockr@shaw.ca \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®