From: Thomas Jackowski <aXe@hadiko.de>
To: linux-ide@vger.kernel.org
Subject: Re: Errors on ICH10R with Seagate HDDs
Date: Sat, 25 Apr 2009 12:22:52 +0200 [thread overview]
Message-ID: <49F2E47C.5010803@hadiko.de> (raw)
In-Reply-To: <49EAE746.4040303@kernel.org>
Hey,
some additional information (2.6.26-1) and ata_piix:
[653158.828848] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action
0x6 frozen
[653158.828856] ata3.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
[653158.828857] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[653158.828860] ata3.00: status: { DRDY }
[653158.828868] ata3: hard resetting link
[653159.331110] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[653159.355648] ata3.00: configured for UDMA/133
[653159.355666] ata3: EH complete
[653159.371885] sd 2:0:0:0: [sde] 1953523055 512-byte hardware sectors
(1000204 MB)
[653159.374081] sd 2:0:0:0: [sde] Write Protect is off
[653159.374081] sd 2:0:0:0: [sde] Mode Sense: 00 3a 00 00
[653159.390212] sd 2:0:0:0: [sde] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
I tried 2.6.29 and I had no outputs in kernel.log with AHCI and w/o NCQ.
But my system still had hiccups (system hangs for a second) so I am not
sure if there was just no output to kernel.log (due using debian
unstable kernel with eventually mysterious options).
I will observe this and report if any error occurs again.
Bye Thomas
Tejun Heo wrote:
> Hello,
>
> Thomas Jackowski wrote:
>> yes this was AHCI. NCQ was enabled. I forgot to mention kernel version:
>> 2.6.26-1-amd64 (Debian Lenny)
>
> Can you please try 2.6.29?
>
>> 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 ?
>
> Well, if the module is loaded from initrd, you need to jump through
> some loops to get the parameter passed to libata.ko. You can also
> disable NCQ by echoing 1 to queue_depth.
>
>> 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?
>
> Hmmm... please verify with ahci w/o NCQ. If that works fine too,
> please go ahead and contact Seagate.
>
> Thanks.
>
next prev parent reply other threads:[~2009-04-25 10:22 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
2009-04-19 8:56 ` Tejun Heo
2009-04-25 10:22 ` Thomas Jackowski [this message]
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=49F2E47C.5010803@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 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).