From: Tejun Heo <htejun@gmail.com>
To: "Lars Michael Jogbäck" <lm@jogback.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: Problems w/ Sil3124 + Port Multiplier
Date: Wed, 02 May 2007 14:47:30 +0200 [thread overview]
Message-ID: <46388862.1020709@gmail.com> (raw)
In-Reply-To: <463828F6.7020209@jogback.se>
Lars Michael Jogbäck wrote:
> I have a system with a Sil3124 controller and two Sil3726 port multipliers.
> I'm running 2.6.18.1 with the patches from
> http://home-tj.org/wiki/index.php/Libata-tj-stable
> since I was not able to get the port multipler to work at all with
> 2.6.21 (perhaps the support for PMP is not fully integrated there).
>
> One of my Sil3726 is freezing my system approx one time per hour when
> the disks are under load.
>
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata5.00: tag 0 cmd 0xea Emask 0x4 stat 0x40 err 0x0 (timeout)
Hmmm... that's FLUSH_CACHE timing out.
> I suspect that the root-cause of the problem could be drive-related. All
> the disks on the other Sil3726 are WD4000KD's and the
> disks attached to this one is 3xWD4000KD and 1xWD4000KS and 1xSamsung
> HD501LJ. Is there a way of test this?
I think the disk attached to port 0 might be bad. Please report the
result of 'smartctl -d ata -a /dev/sdX' where sdX is the device attached
to the failing port.
> Is there an updated patch-set for port multipliers in a later kernel
> than 2.6.18.1?
Sorry but not yet.
--
tejun
next prev parent reply other threads:[~2007-05-02 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 6:00 Problems w/ Sil3124 + Port Multiplier Lars Michael Jogbäck
2007-05-02 12:47 ` Tejun Heo [this message]
2007-05-02 13:30 ` Lars Michael Jogbäck
2007-05-02 13:34 ` Mark Lord
2007-05-03 9:08 ` Tejun Heo
2007-05-03 11:04 ` Lars Michael Jogbäck
2007-05-03 11:37 ` 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=46388862.1020709@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=lm@jogback.se \
/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).