linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Anssi Hannula" <anssi.hannula@iki.fi>
To: linux-ide@vger.kernel.org
Subject: FLUSH CACHE EXT timeouts with ST31500341AS
Date: Tue, 13 Apr 2010 09:09:58 +0300	[thread overview]
Message-ID: <1a212f77bc5e0507a0d7186ccf389dc6.squirrel@mail.onse.fi> (raw)

I'm continously getting the following error with a Seagate ST31500341AS
when under load:

ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata17.00: failed command: FLUSH CACHE EXT
ata17.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata17.00: status: { DRDY }
ata17: hard resetting link
ata17: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata17.00: configured for UDMA/100
ata17.00: retrying FLUSH 0xea Emask 0x4
ata17.00: device reported invalid CHS sector 0
ata17: EH complete

Reading [1] it seems that this is a known issue with this firmware when
NCQ is enabled, and kernel disables NCQ automatically due to this.
However, I'm experiencing the issue despite this. This is on kernel
2.6.33.1.

NCQ seems to be correctly disabled:
# cat /sys/block/sdo/device/queue_depth
1

It seems likely to me that the firmware issue is therefore not limited to
NCQ. Or do you think this might be caused by something else? Do you need
any more information?

In the meantime, I'll try to contact Seagate support to see if they have a
firmware update for my drive.

[1]
https://ata.wiki.kernel.org/index.php/Known_issues#Seagate_harddrives_which_time_out_FLUSH_CACHE_when_NCQ_is_being_used

-- 
Anssi Hannula

             reply	other threads:[~2010-04-13  6:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  6:09 Anssi Hannula [this message]
2010-04-13  6:41 ` FLUSH CACHE EXT timeouts with ST31500341AS Anssi Hannula

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=1a212f77bc5e0507a0d7186ccf389dc6.squirrel@mail.onse.fi \
    --to=anssi.hannula@iki.fi \
    --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).