Hi all,
I have a lot of trouble to bring the kernel 2.6.8-1 to detect my dothan
processor.
It's a Pentium M Dothan B0 version, 1.7Ghz/600Mhz.
The BIOS is DELL's D800 Bios version 09.
I added 3 patches:
cpufreq-speedstep-dothan-3.patch :add correct frequency table in speedstep.c
dothan-speedstep-fix.patch : add correct Level2 cache
bk-cpufreq.patch : from http://linux-dj.bkbits.net/cpufreq
I added a lot of output in speedstep-centrino.c, acpi/processor.c to track the
problem.
I notice that my computer is running always in the lowest speed evenif I'm
stressing it... All ouputs I added show me that Speedstep isn't the cause,
neither CPUFreq but while CPUFreq calls all notifiers, acpi/processor.c's
CPUFREQ_INCOMPATIBLE change the max speed to the lowest evenif during
cpufreq_acpi_cpu_init the max speed is well detected.
Seems to be like it's coz at boot time the kernel doesn't detect correctly the
max speed.
dmesg shows me that a 600Mhz processor has been detected only and not 1.7Ghz.
(on my D600 pentium M not dothan, it detects correctly 1.6Ghz)
is there a fix for that ?
is it a known bug ?
thx for all help I can get,
best regards,
michel.
[email protected] wrote:
>
> Hi all,
>
> I have a lot of trouble to bring the kernel 2.6.8-1 to detect my dothan
> processor.
> It's a Pentium M Dothan B0 version, 1.7Ghz/600Mhz.
> The BIOS is DELL's D800 Bios version 09.
>
> I added 3 patches:
> cpufreq-speedstep-dothan-3.patch :add correct frequency table in speedstep.c
> dothan-speedstep-fix.patch : add correct Level2 cache
> bk-cpufreq.patch : from http://linux-dj.bkbits.net/cpufreq
>
> I added a lot of output in speedstep-centrino.c, acpi/processor.c to track the
> problem.
>
> I notice that my computer is running always in the lowest speed evenif I'm
> stressing it... All ouputs I added show me that Speedstep isn't the cause,
> neither CPUFreq but while CPUFreq calls all notifiers, acpi/processor.c's
> CPUFREQ_INCOMPATIBLE change the max speed to the lowest evenif during
> cpufreq_acpi_cpu_init the max speed is well detected.
> Seems to be like it's coz at boot time the kernel doesn't detect correctly the
> max speed.
> dmesg shows me that a 600Mhz processor has been detected only and not 1.7Ghz.
> (on my D600 pentium M not dothan, it detects correctly 1.6Ghz)
>
> is there a fix for that ?
> is it a known bug ?
>
> thx for all help I can get,
Sounds like you've chosen powersave as the default power governor in
your config. Change it to performance or modify it manually in
/sys/devices.... cpufreq/scaling_governor
(cant remember the exact position; you'll find it)
cat the output of that file and see if it says powersave performance or
ondemand. You can manually change it from one to the other, or set
either powersave or performance in your config during kernel config.
Cheers,
Con
I already tried to put all scaling_govenors... nothing changed... coz
scaling_max_freq is set to 600000 and not to 1700000. ;(
Michel.
Selon Con Kolivas <[email protected]>:
> [email protected] wrote:
> >
> > Hi all,
> >
> > I have a lot of trouble to bring the kernel 2.6.8-1 to detect my dothan
> > processor.
> > It's a Pentium M Dothan B0 version, 1.7Ghz/600Mhz.
> > The BIOS is DELL's D800 Bios version 09.
> >
> > I added 3 patches:
> > cpufreq-speedstep-dothan-3.patch :add correct frequency table in
> speedstep.c
> > dothan-speedstep-fix.patch : add correct Level2 cache
> > bk-cpufreq.patch : from http://linux-dj.bkbits.net/cpufreq
> >
> > I added a lot of output in speedstep-centrino.c, acpi/processor.c to track
> the
> > problem.
> >
> > I notice that my computer is running always in the lowest speed evenif I'm
> > stressing it... All ouputs I added show me that Speedstep isn't the cause,
> > neither CPUFreq but while CPUFreq calls all notifiers, acpi/processor.c's
> > CPUFREQ_INCOMPATIBLE change the max speed to the lowest evenif during
> > cpufreq_acpi_cpu_init the max speed is well detected.
> > Seems to be like it's coz at boot time the kernel doesn't detect correctly
> the
> > max speed.
> > dmesg shows me that a 600Mhz processor has been detected only and not
> 1.7Ghz.
> > (on my D600 pentium M not dothan, it detects correctly 1.6Ghz)
> >
> > is there a fix for that ?
> > is it a known bug ?
> >
> > thx for all help I can get,
>
> Sounds like you've chosen powersave as the default power governor in
> your config. Change it to performance or modify it manually in
> /sys/devices.... cpufreq/scaling_governor
> (cant remember the exact position; you'll find it)
>
> cat the output of that file and see if it says powersave performance or
> ondemand. You can manually change it from one to the other, or set
> either powersave or performance in your config during kernel config.
>
> Cheers,
> Con
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Here I'm puting some more informations:
[root@localhost root]# cat cpuinfo.txt
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.70GHz
stepping : 6
cpu MHz : 599.639
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush
dts acpi mmx fxsr sse sse2 ss tm pbe tm2 est
bogomips : 1183.74
------------------------------------------------------------------------------
2.6.8-1.521.poseidon.root: is my own built with latest acpi fix and the 3 dothan
patches...
[root@localhost root]# cat dmesg
Linux version 2.6.8-1.521.poseidon.root (gcc version 3.3.3 20040412 (Red Hat
Linux 3.3.3-7)) #1 Thu Oct 7 15:23:43 CEST 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
BIOS-e820: 0000000000100000 - 000000001ffae000 (usable)
BIOS-e820: 000000001ffae000 - 0000000020000000 (reserved)
BIOS-e820: 00000000feda0000 - 00000000fee00000 (reserved)
BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
zapping low mappings.
On node 0 totalpages: 130990
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126894 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 DELL ) @ 0x000fdf00
ACPI: RSDT (v001 DELL CPi R 0x27d40903 ASL 0x00000061) @ 0x1fff0000
ACPI: FADT (v001 DELL CPi R 0x27d40903 ASL 0x00000061) @ 0x1fff0400
ACPI: ASF! (v016 DELL CPi R 0x27d40903 ASL 0x00000061) @ 0x1fff0800
ACPI: BOOT (v001 DELL CPi R 0x27d40903 ASL 0x00000061) @ 0x1fff07c0
ACPI: DSDT (v001 INT430 SYSFexxx 0x00001001 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
Built 1 zonelists
Kernel command line: ro root=/dev/hda5 quiet acpi=on apm=off
mapped 4G/4G trampoline to ffff3000.
Initializing CPU#0
CPU 0 irqstacks, hard=023ca000 soft=023c9000
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 599.639 MHz processor.
As u can see at boottime the processor detected is only a 600Mhz instead 1.7Ghz.
on my D600 pentium M not Dothan, here it's written 1.6Ghz.
I think this is the reason that bring ACPI cpufreq checker to reduce the max
spped to 600mhz.
is there a fix ??
Quoting Con Kolivas <[email protected]>:
> [email protected] wrote:
> >
> > Hi all,
> >
> > I have a lot of trouble to bring the kernel 2.6.8-1 to detect my dothan
> > processor.
> > It's a Pentium M Dothan B0 version, 1.7Ghz/600Mhz.
> > The BIOS is DELL's D800 Bios version 09.
> >
> > I added 3 patches:
> > cpufreq-speedstep-dothan-3.patch :add correct frequency table in
> speedstep.c
> > dothan-speedstep-fix.patch : add correct Level2 cache
> > bk-cpufreq.patch : from http://linux-dj.bkbits.net/cpufreq
> >
> > I added a lot of output in speedstep-centrino.c, acpi/processor.c to track
> the
> > problem.
> >
> > I notice that my computer is running always in the lowest speed evenif I'm
> > stressing it... All ouputs I added show me that Speedstep isn't the cause,
> > neither CPUFreq but while CPUFreq calls all notifiers, acpi/processor.c's
> > CPUFREQ_INCOMPATIBLE change the max speed to the lowest evenif during
> > cpufreq_acpi_cpu_init the max speed is well detected.
> > Seems to be like it's coz at boot time the kernel doesn't detect correctly
> the
> > max speed.
> > dmesg shows me that a 600Mhz processor has been detected only and not
> 1.7Ghz.
> > (on my D600 pentium M not dothan, it detects correctly 1.6Ghz)
> >
> > is there a fix for that ?
> > is it a known bug ?
> >
> > thx for all help I can get,
>
> Sounds like you've chosen powersave as the default power governor in
> your config. Change it to performance or modify it manually in
> /sys/devices.... cpufreq/scaling_governor
> (cant remember the exact position; you'll find it)
>
> cat the output of that file and see if it says powersave performance or
> ondemand. You can manually change it from one to the other, or set
> either powersave or performance in your config during kernel config.
>
> Cheers,
> Con
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hi Dominik,
here the outputs:
::::::::::::::
/proc/acpi/processor/CPU0/info
::::::::::::::
processor id: 0
acpi id: 0
bus mastering control: yes
power management: yes
throttling control: yes
limit interface: yes
::::::::::::::
/proc/acpi/processor/CPU0/limit
::::::::::::::
active limit: P0:T0
user limit: P0:T0
thermal limit: P0:T0
::::::::::::::
/proc/acpi/processor/CPU0/power
::::::::::::::
active state: C2
default state: C1
bus master activity: ffffffff
states:
C1: promotion[C2] demotion[--] latency[000] usage[00011180]
*C2: promotion[C3] demotion[C1] latency[050] usage[00390021]
C3: promotion[--] demotion[C2] latency[050] usage[00004735]
::::::::::::::
/proc/acpi/processor/CPU0/throttling
::::::::::::::
state count: 8
active state: T0
states:
*T0: 00%
T1: 12%
T2: 25%
T3: 37%
T4: 50%
T5: 62%
T6: 75%
T7: 87%::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
::::::::::::::
600000
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
::::::::::::::
1700000
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
::::::::::::::
600000
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
::::::::::::::
1700000 1700000 1700000 1400000 1200000 1000000 800000 600000
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
::::::::::::::
userspace
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
::::::::::::::
600000
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
::::::::::::::
centrino
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
::::::::::::::
userspace
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
::::::::::::::
600000
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
::::::::::::::
600000
::::::::::::::
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
::::::::::::::
600000
scaling_min_freq, scaling_max_freq, scaling_governor and scaling_setseed are rw.
but I can write what I want in these files, nothing change.
michel.
and,
Quoting Dominik Brodowski <[email protected]>:
> Hi,
>
> Can you send me the output of
>
> cat /acpi/processor/*/performance
>
> and
>
> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
>
>
> Also, is this happening while on AC power or while on battery?
>
>
> Thirdly, can you disassemble the DSDT and, if it exists, the SSDT, and check
> for the _PPC method? How to disassemble the DSDT is noted at
> http://acpi.sourceforge.net , for the SSDT check gspr's post on Sep. 20th,
> 12:53 at
> http://forums.gentoo.org/viewtopic.php?t=223411&highlight=ssdt+acpidmp
>
> Dominik
>