Intel DG965RY motherboard Intel Core2 Duo 6300 BIOS version MQ1687 Kernel 2.6.22.1-cfs-v19 #1 SMP PREEMPT x86_64 dmesg snippet: ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Processor [CPU1] (supports 8 throttling states) ACPI Exception (processor_core-0781): AE_NOT_FOUND, Processor Device is not present [20070126] ACPI Exception (processor_core-0781): AE_NOT_FOUND, Processor Device is not present [20070126] dmesg / acpidump to follow
Created attachment 12306 [details] dmesg output
Created attachment 12307 [details] acpidump output
John, Can you attach the .config that you are using and output of lsmod. Thanks, Venki
No modules loaded. It may be a while before I'm able to post the .config. I attempted to update the platform firmware to see whether this could be reproduced with the latest version, but unfortunately it completely zeroed my board beyond repair. So now I'm waiting on the RMA process. I'll get .config to you as soon as I can, though.
I experience the SAME (e.g. no power management, thermal control, cpu speed step...) on Intel D975XBX2 rev.507, BIOS 2674 and/or 2770. OS: Gentoo (amd64 profile) x86_64. Kernel: 2.6.22-gentoo-r2.lim #1 SMP PREEMPT Wed Aug 15 17:08:39 EEST 2007 x86_64 Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz GenuineIntel GNU/Linux Kernel 2: 2.6.19 (stock Gentoo LiveCD). E.g. it had the same problems. lsmod: Module Size Used by nfsd 81128 13 exportfs 4672 1 nfsd i2c_i801 7388 0 e1000 99840 0 nfs 99584 0 lockd 52656 3 nfsd,nfs sunrpc 129672 10 nfsd,nfs,lockd scsi_wait_scan 1280 0 sl811_hcd 10880 0 usbhid 16292 0 ohci_hcd 17476 0 uhci_hcd 20376 0 usb_storage 65024 0 ehci_hcd 26060 0 usbcore 98856 7 sl811_hcd,usbhid,ohci_hcd,uhci_hcd,usb_storage,ehci_hcd
Created attachment 12393 [details] .config for Gentoo kernel 2.6.22-r5. I attach the config used for building custom kernel at my machine.
Can you please set the "CONFIG_CPU_FREQ_DEBUG" option and recompile the kernel and then boot with cpufreq.debug=7 boot option in grub. That will give us some more debug infor for this. My feeling is that the messages below are more of a redherring and not the real issue. ACPI Exception (processor_core-0781): AE_NOT_FOUND, Processor Device is not present [20070126] ACPI Exception (processor_core-0781): AE_NOT_FOUND, Processor Device is not present [20070126] They seem to be coming from extra 2 CPUs that is listed in BIOS and not actually present on the system (BIOS has info about 4 CPUs).
I also verified that kernel 2.6.23-rc2-mm1 not helps. It has the same ACPI version. Btw, there are strange bug - when I overclock processor for testing purposes I see default frequency while Bogomips are bigger. This was not the case on 2.6.19 kernel. Example: # acpitool -c CPU type : Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz Min/Max frequency : 1596/2128 MHz Current frequency : 2128 MHz Frequency governor : performance Freq. scaling driver : acpi-cpufreq Cache size : 4096 KB Bogomips : 6402.61 Bogomips : 6399.29 # of CPU's found : 2 Processor ID : 0 Bus mastering control : yes Power management : no Throttling control : no Limit interface : no Active C-state : C0 C-states (incl. C0) : 2 Processor ID : 1 Bus mastering control : yes Power management : no Throttling control : no Limit interface : no Active C-state : C0 C-states (incl. C0) : 2 As you may see I have ~6400 of Bogomips (3.2 GHz) while by default there are about ~4300 (2,1 GHz). Not sure though who responsible for this - bad kernel or ACPI...
Aliaksandr: Not sure whether you have same problem as John or not. Can you post acpidump and dmesg.
I have added CONFIG_CPU_FREQ_DEBUG (as well as ACPI debug) options to kernel 2.6.23 and rebooted with added line cpufreq.debug=7... Btw, there are still wrongly reported CPU speed while it is 3.2 and I may prove it works faster... (For sure, I have rebooted in the stock mode with the same results) There are results: # dmesg|egrep -i "(acpi|cpufreq)" Command line: root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda7 cpufreq.debug=7 BIOS-e820: 000000007ee72000 - 000000007ef00000 (ACPI NVS) BIOS-e820: 000000007feab000 - 000000007feac000 (ACPI data) BIOS-e820: 000000007feac000 - 000000007fef0000 (ACPI NVS) BIOS-e820: 000000007fef0000 - 000000007fef4000 (ACPI data) BIOS-e820: 000000007fef5000 - 000000007feff000 (ACPI data) ACPI: RSDP 000FE020, 0014 (r0 INTEL ) ACPI: RSDT 7FEFD038, 0048 (r1 INTEL D975XBX2 AD2 1000013) ACPI: FACP 7FEFC000, 0074 (r1 INTEL D975XBX2 AD2 MSFT 1000013) ACPI: DSDT 7FEF8000, 3F11 (r1 INTEL D975XBX2 AD2 MSFT 1000013) ACPI: FACS 7FEAC000, 0040 ACPI: APIC 7FEF7000, 0078 (r1 INTEL D975XBX2 AD2 MSFT 1000013) ACPI: WDDT 7FEF6000, 0040 (r1 INTEL D975XBX2 AD2 MSFT 1000013) ACPI: MCFG 7FEF5000, 003C (r1 INTEL D975XBX2 AD2 MSFT 1000013) ACPI: SSDT 7FEF3000, 01BC (r1 INTEL CpuPm AD2 MSFT 1000013) ACPI: SSDT 7FEF2000, 0175 (r1 INTEL Cpu0Ist AD2 MSFT 1000013) ACPI: SSDT 7FEF1000, 0175 (r1 INTEL Cpu1Ist AD2 MSFT 1000013) ACPI: SSDT 7FEF0000, 0175 (r1 INTEL Cpu2Ist AD2 MSFT 1000013) ACPI: SSDT 7FEAB000, 0175 (r1 INTEL Cpu3Ist AD2 MSFT 1000013) ACPI: Local APIC address 0xfee00000 ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information Kernel command line: root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda7 cpufreq.debug=7 ACPI: Core revision 20070126 tbxface-0598 [00] tb_load_namespace : ACPI Tables successfully acquired evxfevnt-0091 [00] enable : Transition to ACPI mode successful ACPI: bus type pci registered ACPI: EC: Look up EC in DSDT ACPI: Interpreter enabled ACPI: (supports S0 S1 S3) ACPI: Using IOAPIC for interrupt routing PCI: BIOS Bug: MCFG area at f0000000 is not reserved in ACPI motherboard resources PM: Adding info for acpi:LNXSYSTM:00 PM: Adding info for acpi:LNXPWRBN:00 PM: Adding info for acpi:ACPI0007:00 PM: Adding info for acpi:ACPI0007:01 PM: Adding info for acpi:ACPI0007:02 PM: Adding info for acpi:ACPI0007:03 PM: Adding info for acpi:device:00 PM: Adding info for acpi:PNP0C0E:00 PM: Adding info for acpi:PNP0A03:00 PM: Adding info for acpi:PNP0C02:00 PM: Adding info for acpi:device:01 PM: Adding info for acpi:device:02 PM: Adding info for acpi:PNP0C0F:00 PM: Adding info for acpi:PNP0C0F:01 PM: Adding info for acpi:PNP0C0F:02 PM: Adding info for acpi:PNP0C0F:03 PM: Adding info for acpi:PNP0C0F:04 PM: Adding info for acpi:PNP0C0F:05 PM: Adding info for acpi:PNP0C0F:06 PM: Adding info for acpi:PNP0C0F:07 PM: Adding info for acpi:PNP0200:00 PM: Adding info for acpi:PNP0B00:00 PM: Adding info for acpi:PNP0000:00 PM: Adding info for acpi:PNP0C04:00 PM: Adding info for acpi:PNP0100:00 PM: Adding info for acpi:PNP0800:00 PM: Adding info for acpi:PNP0C02:01 PM: Adding info for acpi:PNP0C02:02 PM: Adding info for acpi:device:03 PM: Adding info for acpi:device:04 PM: Adding info for acpi:device:05 PM: Adding info for acpi:device:06 PM: Adding info for acpi:device:07 PM: Adding info for acpi:device:08 PM: Adding info for acpi:PNP0003:00 PM: Adding info for acpi:device:09 PM: Adding info for acpi:device:0a PM: Adding info for acpi:device:0b PM: Adding info for acpi:device:0c PM: Adding info for acpi:device:0d PM: Adding info for acpi:device:0e PM: Adding info for acpi:device:0f PM: Adding info for acpi:device:10 PM: Adding info for acpi:device:11 PM: Adding info for acpi:device:12 PM: Adding info for acpi:device:13 PM: Adding info for acpi:device:14 PM: Adding info for acpi:device:15 PM: Adding info for acpi:device:16 PM: Adding info for acpi:device:17 PM: Adding info for acpi:device:18 PM: Adding info for acpi:device:19 PM: Adding info for acpi:device:1a PM: Adding info for acpi:LNXTHERM:00 ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 *9 10 11 12) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 *9 10 11 12) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 *11 12) pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 9 devices ACPI: ACPI bus type pnp unregistered PCI: Using ACPI for IRQ routing ACPI: PCI Interrupt 0000:04:04.0[A] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:00:1c.5[B] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18 ACPI: Power Button (FF) [PWRF] ACPI: Sleep Button (CM) [SLPB] ACPI Exception (processor_core-0791): AE_NOT_FOUND, Processor Device is not present [20070126] ACPI Exception (processor_core-0791): AE_NOT_FOUND, Processor Device is not present [20070126] cpuidle: driver acpi_idle failed to attach to cpu 1 cpuidle: driver acpi_idle failed to attach to cpu 0 ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:00:1f.2[B] -> <7>PM: Adding info for No Bus:target0:0:29 acpi-cpufreq: acpi_cpufreq_init acpi-cpufreq: acpi_cpufreq_early_init cpufreq-core: trying to register driver acpi-cpufreq cpufreq-core: adding CPU 0 acpi-cpufreq: acpi_cpufreq_cpu_init acpi-cpufreq: HARDWARE addr space acpi-cpufreq: get_cur_freq_on_cpu (0) acpi-cpufreq: get_cur_val = 100665380 acpi-cpufreq: cur freq = 2128000 acpi-cpufreq: CPU0 - ACPI performance management activated. acpi-cpufreq: *P0: 2128 MHz, 89000 mW, 10 uS acpi-cpufreq: P1: 1596 MHz, 55269 mW, 10 uS cpufreq-core: setting new policy for CPU 0: 1596000 - 2128000 kHz acpi-cpufreq: acpi_cpufreq_verify acpi-cpufreq: acpi_cpufreq_verify cpufreq-core: new min and max freqs are 1596000 - 2128000 kHz cpufreq-core: governor switch cpufreq-core: __cpufreq_governor for CPU 0, event 1 cpufreq-core: target for CPU 0: 2128000 kHz, relation 1 acpi-cpufreq: acpi_cpufreq_target 2128000 (0) acpi-cpufreq: Called after resume, resetting to P0 cpufreq-core: notification 0 of frequency transition to 2128000 kHz cpufreq-core: notification 1 of frequency transition to 2128000 kHz cpufreq-core: governor: change or update limits cpufreq-core: __cpufreq_governor for CPU 0, event 3 cpufreq-core: target for CPU 0: 2128000 kHz, relation 1 acpi-cpufreq: acpi_cpufreq_target 2128000 (0) acpi-cpufreq: Already at target state (P0) cpufreq-core: initialization complete cpufreq-core: adding CPU 1 acpi-cpufreq: acpi_cpufreq_cpu_init acpi-cpufreq: HARDWARE addr space acpi-cpufreq: get_cur_freq_on_cpu (1) acpi-cpufreq: get_cur_val = 100665380 acpi-cpufreq: cur freq = 2128000 acpi-cpufreq: CPU1 - ACPI performance management activated. acpi-cpufreq: *P0: 2128 MHz, 89000 mW, 10 uS acpi-cpufreq: P1: 1596 MHz, 55269 mW, 10 uS cpufreq-core: setting new policy for CPU 1: 1596000 - 2128000 kHz acpi-cpufreq: acpi_cpufreq_verify acpi-cpufreq: acpi_cpufreq_verify cpufreq-core: new min and max freqs are 1596000 - 2128000 kHz cpufreq-core: governor switch cpufreq-core: __cpufreq_governor for CPU 1, event 1 cpufreq-core: target for CPU 1: 2128000 kHz, relation 1 acpi-cpufreq: acpi_cpufreq_target 2128000 (1) acpi-cpufreq: Called after resume, resetting to P0 cpufreq-core: notification 0 of frequency transition to 2128000 kHz cpufreq-core: notification 1 of frequency transition to 2128000 kHz cpufreq-core: governor: change or update limits cpufreq-core: __cpufreq_governor for CPU 1, event 3 cpufreq-core: target for CPU 1: 2128000 kHz, relation 1 acpi-cpufreq: acpi_cpufreq_target 2128000 (1) acpi-cpufreq: Already at target state (P0) cpufreq-core: initialization complete cpufreq-core: driver acpi-cpufreq up and running cpufreq-core: trying to register driver centrino cpufreq-core: trying to register driver p4-clockmod ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 23 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 23 ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19 P.S. Please, let me know how to get acpidump output.
Created attachment 12395 [details] acpidump from /proc/acpi/dsdt
Hmm. I do see acpi-cpufreq: *P0: 2128 MHz, 89000 mW, 10 uS acpi-cpufreq: P1: 1596 MHz, 55269 mW, 10 uS So, cpufreq and ondemand must be alive and running on this system. Do you see anything at all in /sys/devices/system/cpu/cpu*/cpufreq/
Yes, I see many things at /sys/devices/system/cpu/cpu*/cpufreq/. But: 1) It reports wrong frequency (while understand higher Bogomips) ls -la /sys/devices/system/cpu/cpu0/cpufreq/ итого 0 drwxr-xr-x 3 root root 0 Авг 16 03:02 ./ drwxr-xr-x 7 root root 0 Авг 16 03:02 ../ -r--r--r-- 1 root root 4096 Авг 16 03:02 affected_cpus -r-------- 1 root root 4096 Авг 16 03:02 cpuinfo_cur_freq -r--r--r-- 1 root root 4096 Авг 16 03:02 cpuinfo_max_freq -r--r--r-- 1 root root 4096 Авг 16 03:02 cpuinfo_min_freq -r--r--r-- 1 root root 4096 Авг 16 03:02 scaling_available_frequencies -r--r--r-- 1 root root 4096 Авг 16 03:02 scaling_available_governors -r--r--r-- 1 root root 4096 Авг 16 03:02 scaling_cur_freq -r--r--r-- 1 root root 4096 Авг 16 03:02 scaling_driver -rw-r--r-- 1 root root 4096 Авг 16 03:02 scaling_governor -rw-r--r-- 1 root root 4096 Авг 16 03:02 scaling_max_freq -rw-r--r-- 1 root root 4096 Авг 16 03:02 scaling_min_freq drwxr-xr-x 2 root root 0 Авг 16 03:02 stats/ 2) There still no possibility to view CPU temperature (the main thing for me...). # ls -la /proc/acpi/thermal_zone/ итого 0 dr-xr-xr-x 2 root root 0 Авг 16 03:03 ./ dr-xr-xr-x 10 root root 0 Авг 16 02:35 ../
Any thoughts on this?
I am not understanding the wrong frequency part. The CPU brand string is saying Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz and cpufreq is showning the same freq as max. 2,128 MHz. So what is the problem? If you are referring to overclocking and then frequency reported is wrong. Yes. That is expected as BIOS does not know about your overclocking and still gives the same frequency table as before. Basically, platform BIOS is not supporting overclocking. Thermal zone: Most probably BIOS is not exporting any methods for thermal zone. Can you attach your acpidump (using pmtools).
Thanks for the info. 1.The bogomips has no problem. The value of bogomips should be double CPU frequency according to the algorithm of calibrate_delay. If you doubt the bogomips,please refer to the function of calibrate_delay, on which there exists detailed description. 2. The error message of AE_NOT_FOUND can be ignored. Four cpus are defined in the BIOS(ACPI tables), but there exists only two CPUS. In the initialization of ACPI the system will check whether the defined CPU exists or not. If the defined CPU doesn't exist , the system will print the promote info of AE_NOT_FOUND. It has no effect on the system. >
Aliaksandr, I think the only bug on your d975xbx2 is the existence of these messages: ACPI Exception (processor_core-0791): AE_NOT_FOUND, Processor Device is not present [20070126] ACPI Exception (processor_core-0791): AE_NOT_FOUND, Processor Device is not present [20070126] which should probably just be deleted in this type of case. Your BIOS suports a quad-core processor, but your board currently has only a dual-core processor installed. I have a D975XBX2 (I'm typing this from it now:-) Processor speed control via cpufreq is working properly. The fact that the BIOS doesn't know that you've over-clocked your board is also normal. This is analogous to putting large tires on your car and getting a speeding ticket because your car is moving at 60 when its built-in speedometer only really knows about tire revolutions and reports 55... Empty /proc/acpi/thermal_zone is also normal on this board. The board doesn't have any ACPI thermal zone support. The fan is controlled by the motherboard without involving ACPI or Linux. Note that this is done using sensors on the board and you may be able to observe temperature and fan speeds by loading some sensors with CONFIG_HWMON -- but that has nothing to do with this bug report. It seems that John Karp's bug is also the error messages that Linux reports when a dual-core processor is installed on a quad-core capable motherboard. Is that it or is there some functional problem in this bug report?
There is no functional problem that I've seen. My complaint is that there is an error message for a normal condition. I don't know whether to blame the Intel firmware folks or the Intel linux/acpi folks, but hopefully they get along well enough that it doesn't matter :-)
Older kernel 2.6.19 show full overcloacked frequency. Newer 2.6.22 doesn't. It is a bug. Not sure either kernel or acpi. What about cpufreqd - it also should see real (overcloacked) frequency and then allow it to be changed via multiplier (8 down to 6). It is how things worked on older boards with other Intel CPUs and older 2.6 kernels.
Confirmed that kernel 2.6.16 show proper frequency (it however fail to boot with 3ware but it is something I need to work out). So something has been broken during transition from 2.6.17 kernel to newer ones... Perhaps ACPI broken in newer kernels as well...
Len Brown said in #17: > I think the only bug on your d975xbx2 is the existence of these messages: > ACPI Exception (processor_core-0791): AE_NOT_FOUND, Processor Device is not > present [20070126] > ACPI Exception (processor_core-0791): AE_NOT_FOUND, Processor Device is not > present [20070126] > which should probably just be deleted in this type of case. > Your BIOS suports a quad-core processor, but your board > currently has only a dual-core processor installed. I also have these messages (2.6.23-rc7, Intel D945GCZ board), probably for the same reason as the system works perfectly. Is the option to suppress them still being considered? An alternative could be to include the processor number (or core number or whatever) in the message. With that a user could at least think "I only have two cores, so not finding 3 and 4 is OK". The current messages are somewhat scary and confusing, and are bound to lead to loads of time wasted googling and on forums, BTSs. P.S. "neededinfo" tag on this report seems obsolete.
To supress the Processor Device is not present message, please see bug# 8570.
Hi, Aliaksandr I agreed with what Venki said in the comment #15. The problem in comment #8 is that /proc/cpuinfo can't display the cpu frequency correctly after the acpi-cpufreq driver is loaded. The root cause is listed in the following: 1. After the cpufreq module is loaded, the /proc/cpuinfo will display the cpu frequency obtained from the P-states table. 2. After the cpu is overclocked, the system will work in overclocked frequency. But unfortunately OSPM doens't know about the overclocking and continues to display the cpu frequency obtained from the P-state table. So /proc/cpuinfo reports the wrong cpufrequency.
Hi, Aliaksandr The folliwng is added for the comment #23: 1. In the boot phase OSPM will detect the cpu frequency and store the result to cpu_khz. The /proc/info will use the cpu_khz to display the cpu frequency before the cpufreq module is loaded. 2. In the previous kernel(for example 2.6.12) the /proc/info continues using the cpu_khz to display the cpu frequency after the cpufreq module is loaded. When the P-state is changed, the OSPM will update the cpu_khz using the function of cpufreq_scale.In this case even when the cpu is overclocked the OSPM can update the cpu_khz correctly. In smp system when the CPUs run in different p-states , the /proc/info for all cpus will display the same frequency.It is uncorrect. Of course there is no problem when the all cpus run in the same P-states. So in the current kernel the above method is discarded and the /proc/info displays the cpu freqency obtained from the P-state table. It can still display the cpu frequency correctly when all cpus run in different p-states. Of course there appears a new problem that OS can't display the cpu frequency correctly when overclocked.The problem can be solved by adding frequency ratio for every cpu. The frequency ration can be defined as : ratio = cpu_max_khz / cpu_khz_p0_states cpu_max_khz is calculated in the function of calibrate_delay. cpu_khz_p0_states is the max frequency in P0-states. But I think that it is unnecessary to fix this problem because the floating calculation will be involved.(The floating calculation can be avoided if two variables are added for every cpu. And it is complex).
Huh?? That new title has nothing to do with the original bug I reported... and why 'rejected will not fix'? Is the patch in bug #8570 not going to be applied upstream?
Hi, John The original bug is duplicated of bug #8570. The patch will be applied upstream. Now there is another problem in the comment #8. So it is given a new title and marked as 'rejected will not fix'. Thanks.