From: Kronos <kronos@kronoz.cjb.net>
To: cpufreq@www.linux.org.uk
Cc: dbonomi@crema.unimi.it
Subject: Re: [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9
Date: Wed, 20 Oct 2004 17:47:44 +0200 [thread overview]
Message-ID: <20041020154744.GA5372@dreamland.darkstar.lan> (raw)
In-Reply-To: <200410201413.i9KED718023481@fire-1.osdl.org>
Il Wed, Oct 20, 2004 at 07:13:07AM -0700, bugme-daemon@osdl.org ha scritto:
> Problem Description:
> with linux 2.6.7 my processor is correctly recognized, this is the relative
> kernel output
>
> powernow: PowerNOW! Technology present. Can scale: frequency and voltage.
> powernow: FSB: 132.686 MHz
> powernow: Found PSB header at c00f06f0
> powernow: Table version: 0x12
> powernow: Flags: 0x0 (Mobile voltage regulator)
> powernow: Settling Time: 100 microseconds.
> powernow: Has 8 PST tables. (Only dumping ones relevant to this CPU).
> powernow: PST:3 (@c00f0746)
> powernow: cpuid: 0x7a0^Ifsb: 133^ImaxFID: 0x1a^Istartvid: 0x7
> powernow: FID: 0x0 (11.0x [1459MHz])^IVID: 0xe (1.300V)
> powernow: FID: 0x1 (11.5x [1525MHz])^IVID: 0xd (1.350V)
> powernow: FID: 0x2 (12.0x [1592MHz])^IVID: 0xc (1.400V)
> powernow: FID: 0x3 (12.5x [1658MHz])^IVID: 0xb (1.450V)
> powernow: FID: 0x14 (13.0x [1724MHz])^IVID: 0xa (1.500V)
> powernow: FID: 0x15 (13.5x [1791MHz])^IVID: 0x9 (1.550V)
> powernow: FID: 0x18 (15.0x [1990MHz])^IVID: 0x8 (1.600V)
> powernow: FID: 0x1a (16.0x [2122MHz])^IVID: 0x7 (1.650V)
> powernow: SGTC: 13333
> powernow: Minimum speed 1459 MHz. Maximum speed 2122 MHz.
>
> with 2.6.9 is not
>
> powernow: PowerNOW! Technology present. Can scale: frequency and voltage.
> powernow: No PST tables match this cpuid (0x7a0)
> powernow: This is indicative of a broken BIOS.
> powernow: Trying ACPI perflib
> powernow: Minimum speed 298 MHz. Maximum speed 796 MHz.
Hi,
I saw something similar on my notebook. In my case when the notebook is
turned on while using battery BIOS sets CPU speed to a frequency lower
than the defaul (800MHz for me). It seems that powernow driver is
confused by the BIOS fiddling with CPU speed and fails to load. I had
the same symptoms: PST not found and wrong min/max frequencies.
Disabling "Automatic CPU power saving" (or something like that) in the
BIOS cures the problem for me. Note that this option do not affect power
management under linux (or windows), it just controls the CPU before a
real OS comes up.
Luca
--
Home: http://kronoz.cjb.net
La somma dell'intelligenza sulla terra e` una costante.
La popolazione e` in aumento.
next prev parent reply other threads:[~2004-10-20 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:13 [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9 bugme-daemon
2004-10-20 15:47 ` Kronos [this message]
2004-10-20 16:05 ` Daniele Bonomi
2004-10-20 16:51 ` Kronos
2004-10-21 10:25 ` Bruno Ducrot
2004-10-21 16:10 ` Kronos
2004-10-23 21:43 ` [PATCH] Fix cpu recognization if BIOS does not set cpu to max freq [was: Re: [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9] Kronos
2004-10-29 15:35 ` Dominik Brodowski
2004-11-10 20:15 ` Bruno Ducrot
2004-11-02 21:10 ` [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9 Dave Jones
2004-11-02 22:13 ` [PATCH for other issue included] " Dominik Brodowski
2004-10-20 19:37 ` Daniele Bonomi
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=20041020154744.GA5372@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=cpufreq@www.linux.org.uk \
--cc=dbonomi@crema.unimi.it \
/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.