All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: Dominik Brodowski <linux@brodo.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: speedstep-smi woes
Date: Tue, 18 Nov 2003 20:09:34 +0100	[thread overview]
Message-ID: <20031118190934.GD32464@poupinou.org> (raw)
In-Reply-To: <20031118182046.GA5950@brodo.de>

On Tue, Nov 18, 2003 at 07:20:46PM +0100, Dominik Brodowski wrote:
> Under heavy load speedstep-smi generates "cpufreq: change failed" messages
> at least on two systems, one of them my own. I've tried to evaluate how to
> avoid these failures:
> 
> - wbinvd() has no positive effect
> - disabling bus master arbitration (io-port 0x22 on 440bx) has no positive effect
> - mdelay(250) immediately before the asm smi call has resulted in _zero_
>   failures.
> 
> However, in most cases, even under heavy load, the speedstep-smi driver
> _does_ achieve speedstep transitions. 
> 
> So, how to proceed?
> a) Try to avoid these failures, even if the cost of all transitions is 250ms
>    then? This practically disables dynamic frequency scaling for
>    speedstep-smi.
> b) Do the same as before: this means that sometimes the frequency isn't
>    changed even though the user or the dynamic frequency scaling governor
>    demands a higher frequency. Also, the "speedstep_init" step tends to fail
>    sometimes.
> 

Have you done testing with ide stuff in pio mode?

Cheers,

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2003-11-18 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18 18:20 speedstep-smi woes Dominik Brodowski
2003-11-18 19:09 ` Ducrot Bruno [this message]
2003-11-18 20:34   ` Dominik Brodowski
2003-11-18 21:35     ` Ducrot Bruno

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=20031118190934.GD32464@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux@brodo.de \
    /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.