From: Dominik Brodowski <linux@brodo.de>
To: cpufreq@www.linux.org.uk
Subject: Re: Problem with ondemand on Athlon
Date: Mon, 10 Nov 2003 21:59:12 +0100 [thread overview]
Message-ID: <20031110205912.GB7149@brodo.de> (raw)
In-Reply-To: <20031105182110.GA922@inferi.kami.home>
This is really strange... will provide a DEBUG()-printk patch soon, would be
great if you could test it then...
On Wed, Nov 05, 2003 at 07:21:10PM +0100, Mattia Dongili wrote:
> On Tue, Nov 04, 2003 at 07:12:27PM +0100, Dominik Brodowski wrote:
> > Unfortunately, I can't reproduce the problem locally on my p4.
> > Can both of you try out the following, please:
> >
> > 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.
> Linux inferi-2 2.6.0-test9-1 #3 Thu Oct 30 19:40:17 CET 2003 i686 GNU/Linux
> >
> > The p4-clockmod driver [currently] needs to be built as a module then,
> > and you need to pass stock_freq as an argument then. AFAIK, no such
> > requirement exists for powernow-k7.
>
> having a P4 1.8GHz do I need stock_freq=1800000 ? (tried, it works)
yes.
> # modprobe p4_clockmod stock_freq=1800000
>
> # echo *ondemand* > /sys/.../scaling_governor
> --> never returns
strange...
Dominik
next prev parent reply other threads:[~2003-11-10 20:59 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 [this message]
2003-11-11 9:51 ` Mattia Dongili
2003-11-11 18:29 ` Dominik Brodowski
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=20031110205912.GB7149@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 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.