From: Erik Slagter <erik@slagter.name>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: ATA Write Error and Time-out Notification in User Space
Date: Wed, 04 Jan 2006 13:48:37 +0100 [thread overview]
Message-ID: <1136378917.24032.18.camel@localhost.localdomain> (raw)
In-Reply-To: <1136378721.22598.90.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Wed, 2006-01-04 at 12:45 +0000, Alan Cox wrote:
> On Mer, 2006-01-04 at 13:37 +0100, Erik Slagter wrote:
> > > Its been known for some time so perhaps the ide maintainers have patches
> > > waiting for 2.6.16 now its opened ?
> >
> > Is this patch supposed to fix this problem:
>
> Nope - it fixes a problem with the old IDE layer.
Ow, sorry, I probably didn't read your msg carefully.
> > Promise SATAII150 TX2plus using libata_promise, when it misses one
> > single interrupt (or maybe it's not even missed but only delayed), it
> > goes crazy, kernel log is full with disk failures, and the disk is
> > kicked out of the md(1) array grmbl.
> >
> > This happens when amd76x_pm is used, even with the irq watcher in the
> > utter most conservative setting.
>
> Does it happen with it not being used ?
No, I bought a new (decent) power supply recently, and since then I did
not have a single problem with the card. Until I start using amd76x_pm.
I have it setup so that whenever a single interrupt is caught
(monitoring interval: 1ms) any transition to C2 is suspended for about a
second.
But I realise this is not officially supported stuff, it's just nice if
it would work, it saves about 70 watts on power (confirmed by own
measurements) and a lot of heat.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]
next prev parent reply other threads:[~2006-01-04 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 18:29 ATA Write Error and Time-out Notification in User Space John Treubig
2006-01-03 18:58 ` Alan Cox
2006-01-03 19:27 ` John Treubig
2006-01-03 21:48 ` Alan Cox
2006-01-04 12:37 ` Erik Slagter
2006-01-04 12:45 ` Alan Cox
2006-01-04 12:48 ` Erik Slagter [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 20:27 John Treubig
2005-12-20 21:55 John Treubig
2005-12-20 22:50 ` Alan Cox
2005-12-21 0:31 ` Drew Winstel
2005-12-22 1:09 ` Alan Cox
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=1136378917.24032.18.camel@localhost.localdomain \
--to=erik@slagter.name \
--cc=alan@lxorguk.ukuu.org.uk \
--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).