From: Thomas Jackowski <aXe@hadiko.de>
To: linux-ide@vger.kernel.org
Subject: Re: Errors on ICH10R with Seagate HDDs
Date: Fri, 17 Apr 2009 11:10:59 +0200 [thread overview]
Message-ID: <49E847A3.9070100@hadiko.de> (raw)
In-Reply-To: <49DE39E2.7070505@kernel.org>
Hi,
yes this was AHCI. NCQ was enabled. I forgot to mention kernel version:
2.6.26-1-amd64 (Debian Lenny)
So here is my test:
Enabled AHCI in BIOS.
[ 0.000000] Command line: root=/dev/md1 ro libata.force=noncq
[ 0.000000] Kernel command line: root=/dev/md1 ro libata.force=noncq
[...]
[ 3.237941] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps
0x3f impl SATA mode
[ 3.238000] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo
pmp pio slum part
Ah, NCQ still activated.
/sys/block/sdc/device/queue_depth shows 31.
I guess NCQ still activated even with libata.force=noncq ?
Now here is my second test:
Disabled AHCI in BIOS.
ata_piix is used now. Did some IO, can't force any freezes.
In the meantime I found topics like this:
http://forums.seagate.com/stx/board/message?board.id=ata_drives&thread.id=2879&view=by_date_ascending&page=1
This looks like a firmware bug. I think I should contact Seagate ;) or
any other ideas?
Bye
Tejun Heo wrote:
> Hello,
>
> Thomas Jackowski wrote:
>> This is /dev/sdc. /dev/sdd and /dev/sde is the same model with the same
>> Firmware. I'm using a RAID5 on these 3 HDDs.
>> Because of the Seagate Firmware Bug I had to upgrade the firmware from
>> 'SD15' to 'SD1A'. The upgrade was successful.
>>
>> Before the upgrade there were no problems, after the upgrade I have
>> trouble like this:
> ...
>> [14144.875931] ata4.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0
>
> Timeout on IDENTIFY.
>
>> [507139.744602] ata5.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
>> [507453.049519] ata4.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
>
> and two timeouts on CHK_POWER.
>
> ahci, right? Given that the problem appeared after firmware update,
> it seems to indicate firmware problem. Does libata.force=noncq make
> any difference?
>
next prev parent reply other threads:[~2009-04-17 9:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 11:32 Errors on ICH10R with Seagate HDDs Thomas Jackowski
2009-04-09 18:09 ` Tejun Heo
2009-04-17 9:10 ` Thomas Jackowski [this message]
2009-04-19 8:56 ` Tejun Heo
2009-04-25 10:22 ` Thomas Jackowski
2009-04-26 2:00 ` Tejun Heo
2009-06-16 1:59 ` Thomas Jackowski
2009-06-17 6:33 ` Tejun Heo
2009-06-22 18:40 ` Thomas Jackowski
2009-06-26 2:33 ` Tejun Heo
2009-06-29 8:17 ` Thomas Jackowski
2009-06-29 14:09 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2009-10-28 15:26 Thomas Jackowski
2009-11-09 15:02 ` Tejun Heo
2009-11-09 19:39 ` Thomas Jackowski
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=49E847A3.9070100@hadiko.de \
--to=axe@hadiko.de \
--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 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.