From: Peter Favrholdt <linux-ide@how.dk>
To: Tomi Orava <Tomi.Orava@ncircle.nullnet.fi>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_promise SATA300TX4 "intermittent problems"
Date: Fri, 09 Mar 2007 08:29:24 +0100 [thread overview]
Message-ID: <45F10CD4.1070201@how.dk> (raw)
In-Reply-To: <40739.194.237.142.21.1173423710.squirrel@ncircle.nullnet.fi>
Hi Tomi,
My experiences are in accordance with yours:
1) it doesn't matter if IO-APIC is enabled or not.
2) using Mikaels "patch bundle" the channel may die then recovers ok.
(This can be triggered by using smartctl when loaded).
3) It is never the first port that dies. It seems to be always number 3
or 4.
If you dare, then try using smartctl -d ata -a on your disks and observe
dmesg output :-) Every now and then smartctl will "kill the channel"
which will then recover ok.
However, smartctl does not show this behaviour using just the 1.5Gbps
patch. Running at 1.5Gbps seems to fix the problem - no hickups whatsoever.
Best regards,
Peter
Tomi Orava wrote:
> I've now been running with 2.6.21-rc2-git1 + Mikaels original "patch
> bundle" for 7 days without hangs! The machine has 2 Seagate 7200.7 disks
> and 2 Seagate 7200.10 (in 3.0Gps mode) with Promise Sata300TX4. The system
> does spit the following messages whenever there is load (no hickups user
> noticiable hickups however):
>
> Mar 4 03:51:13 alderan kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x0
> Mar 4 03:51:13 alderan kernel: ata4.00: cmd
> 25/00:00:3f:0e:a8/00:04:09:00:00/e0 tag 0 cdb 0x0 data 524288 in
> Mar 4 03:51:13 alderan kernel: res
> 50/00:00:3e:12:a8/00:00:09:00:00/e0 Emask 0x1 (device error)
> Mar 4 03:51:13 alderan kernel: ata4.00: configured for UDMA/133
> Mar 4 03:51:13 alderan kernel: ata4: EH complete
> Mar 4 03:51:13 alderan kernel: SCSI device sdd: 976773168 512-byte hdwr
> sectors (500108 MB)
> Mar 4 03:51:13 alderan kernel: sdd: Write Protect is off
> Mar 4 03:51:13 alderan kernel: SCSI device sdd: write cache: enabled,
> read cache: enabled, doesn't support DPO or FUA
>
> I have io-apic enabled, Asus A7V880 (Via KT880-chipset).
> In the past, when ever one of the disks failed, it _never_ was
> the first disk on the linux system (although I don't remember if it was
> connected to promise-cards first port as the ports are still numbered in
> some very pecualiar way under linux).
>
> Regards,
> Tomi Orava
next prev parent reply other threads:[~2007-03-09 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 14:32 sata_promise SATA300TX4 "intermittent problems" Peter Favrholdt
2007-03-07 20:12 ` Mikael Pettersson
2007-03-08 16:26 ` Peter Favrholdt
2007-03-09 6:27 ` Peter Favrholdt
2007-03-09 7:01 ` Tomi Orava
2007-03-09 7:29 ` Peter Favrholdt [this message]
2007-03-13 7:11 ` Tomi Orava
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=45F10CD4.1070201@how.dk \
--to=linux-ide@how.dk \
--cc=Tomi.Orava@ncircle.nullnet.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).