public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: Andrew Morton <akpm@osdl.org>
Cc: Joerg Sommrey <jo@sommrey.de>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, arjan@infradead.org,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Wed, 01 Feb 2006 11:25:16 +0100	[thread overview]
Message-ID: <1138789516.4449.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20060131193446.7904ac6f.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

On Tue, 2006-01-31 at 19:34 -0800, Andrew Morton wrote:
> > This is a processor idle module for AMD SMP 760MP(X) based systems.
> >  The patch was originally written by Tony Lindgren and has been around
> >  since 2002.  It enables C2 mode on AMD SMP systems and thus saves
> >  about 70 - 90 W of energy in the idle mode compared to the default idle
> >  mode.  The idle function has been rewritten and is now free of locking
> >  issues and is independent from the number of CPUs.  The impact
> >  from this module on the system clock and on i/o transfer are now fairly
> >  low.

Very nice, but I do have problems with it (last tested version about a
month ago).

I have a Tyan S2466 (760/8MPX) motherboard with a Promise PDC20575
(SATAII150 TX2plus), with two disks configured as raid-1. As soon as C2
starts to kick in (or C3 that doesn't matter) my syslog/dmesg starts to
fill up with error messages from the attached disks and one of the two
(at random) disks is kicked out of the raid. It looks like the other
disk keeps functioning although it keeps spewing lots of error messages.

To me it looks like the Promise controller goes totally bunkus when one
single interrupt is not served, or when it cannot bus master within a
certain time interval. I have tried to work around this problem by using
_very_ conservative values for the irq-watcher. This works well for some
time, but sooner or later the problem re-appears.

So it looks like the only way is to tackle the source of the problem. I
already reported this on linux-ide, but no response. I assume they think
it's a amd76x_pm specific issue.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]

  reply	other threads:[~2006-02-01 10:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 18:55 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Joerg Sommrey
2006-02-01  3:34 ` Andrew Morton
2006-02-01 10:25   ` Erik Slagter [this message]
2006-02-01 17:20   ` Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2006-02-01 18:11 Brown, Len
2006-02-01 18:18 ` Erik Slagter
2006-02-01 18:40   ` Tony Lindgren
2006-02-01 19:13 ` Joerg Sommrey
2006-02-02  1:35 Brown, Len
2006-02-02  1:50 ` Alan Cox
2006-02-02  9:50   ` Erik Slagter
2006-02-02 19:38     ` Tony Lindgren
2006-02-03  9:21 ` Erik Slagter
2006-02-03  9:33   ` Pavel Troller
2006-02-03  9:39     ` Erik Slagter
2006-02-03 10:14       ` Pavel Troller
2006-02-03 10:28         ` Erik Slagter
2006-02-02 22:24 Joerg Sommrey
2006-02-02 22:37 ` Andrew Morton
2006-02-03  7:03   ` Joerg Sommrey
2006-02-02 22:43 ` Dave Jones
2006-02-03  8:45 Brown, Len
2006-02-03  9:35 ` Erik Slagter
2006-02-03 10:31   ` Pavel Troller
2006-02-03 14:16 ` Joerg Sommrey
2006-02-03 15:59 ` Juhani Rautiainen
2006-02-03 17:02   ` Erik Slagter
2006-02-08 20:10   ` Pavel Machek
2006-02-03 18:20 Brown, Len
2006-02-03 18:28 Brown, Len
2006-02-03 18:40 Brown, Len
2006-02-04 10:31 ` Erik Slagter
2006-02-04 10:49   ` Pavel Troller

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=1138789516.4449.14.camel@localhost.localdomain \
    --to=erik@slagter.name \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=jo@sommrey.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.com \
    /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