mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Mr. James W. Laferriere" <babydr@baby-dragons.com>,
	Tom Mortensen <tmmlkml@gmail.com>,
	Bill Davidsen <davidsen@tmr.com>,
	Gwendal Grignou <gwendal@google.com>,
	Brian Rademacher <rad@radfiles.net>,
	linux-ide@vger.kernel.org,
	linux-raid maillist <linux-raid@vger.kernel.org>,
	Linux Kernel Maillist <linux-kernel@vger.kernel.org>,
	Bruce Allen <ballen@gravity.phys.uwm.edu>,
	smartmontools-support@lists.sourceforge.net, xfs@oss.sgi.com
Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen
Date: Fri, 10 Oct 2008 15:13:26 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0810101505420.12937@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.1.10.0810040410170.14969@p34.internal.lan>



On Sat, 4 Oct 2008, Justin Piszcz wrote:

>
>
> On Sat, 4 Oct 2008, Tejun Heo wrote:
>
>> Justin Piszcz wrote:
>>

What do these signifiers mean (they are always the same, no matter the
controller used OR the disk in question (happens across 12 disks and 3 
different controllers)):

[420781.333179] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[420781.333189] ata6.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
                              ^^ ^^(b0/d8)^^ ^^(4f:c2)
[420781.333190]          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)                    ^^ 40:00:ff
[420781.333194] ata6.00: status: { DRDY }
[420781.333200] ata6: hard resetting link
[420781.638589] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[420781.662166] ata6.00: configured for UDMA/133
[420781.662166] ata6: EH complete

(at the time there was little to no I/O occuring on this block device, but 
disks on the raid5 volume were being accessed at the time, so there was 
system activity, mainly disk reads 300-500KiB/s over ethernet)

  Nick's(?) problem:

> Nick
> 
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
                ^^ ^^ (ea/00) vs. (b0/d8) - mind are always the same (FYI)
>         res 40/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
               ^^ ^^ (40:00: but no ff)

           The rest of the messages are the same.  Is there any correlation
           that can be made here?  When this happens to others, is it
           always the same codes as shown above or do they change?  If they
           do not change, how come they vary between users who have this
           problem?

> ata1.00: status: { DRDY }
> ata1: soft resetting link
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
> sd 1:0:0:0: [sda] Write Protect is off
> sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA

Can anything be said about these errors, can we classify them into groups?
Or are they just random? It does not appear to happen more or less with 
one filesystem or another either, one guy is using ext3, I am using XFS-- 
certainly something much deeper..

Justin.

  parent reply	other threads:[~2008-10-10 19:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E6D0C24877245C3A5A327129A7B4CA7@909927SOSLA>
     [not found] ` <alpine.DEB.1.10.0809220404400.18908@p34.internal.lan>
     [not found]   ` <5A4A9A3B0AAA4A20A33BC2D578F5F75F@909927SOSLA>
     [not found]     ` <alpine.DEB.1.10.0809220828490.23159@p34.internal.lan>
     [not found]       ` <5419A02543384E69AF2BA82FF6E66C14@909927SOSLA>
     [not found]         ` <alpine.DEB.1.10.0809220903400.23159@p34.internal.lan>
     [not found]           ` <4B1ABD0393EF40FFB0A12242FE8356AF@909927SOSLA>
2008-09-22 13:19             ` Justin Piszcz
2008-09-22 13:26               ` Justin Piszcz
2008-09-23 18:14                 ` Gwendal Grignou
2008-09-23 20:59                   ` Brian Rademacher
2008-09-25 15:17                   ` Bill Davidsen
2008-09-29  8:13                     ` Tejun Heo
2008-09-30 20:47                       ` Tom Mortensen
2008-09-30 21:18                         ` Justin Piszcz
2008-10-01  3:50                           ` Mr. James W. Laferriere
2008-10-01  8:06                             ` Justin Piszcz
2008-10-01 11:12                               ` Justin Piszcz
2008-10-04  2:27                                 ` Tejun Heo
2008-10-04  8:11                                   ` Justin Piszcz
2008-10-05  0:23                                     ` Justin Piszcz
2008-10-05  0:29                                       ` berk walker
2008-10-10 19:13                                     ` Justin Piszcz [this message]
2008-10-10 19:27                                       ` Alan Cox
2008-10-01 15:09                       ` Bill Davidsen
2008-09-30 22:04 Christian

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=alpine.DEB.1.10.0810101505420.12937@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=babydr@baby-dragons.com \
    --cc=ballen@gravity.phys.uwm.edu \
    --cc=davidsen@tmr.com \
    --cc=gwendal@google.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=rad@radfiles.net \
    --cc=smartmontools-support@lists.sourceforge.net \
    --cc=tj@kernel.org \
    --cc=tmmlkml@gmail.com \
    --cc=xfs@oss.sgi.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

all inboxes | Powered by JetHome®