From: Dominik Brodowski <linux@brodo.de>
To: cpufreq@www.linux.org.uk
Subject: Re: Problem with ondemand on Athlon
Date: Tue, 11 Nov 2003 19:29:38 +0100 [thread overview]
Message-ID: <20031111182938.GA4825@brodo.de> (raw)
In-Reply-To: <20031111095143.GC930@inferi.kami.home>
On Tue, Nov 11, 2003 at 10:51:43AM +0100, Mattia Dongili wrote:
> On Mon, Nov 10, 2003 at 09:59:12PM +0100, Dominik Brodowski wrote:
> > This is really strange... will provide a DEBUG()-printk patch soon, would be
> > great if you could test it then...
>
> of course I can. In the meantime if you can tell a couple of interesting
> functions and variables, I could add some printk-s by myself (if I get
> some spare time before you do)
Basically the ->governor function in the ondemand() governor, the
__cpufreq_governor, cpufreq_governor, cpufreq_set_policy after the call to
__cpufreq_set_policy, and the sysfs fuctions (show / store /
store_scaling_governor).
> > > > pass "clock=pit" as a command line argument
> > >
> > > this semms not to be a valid argument here
> >
> > ? clock=pit specifies that the PIT should be used instead of the TSC as
> > timing source... so it should be a valid boot argument.
>
> sorry... my bad. I used it as a p4_clockmod argument
Sorry for my unclear comment "command line argument"...
> I'll re-test it as soon as possible.
Many thanks.
Dominik
prev parent reply other threads:[~2003-11-11 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 13:14 Problem with ondemand on Athlon Thierry Lathuille
2003-10-31 12:27 ` Problem with ondemand on Athlon [and P4 too] Mattia Dongili
2003-11-04 18:12 ` Problem with ondemand on Athlon Dominik Brodowski
2003-11-05 14:57 ` Mattia Dongili
2003-11-05 18:21 ` Mattia Dongili
2003-11-10 20:59 ` Dominik Brodowski
2003-11-11 9:51 ` Mattia Dongili
2003-11-11 18:29 ` Dominik Brodowski [this message]
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=20031111182938.GA4825@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
/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