From: "Rafał Bilski" <rafalbilski@interia.pl>
To: "Herbert G. Fischer" <herbert.fischer@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: VIA C3 'Ezra-T' [C5M] - longhaul - do nothing
Date: Wed, 29 Aug 2007 19:36:15 +0200 [thread overview]
Message-ID: <46D5AE8F.2080209@interia.pl> (raw)
In-Reply-To: <9f90e8bf0708290624m592290a0v6ae9d76b7d4d19a0@mail.gmail.com>
> Here is the output after:
>
> # modprobe longhaul
> # cpufreq-info
> # cpufreq-set -f399
> # cpufreq-set -gpowersave
> # cpufreq-info
Thanks. Can You try the same for longhaul with "scale_voltage"
module option set to "1"?
> cpufreq-core: trying to register driver longhaul
> cpufreq-core: adding CPU 0
> longhaul: VIA C3 'Ezra-T' [C5M] CPU detected. Powersaver supported.
> longhaul: Using northbridge support.
> longhaul: MinMult:3.0x MaxMult:7.5x
> longhaul: FSB:133MHz Lowest speed: 399MHz Highest speed:399MHz
Weird bug, but can wait. Seems to be present in print_speed().
> freq-table: table entry 0: 399000 kHz, 1 index
> [...]
> freq-table: target is 0 (399000 kHz, 1)
> cpufreq-core: notification 0 of frequency transition to 399000 kHz
> userspace: saving cpu_cur_freq of cpu 0 to be 399000 kHz
> longhaul: Setting to FSB:133MHz Mult:3.0x (399MHz)
> cpufreq-core: notification 1 of frequency transition to 997000 kHz
> userspace: saving cpu_cur_freq of cpu 0 to be 997000 kHz
In this moment I don't know if it is unsuccessfull frequency
transition or problem with hardware. Maybe bits in EBL_CR_POWERON
registers are stuck. Can You benchmark (any program You like)
how fast Your CPU is after reboot and before modprobing longhaul?
And compare it with results after modprobing longhaul and setting
governor to "powersave"?
----------------------------------------------------------------------
Gorace i zmyslowe (tylko dla doroslych)
>>>http://link.interia.pl/f1b13
next prev parent reply other threads:[~2007-08-29 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f90e8bf0708280759x6068ae15j9f24e654307a3037@mail.gmail.com>
[not found] ` <46D4433A.7000509@interia.pl>
[not found] ` <9f90e8bf0708281101q19afb3ableb3589b7c363759c@mail.gmail.com>
[not found] ` <46D46CC2.6080405@interia.pl>
[not found] ` <9f90e8bf0708281314v28f29cb3o8e68a3b77701e656@mail.gmail.com>
[not found] ` <46D5000D.7010503@interia.pl>
2007-08-29 13:24 ` VIA C3 'Ezra-T' [C5M] - longhaul - do nothing Herbert G. Fischer
2007-08-29 17:36 ` Rafał Bilski [this message]
2007-08-29 18:35 ` Herbert G. Fischer
2007-08-29 19:16 ` Rafał Bilski
2007-08-29 19:40 ` Herbert G. Fischer
2007-08-29 20:21 ` Rafał Bilski
2007-08-29 20:42 ` Herbert G. Fischer
2007-08-31 6:49 ` Rafał Bilski
2007-08-31 10:51 ` Herbert G. Fischer
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=46D5AE8F.2080209@interia.pl \
--to=rafalbilski@interia.pl \
--cc=cpufreq@lists.linux.org.uk \
--cc=herbert.fischer@gmail.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 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.