[Bug 387207] New: Processor is overheated
https://bugzilla.novell.com/show_bug.cgi?id=387207 Summary: Processor is overheated Product: openSUSE 11.0 Version: Factory Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: j.reitsma@hccnet.nl QAContact: qa@suse.de Found By: Beta-Customer The processor of my Acer 1710 laptop is much hotter running 11.0b3 then when running 10.3 (or, for that matter, 10.0 trough 10.2). Temp when running only one desktop, and no applications beside that is up to 75 degrees, where some 40 - 45 was normal. Changing to runlevel 1 doesn't lower the temperature apparently, so I file it under the Basesystem component. cat /proc/cpuinfo gives processor : 0
vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.80GHz stepping : 9 cpu MHz : 2793.029 cache size : 512 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 pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr bogomips : 5591.59 clflush size : 64
This cpu doesn't support CPU frequency scaling, so there's cause nor solution to find. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387207
User sboyce@blueyonder.co.uk added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c1
Sid Boyce
https://bugzilla.novell.com/show_bug.cgi?id=387207
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c2
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User sboyce@blueyonder.co.uk added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c3
--- Comment #3 from Sid Boyce
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c4
--- Comment #4 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c5
--- Comment #5 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c6
--- Comment #6 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c7
--- Comment #7 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User rui.zhang@intel.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c8
--- Comment #8 from Rui Zhang
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c9
--- Comment #9 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User sboyce@blueyonder.co.uk added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c10
--- Comment #10 from Sid Boyce
https://bugzilla.novell.com/show_bug.cgi?id=387207
User sboyce@blueyonder.co.uk added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c11
--- Comment #11 from Sid Boyce
https://bugzilla.novell.com/show_bug.cgi?id=387207
User rui.zhang@intel.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c12
--- Comment #12 from Rui Zhang
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c13
--- Comment #13 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c14
--- Comment #14 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c15
--- Comment #15 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c16
--- Comment #16 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c17
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c18
--- Comment #18 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c19
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User funtasyspace@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c20
Jörg Hermsdorf
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c21
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User funtasyspace@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c22
--- Comment #22 from Jörg Hermsdorf
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c23
--- Comment #23 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User tom-osbug@tautologysolutions.ca added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c24
Tom Hui
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c25
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c26
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User pavel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c28
--- Comment #28 from Pavel Machek
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c29
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User j.reitsma@hccnet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c30
--- Comment #30 from Jogchum Reitsma
https://bugzilla.novell.com/show_bug.cgi?id=387207
User funtasyspace@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c31
--- Comment #31 from Jörg Hermsdorf
https://bugzilla.novell.com/show_bug.cgi?id=387207
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c32
Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=387207
User pavel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c33
--- Comment #33 from Pavel Machek
https://bugzilla.novell.com/show_bug.cgi?id=387207
User tom-osbug@tautologysolutions.ca added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c34
--- Comment #34 from Tom Hui
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c35
Thomas Renninger
From the huge difference, I expect we have a CPU problem here. Possibly graphics cards, but I very much expect the CPU.
The first report states a Pentium 4 in the description, so it cannot be cpufreq. It looks like the processor sleep states (C-states) are not entered correctly. The Pentium 4 probably has no deeper sleep states (only C1), it could be that something is still spinning instead of entering the idle function, like if idle=poll is passed? Can you do: echo 1 > /proc/sys/kernel/sysrq Then push the SysRq button (near Scroll/Lock button) and also "P" Do this when the machine is idle. You should then see a backtrace at the end of: dmesg |less It should look like: ----------------- RIP: 0010:[<ffffffff80221970>] [<ffffffff80221970>] native_safe_halt+0x6/0x8 .. Call Trace: Inexact backtrace: [<ffffffff8020b115>] ? default_idle+0x43/0x78 [<ffffffff8020b0d2>] ? default_idle+0x0/0x78 [<ffffffff8020b08a>] ? cpu_idle+0x92/0xda [<ffffffff804447fc>] ? start_secondary+0x408/0x417 ----------------- Important is the RIP line and the backtrace (like above). If you are not in the default_idle function, try again some more times when no process is running. Can you attach the stripped output like above. The C-states statistics are exported to userspace via: /proc/acpi/processor/*/power Please also run powertop and tell us if you see any noticable message/warning. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387207
User funtasyspace@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c36
--- Comment #36 from Jörg Hermsdorf
Everyone was experiencing extremely high CPU temp or overheat and fans running > continuously at full speed. Yes, the fan of my ThinkPad T60p became a victim of this bug :( I had to send it in to get it repaired.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387207
User tom-osbug@tautologysolutions.ca added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c37
--- Comment #37 from Tom Hui
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c38
Thomas Renninger
The only thing that seems unusual is that every so often ACPI generated a large number of interrupts. Yes, this is definetly wronng. Do you see kacpid consume a lot cpu time in top? This could be related to bug #401740. Hmm, but there it only happens after suspend. ACPI daemone running in a loop can also be something else. do (when this happens): echo 0x1F >/sys/module/acpi/parameters/debug_level;sleep 1;echo 0x3 /sys/module/acpi/parameters/debug_level (Be careful, not C&Ped, path might not be 100% correct). and send dmesg output
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387207
User tom-osbug@tautologysolutions.ca added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c39
--- Comment #39 from Tom Hui
/sys/module/acpi/parameters/debug_level" and ran "powertop". Then just waited for the ACPI interrupts to show a spike in the Top causes for wakeups section. When that happened, I quit "powertop" and captured the "dmesg" output.
I don't know much about ACPI so the output is pretty meaningless to me. Hopefully it will be helpful to you guys. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c40
--- Comment #40 from Thomas Renninger
Then just waited for the ACPI interrupts to show a spike How often does that happen? Do the interrupts also calm down for a while, do you have to wait for something that triggers the irq storm? You can also use: watch -n1 cat /proc/interrupts The ACPI interrupts should increase rapidly? Can you give an estimation how much there are per second by e.g. cat /proc/interrupts;sleep 10; cat /proc/interrupts
Does it help if you unload or better not load the battery module? Best copy away battery.ko temporarily: mv /lib/modules/`uname -r`/kernel/drivers/acpi/battery.ko /lib/modules reboot. Do not forget to move the battery.ko driver back when you finished tests(especially if it is not the problem or you will miss battery status): mv /lib/modules/battery.ko /lib/modules/`uname -r`/kernel/drivers/acpi/battery.ko I wonder if this is really related to battery or whether we still do not see what kind of ACPI interrupts/GPEs are processed. If the problem persists, maybe you can again increase acpi debug level, but this time set to 0x21f instead 0x1f (with battery still unloaded). Better copy away the relvant parts from /var/log/messages now, then we have the time how often things happen. You may want to do: logger XXXXXXXXXX before the commands you increase acpi_debug level. Then you can search /var/log/messages for it and know when you started debugging. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=387207
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c41
--- Comment #41 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=387207
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c42
--- Comment #42 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=387207
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c43
--- Comment #43 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=387207
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c44
--- Comment #44 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c45
--- Comment #45 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c46
--- Comment #46 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c47
Thomas Renninger
participants (1)
-
bugzilla_noreply@novell.com