From: Daniele Bonomi <dbonomi@crema.unimi.it>
To: cpufreq@www.linux.org.uk
Subject: Re: [Bug 3600] New: Cpu recognization fails after upgrade from 2.6.7 to 2.6.9
Date: Wed, 20 Oct 2004 21:37:22 +0200 [thread overview]
Message-ID: <20041020213722.3cae81fc@paraclito.crema> (raw)
In-Reply-To: <20041020154744.GA5372@dreamland.darkstar.lan>
On Wed, 20 Oct 2004 17:47:44 +0200 Kronos <kronos@kronoz.cjb.net> wrote:
With the patch previously supplied by Kronos things started working as
well.
Output from the "broken" kernel with debug enabled is
powernow: PowerNOW! Technology present. Can scale: frequency and
voltage. powernow: FSB: 49.758 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: No PST tables match this cpuid (0x7a0)
powernow: This is indicative of a broken BIOS.
powernow: Trying ACPI perflib
powernow: acpi: P0: 2133 MHz 75000 mW 125 uS control 00d058fa SGTC
13334 powernow: FID: 0x1a (16.0x [796MHz]) VID: 0x7 (1.650V)
powernow: acpi: P1: 1800 MHz 55000 mW 125 uS control 00d05935 SGTC
13334 powernow: FID: 0x15 (13.5x [671MHz]) VID: 0x9 (1.550V)
powernow: acpi: P2: 1467 MHz 32000 mW 125 uS control 00d059c0 SGTC
13334 powernow: FID: 0x0 (11.0x [547MHz]) VID: 0xe (1.300V)
powernow: acpi: P3: 1064 MHz 30000 mW 125 uS control 00d059ca SGTC
13334 powernow: FID: 0xa (8.0x [398MHz]) VID: 0xe (1.300V)
powernow: acpi: P4: 800 MHz 26000 mW 125 uS control 00d059c6 SGTC 13334
powernow: FID: 0x6 (6.0x [298MHz]) VID: 0xe (1.300V)
powernow: Minimum speed 298 MHz. Maximum speed 796 MHz.
now is right
powernow: PowerNOW! Technology present. Can scale:
frequency and voltage. powernow: FSB: 132.718 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 fsb: 133 maxFID: 0x1a startvid: 0x7
powernow: FID: 0x0 (11.0x [1459MHz]) VID: 0xe (1.300V)
powernow: FID: 0x1 (11.5x [1526MHz]) VID: 0xd (1.350V)
powernow: FID: 0x2 (12.0x [1592MHz]) VID: 0xc (1.400V)
powernow: FID: 0x3 (12.5x [1658MHz]) VID: 0xb (1.450V)
powernow: FID: 0x14 (13.0x [1725MHz]) VID: 0xa (1.500V)
powernow: FID: 0x15 (13.5x [1791MHz]) VID: 0x9 (1.550V)
powernow: FID: 0x18 (15.0x [1990MHz]) VID: 0x8 (1.600V)
powernow: FID: 0x1a (16.0x [2123MHz]) VID: 0x7 (1.650V)
powernow: SGTC: 13333
powernow: Minimum speed 1459 MHz. Maximum speed 2123 MHz.
Thank you all very much for the help.
Daniele
--
,___, While most peoples' opinions change, the conviction of their
(9v9) correctness never does
(_^((\ Gpg Key at filibusta.crema.unimi.it/~dbonomi/db.asc
-^-"-"-\\-^-- FP = C613 3CF3 94CD FA27 7900 D16C 3A6E 1CB5 585A CD71
prev parent reply other threads:[~2004-10-20 19:37 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
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 [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=20041020213722.3cae81fc@paraclito.crema \
--to=dbonomi@crema.unimi.it \
--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