From: Peter Favrholdt <linux-ide@how.dk>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_promise SATA300TX4 "intermittent problems"
Date: Fri, 09 Mar 2007 07:27:24 +0100 [thread overview]
Message-ID: <45F0FE4C.7060901@how.dk> (raw)
In-Reply-To: <45F0393D.80301@how.dk>
Hi again,
Peter Favrholdt wrote:
> My feeling is this is not caused by 1.5Gbps or 3.0Gbps operation.
> <...snip>
> My next test will be a plain 2.6.21rc2. Then I'll apply the patches one
> by one.
I've tested 2.6.21-rc2 which fails (sdc down after 27 minutes & sdd down
after 46 minutes).
Then I applied just a single patch to 2.6.21-rc2: Mikael Petterssons
patch to force 1.5Gbps operation and tested again - this time no
problems at all!
(BTW: both kernels are running with IO-APIC disabled).
I've put results+dmesg output here: http://sata300tx4.gratiswiki.dk/
Best regards,
Peter
next prev parent reply other threads:[~2007-03-09 6:27 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 [this message]
2007-03-09 7:01 ` Tomi Orava
2007-03-09 7:29 ` Peter Favrholdt
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=45F0FE4C.7060901@how.dk \
--to=linux-ide@how.dk \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.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 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.