linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Jan Christoph Uhde <UhdeJC@gmx.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: disk with ata_piix freezes
Date: Mon, 19 Oct 2009 18:39:08 -0600	[thread overview]
Message-ID: <4ADD06AC.20104@gmail.com> (raw)
In-Reply-To: <4ADC3B7C.2070207@gmx.net>

On 10/19/2009 04:12 AM, Jan Christoph Uhde wrote:
> Hi,
> my net-book suffers serious disk freezes. I am using the ata_piix driver
> fom the latest ubuntu karmic kernel and have tried almost everything i
> could find .. every kernel option from force_pcs to .. acpi=.+ , pci=.+
> and i would really like to keep acpi .. :(
>
> Since google will not help this time i will ask here for help:
>
>
> ata port 1 device 0
> action = 0x6 i am to stupid to read the acton from libata.h:(
>
> exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> cmd ca/00:28:67:b5:7e/00:00:00:00:00/e0 tag 0 dma 20480 out
> res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
> status: { DRDY }

Unfortunately this error output is not all that useful as it just says 
that a command (in this case a write) never completed. However, some of 
the data from your SMART output is a bit odd:

> 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 20

So looks like you had some data transfer errors..

> Error 20 occurred at disk power-on lifetime: 55 hours (2 days + 7 hours)
> When the command that caused the error occurred, the device was active
> or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 84 51 05 82 a9 11 e0 Error: ICRC, ABRT 5 sectors at LBA = 0x0011a982 =
> 1157506
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> c8 00 08 7f a9 11 e0 08 00:04:19.791 READ DMA
> ef 10 03 9e 3e 05 a0 08 00:04:11.675 SET FEATURES [Reserved for Serial ATA]
> ea 00 00 9e 3e 05 a0 08 00:04:08.477 FLUSH CACHE EXIT
> ca 00 08 97 3e 05 e9 08 00:04:08.476 WRITE DMA
> ea 00 00 96 3e 05 a0 08 00:04:08.370 FLUSH CACHE EXIT

So the command failed due to a CRC error on the SATA link. There should 
really be nothing the kernel or the driver could be doing that could 
cause this on a SATA device. What's the model of this netbook? This 
sounds like some kind of hardware issue to me..

I suspect that disabling ACPI only helps by coincidence (changes power 
usage pattern or something) as it has a lot of effects on the system, 
and isn't really a practical thing to do on any modern system because of 
the amount of functionality that this disables..

  reply	other threads:[~2009-10-20  0:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 10:12 disk with ata_piix freezes Jan Christoph Uhde
2009-10-20  0:39 ` Robert Hancock [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-19 12:30 Jan Christoph Uhde
2009-10-20  1:50 ` Tejun Heo
2009-10-20  8:19   ` Jan Christoph Uhde
2009-10-20  9:50     ` Tejun Heo

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=4ADD06AC.20104@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=UhdeJC@gmx.net \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).