From: Michael Thonke <iogl64nx@gmail.com>
To: Matthias-Christian Ott <matthias.christian@tiscali.de>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>, jeremy@goop.org
Subject: Re: CPUFREQ/speedstep on Intel 955X chipset based system
Date: Sun, 29 May 2005 23:53:03 +0200 [thread overview]
Message-ID: <429A39BF.3020005@gmail.com> (raw)
In-Reply-To: <429A14C3.20604@tiscali.de>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
Matthias-Christian Ott schrieb:
> Michael Thonke wrote:
>
>> Hello,
>>
>> I recently bought an Asus P5WAD2 motherboard which uses the Intel 955x
>> chipset.
>> I noticed that CPUFREQ/speedsteps with the same kernel and same
>> config from
>> my system with Intel 925XE and Intel Pentium 640 does not work on the
>> system with
>> Intel 955X chipset (the processor is the same). In Windows it works
>> perfectly on 925XE
>> and 955X chipset.
>> The kernels I used
>>
>> 2.6.12-rc5 vanilla with git4 patch
>> 2.6.12-rc5-mm1.
>>
>> I attached the output of dmesg and `cat /proc/cpuinfo`
>>
> Please turn on cpufreq debugging (see Documentation/ for details) and
> post the output.
>
>> Thanks in advance
>>
>> Best regards
>> Michael
>> [ ... ]
>
>
> Matthias-Christian Ott
>
Hello,
the debug infos show following when I try to modprobe speedstep-centrino.
speedstep-centrino: Invalid control/status registers (1 - 1)
speedstep-centrino: <6>speedstep-centrino: invalid ACPI data
speedstep-centrino: <6>speedstep-centrino: found unsupported CPU
with Enhanced SpeedStep: send /proc/cpuinfo to Jeremy Fitzhardinge
<jeremy@goop.org>
speedstep-centrino: Invalid control/status registers (1 - 1)
speedstep-centrino: <6>speedstep-centrino: invalid ACPI data
cpuinfo follows
/Michael
[-- Attachment #2: cpuinfo.out --]
[-- Type: text/plain, Size: 1222 bytes --]
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 3.20GHz
stepping : 3
cpu MHz : 3211.542
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr
bogomips : 6340.60
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 3.20GHz
stepping : 3
cpu MHz : 3211.542
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr
bogomips : 6406.14
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
next prev parent reply other threads:[~2005-05-29 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 18:20 CPUFREQ/speedstep on Intel 955X chipset based system Michael Thonke
2005-05-29 19:15 ` Matthias-Christian Ott
2005-05-29 21:53 ` Michael Thonke [this message]
2005-05-31 17:02 ` Venkatesh Pallipadi
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=429A39BF.3020005@gmail.com \
--to=iogl64nx@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.christian@tiscali.de \
/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