linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonas Petersson" <jonas.petersson@xms.se>
Cc: linux-ide@vger.kernel.org,
	smartmontools-support@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Date: Sun, 07 Sep 2008 22:48:48 +0200	[thread overview]
Message-ID: <48C43E30.6020504@xms.se> (raw)
In-Reply-To: <48BD6086.1030101@xms.se>

For the record:

Jonas Petersson wrote:
> Owen Martin wrote:
>  > This looks like a timeout during a read command:
>  >
>  > ata3.00: cmd c8/00:08:90:3c:59
>  >
>  > Read dma of 8 blocks from 0x903c59
>  >
>  > Next time it happens, see if it is the same LBA. Since the drive came
>  > back after the bus reset makes me think it was probably in error
>  > recovery for an extended amount of time.
> 
> Sounds like a good idea. However, I had the drive swapped yesterday and 
> have now reinstalled on a (seemingly) identical one which so far seems 
> to be free from these messages. Hence, I keep my fingers crossed that 
> this was indeed a hw error.
 > [...]

I've now stressed the new disk for almost a week and seen no indication 
at all to the previous error. Everything else is the same as before - I 
even installed from the very same DVD. My conclusion is therefore that I 
really had a disk that was broken in a way that normal tests will not 
detect.

Hence, my tip to anyone having a similar experience: Don't blame the 
driver, nor the motherboard/chipset - just replace the drive. It would 
of course be even nicer if the error message could spell this out 
somewhat clearer too, but I guess the "I/O error" in the middle is a 
fair hint in retrospect.

			Best / Jonas



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

  reply	other threads:[~2008-09-07 20:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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         ` exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen 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 [this message]
     [not found] <29a863790710101217g607b5425g6a3374c2be1d75a5@mail.gmail.com>
2007-10-13  0:54 ` Andrew Morton
     [not found] <56020.194.255.108.253.1192004925.squirrel@root.dusted.dk>
2007-10-13  0:41 ` Andrew Morton
2007-10-13  5:49   ` Steen Eugen Poulsen
2007-10-23  9:55     ` Tejun Heo
     [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

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=48C43E30.6020504@xms.se \
    --to=jonas.petersson@xms.se \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.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 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).