All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Steen Eugen Poulsen <sep@lix-world.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	lists@dusted.dk, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Date: Tue, 23 Oct 2007 18:55:55 +0900	[thread overview]
Message-ID: <471DC52B.20802@gmail.com> (raw)
In-Reply-To: <47105C53.7040603@lix-world.net>

Hello,

Steen Eugen Poulsen wrote:
> Sep 28 04:32:40 locker ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0
> action 0x2 frozen
> Sep 28 04:32:40 locker ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00
> tag 0 cdb 0x0 data 123392 in
> Sep 28 04:32:40 locker res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask
> 0x202 (HSM violation)
[--snip--]
> Another machine:
> 
> Sep 28 03:47:55 dragonslair ata1.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x2 frozen
> Sep 28 03:47:55 dragonslair ata1.00: cmd
> b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in
> 
> Sep 28 03:47:55 dragonslair res 50/00:f8:00:4f:c2/00:00:00:00:00/00
> Emask 0x202 (HSM violation)
[--snip--]
> Sep 28 04:33:52 liferaft kernel: ata1.00: exception Emask 0x0 SAct 0x0
> SErr 0x0 action 0x2 frozen
> Sep 28 04:33:55 liferaft kernel: ata1.00: cmd
> b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in
> Sep 28 04:33:55 liferaft kernel:          res
> 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
> Sep 28 04:33:55 liferaft kernel: ata1: soft resetting port
> Sep 28 04:33:55 liferaft kernel: ata1: SATA link up 3.0 Gbps (SStatus
> 123 SControl 300)
> Sep 28 04:33:55 liferaft kernel: ata1.00: configured for UDMA/133
> Sep 28 04:33:55 liferaft kernel: ata1: EH complete

All these are caused by smartd.  Updating should fix the problem.

> Note 2: The hardware didn't freeze for me and I believe the freeze is do
> to swap breaking due to the errors.

Above HSM violations should be harmless other than those messages.
libata resets the devices and should just go on.

> Note 3: dragonslair's harddisk actually crashed, kernel didn't die, it
> just remounted read only. Reboot and the disk was missing, more reboot
> and the machine started with all disks running again, been stable since
> the 28th Sep. (knock on wood)

libata EH can't really recover from actual hardware failures but some
drives come back on if you hot unplug and then replug it.

-- 
tejun

  reply	other threads:[~2007-10-23  9:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10  8:28 exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen lists
2007-10-13  0:41 ` Andrew Morton
2007-10-13  5:49   ` Steen Eugen Poulsen
2007-10-23  9:55     ` Tejun Heo [this message]
     [not found]       ` <471F2647.4030304@lix-world.net>
2007-10-26  1:40         ` Tejun Heo
2007-10-26  4:02           ` Jim Paris
2007-11-06  9:49             ` Bruce Allen
  -- strict thread matches above, loose matches on Subject: below --
2007-10-10 19:17 Greg Cormier
2007-10-11  2:37 ` Steen Eugen Poulsen
2007-10-13  0:54 ` Andrew Morton
     [not found] <48B91198.3020803@xms.se>
     [not found] ` <alpine.DEB.1.10.0808300708330.19513@p34.internal.lan>
     [not found]   ` <48B9AE15.7010605@xms.se>
     [not found]     ` <alpine.DEB.1.10.0808301710380.11166@p34.internal.lan>
     [not found]       ` <48B9C261.4010609@xms.se>
2008-08-30 22:12         ` Justin Piszcz
2008-08-31 10:00           ` Jonas Petersson
2008-09-02 13:39           ` Owen Martin
2008-09-02 15:49             ` [smartmontools-support] " Jonas Petersson
2008-09-07 20:48               ` Jonas Petersson

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=471DC52B.20802@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@dusted.dk \
    --cc=sep@lix-world.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.