[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
thermald is the defacto solution to this in Trusty+, I've added a
Wikipage to describe how to install and configure this daemon:
https://wiki.ubuntu.com/Kernel/PowerManagement/ThermalIssues
I think this addresses the bug, so I'm going to close it.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu should handle hot CPUs by taking preemptive action and
warning users
Status in “linux” package in Ubuntu:
Fix Released
Bug description:
If the kernel detects your CPU(s) is/are too hot currently (see bug
751689), the kernel calls /sbin/poweroff. This will provide a
graceful system shutdown. If /sbin/poweroff fails, the kernel just
forcibly shuts the system down. However, both strategies are last
resorts and are called when the system temperature has reached a
critical level.
However, the kernel seems to emit an ACPI event when it detects the
CPU(s) are merely hot. I suggest we consider adding an acpi hook to
attempt to avoid a critical scenario.
Currently, the user experience when critical gets hit is not good -
the system just shuts down with no warning whatsoever. This is
alarming in the extreme to users.
Ideas:
- proactively attempt to kill off power hogging processes (use powertop?)
- ramp fans to maximum and present the user with a warning window explaining
what is happening.
- present the user with a window of high-power processes and ask *them* to
select the processes they'd like to kill off in an effort
to avoid a system shutdown.
Problems:
- it is unclear (to me atleast) how close (in terms of degrees
centigrade) hot and critical are (is it different for all CPUs ?)
As such, it is unclear how long (time) it might take for a system that
is hot to go critical and just shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: acpi-support 0.140
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 17:22:09 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3788 F pulseaudio
/dev/snd/controlC0: james 3788 F pulseaudio
james 10267 F alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa214c,00100302
HDA:14f12c06,17aa2122,0010'
Controls : 9
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6IHT37WW-1.12'
Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
RelatedPackageVersions:
linux-restricted-modules-3.2.0-18-generic-pae N/A
linux-backports-modules-3.2.0-18-generic-pae N/A
linux-firmware1.71
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-18-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
Hi Colin - thanks, yes running thermald has improved the situation
immensely! I do still very occasionally see overheats, although they are
extremely rare now and I suspect may be more related to my fans needing
a clean :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu should handle hot CPUs by taking preemptive action and
warning users
Status in “linux” package in Ubuntu:
Fix Released
Bug description:
If the kernel detects your CPU(s) is/are too hot currently (see bug
751689), the kernel calls /sbin/poweroff. This will provide a
graceful system shutdown. If /sbin/poweroff fails, the kernel just
forcibly shuts the system down. However, both strategies are last
resorts and are called when the system temperature has reached a
critical level.
However, the kernel seems to emit an ACPI event when it detects the
CPU(s) are merely hot. I suggest we consider adding an acpi hook to
attempt to avoid a critical scenario.
Currently, the user experience when critical gets hit is not good -
the system just shuts down with no warning whatsoever. This is
alarming in the extreme to users.
Ideas:
- proactively attempt to kill off power hogging processes (use powertop?)
- ramp fans to maximum and present the user with a warning window explaining
what is happening.
- present the user with a window of high-power processes and ask *them* to
select the processes they'd like to kill off in an effort
to avoid a system shutdown.
Problems:
- it is unclear (to me atleast) how close (in terms of degrees
centigrade) hot and critical are (is it different for all CPUs ?)
As such, it is unclear how long (time) it might take for a system that
is hot to go critical and just shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: acpi-support 0.140
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 17:22:09 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3788 F pulseaudio
/dev/snd/controlC0: james 3788 F pulseaudio
james 10267 F alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa214c,00100302
HDA:14f12c06,17aa2122,0010'
Controls : 9
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6IHT37WW-1.12'
Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
RelatedPackageVersions:
linux-restricted-modules-3.2.0-18-generic-pae N/A
linux-backports-modules-3.2.0-18-generic-pae N/A
linux-firmware1.71
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-18-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
dmi.bios.date: 08/27/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET72WW (1.32 )
Re: [Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
On 07/03/14 10:23, James Hunt wrote:
Hi Colin - thanks, yes running thermald has improved the situation
immensely! I do still very occasionally see overheats, although they are
extremely rare now and I suspect may be more related to my fans needing
a clean :-)
One can tweak the default thermald config to start throttling back at a
lower temperature if required. So it may need some machine specific
modification if it keeps on occurring.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu should handle hot CPUs by taking preemptive action and
warning users
Status in “linux” package in Ubuntu:
Fix Released
Bug description:
If the kernel detects your CPU(s) is/are too hot currently (see bug
751689), the kernel calls /sbin/poweroff. This will provide a
graceful system shutdown. If /sbin/poweroff fails, the kernel just
forcibly shuts the system down. However, both strategies are last
resorts and are called when the system temperature has reached a
critical level.
However, the kernel seems to emit an ACPI event when it detects the
CPU(s) are merely hot. I suggest we consider adding an acpi hook to
attempt to avoid a critical scenario.
Currently, the user experience when critical gets hit is not good -
the system just shuts down with no warning whatsoever. This is
alarming in the extreme to users.
Ideas:
- proactively attempt to kill off power hogging processes (use powertop?)
- ramp fans to maximum and present the user with a warning window explaining
what is happening.
- present the user with a window of high-power processes and ask *them* to
select the processes they'd like to kill off in an effort
to avoid a system shutdown.
Problems:
- it is unclear (to me atleast) how close (in terms of degrees
centigrade) hot and critical are (is it different for all CPUs ?)
As such, it is unclear how long (time) it might take for a system that
is hot to go critical and just shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: acpi-support 0.140
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 17:22:09 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3788 F pulseaudio
/dev/snd/controlC0: james 3788 F pulseaudio
james 10267 F alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa214c,00100302
HDA:14f12c06,17aa2122,0010'
Controls : 9
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6IHT37WW-1.12'
Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
RelatedPackageVersions:
linux-restricted-modules-3.2.0-18-generic-pae N/A
linux-backports-modules-3.2.0-18-generic-pae N/A
linux-firmware1.71
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-18-generic-pae i686
UpgradeStatus: Upgraded
[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
One can use a thermald helper script to set the CPU Max temperature on
your machine.
Attached is the script, one has to specify the max temp in milli degrees
C, so for 80 degress C, enter 8, example:
sudo ./thermald_set_pref.sh
[sudo] password for king:
thermald preference
0 : DEFAULT
1 : PERFORMANCE
2 : ENERGY_CONSERVE
3 : DISABLED
4 : CALIBRATE
5 : SET USER DEFINED CPU MAX temp
6 : TERMINATE
Enter thermald preference [1..6]: 5
Enter valid max temp in mill degree celsius 8
** Attachment added: thermald management script
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/955287/+attachment/3968543/+files/thermald_set_pref.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu should handle hot CPUs by taking preemptive action and
warning users
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
If the kernel detects your CPU(s) is/are too hot currently (see bug
751689), the kernel calls /sbin/poweroff. This will provide a
graceful system shutdown. If /sbin/poweroff fails, the kernel just
forcibly shuts the system down. However, both strategies are last
resorts and are called when the system temperature has reached a
critical level.
However, the kernel seems to emit an ACPI event when it detects the
CPU(s) are merely hot. I suggest we consider adding an acpi hook to
attempt to avoid a critical scenario.
Currently, the user experience when critical gets hit is not good -
the system just shuts down with no warning whatsoever. This is
alarming in the extreme to users.
Ideas:
- proactively attempt to kill off power hogging processes (use powertop?)
- ramp fans to maximum and present the user with a warning window explaining
what is happening.
- present the user with a window of high-power processes and ask *them* to
select the processes they'd like to kill off in an effort
to avoid a system shutdown.
Problems:
- it is unclear (to me atleast) how close (in terms of degrees
centigrade) hot and critical are (is it different for all CPUs ?)
As such, it is unclear how long (time) it might take for a system that
is hot to go critical and just shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: acpi-support 0.140
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 17:22:09 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3788 F pulseaudio
/dev/snd/controlC0: james 3788 F pulseaudio
james 10267 F alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa214c,00100302
HDA:14f12c06,17aa2122,0010'
Controls : 9
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6IHT37WW-1.12'
Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
RelatedPackageVersions:
linux-restricted-modules-3.2.0-18-generic-pae N/A
[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
Hmm, I'm not sure why you need to unload the thinkpad acpi driver.
Can you force fan control mode with
options thinkpad_acpi fan_control=1
in a /etc/modprobe.d/ .conf file and this will configure the driver at
boot time.
I also suggest enabling the intel-pstate driver. Ubuntu currently has a
patch to turn this off by default, and it can be enabled by changing
/etc/default/grub and set the following:
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash intel_pstate=enable
then run: sudo update-grub
and reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu should handle hot CPUs by taking preemptive action and
warning users
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
If the kernel detects your CPU(s) is/are too hot currently (see bug
751689), the kernel calls /sbin/poweroff. This will provide a
graceful system shutdown. If /sbin/poweroff fails, the kernel just
forcibly shuts the system down. However, both strategies are last
resorts and are called when the system temperature has reached a
critical level.
However, the kernel seems to emit an ACPI event when it detects the
CPU(s) are merely hot. I suggest we consider adding an acpi hook to
attempt to avoid a critical scenario.
Currently, the user experience when critical gets hit is not good -
the system just shuts down with no warning whatsoever. This is
alarming in the extreme to users.
Ideas:
- proactively attempt to kill off power hogging processes (use powertop?)
- ramp fans to maximum and present the user with a warning window explaining
what is happening.
- present the user with a window of high-power processes and ask *them* to
select the processes they'd like to kill off in an effort
to avoid a system shutdown.
Problems:
- it is unclear (to me atleast) how close (in terms of degrees
centigrade) hot and critical are (is it different for all CPUs ?)
As such, it is unclear how long (time) it might take for a system that
is hot to go critical and just shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: acpi-support 0.140
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 17:22:09 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3788 F pulseaudio
/dev/snd/controlC0: james 3788 F pulseaudio
james 10267 F alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa214c,00100302
HDA:14f12c06,17aa2122,0010'
Controls : 9
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6IHT37WW-1.12'
Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
RelatedPackageVersions:
linux-restricted-modules-3.2.0-18-generic-pae N/A
linux-backports-modules-3.2.0-18-generic-pae N/A
linux-firmware1.71
StagingDrivers: mei
Tags: precise staging
[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
Hi Colin - thanks, I'm now running thermald but cannot really stress my
system due to o/s bug 1268906 (kvm always makes it overheat unless fans
are disengaged. That is currently not possible on my T410 btw due to bug
1268880 - will that impact thermald's abilities?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu should handle hot CPUs by taking preemptive action and
warning users
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
If the kernel detects your CPU(s) is/are too hot currently (see bug
751689), the kernel calls /sbin/poweroff. This will provide a
graceful system shutdown. If /sbin/poweroff fails, the kernel just
forcibly shuts the system down. However, both strategies are last
resorts and are called when the system temperature has reached a
critical level.
However, the kernel seems to emit an ACPI event when it detects the
CPU(s) are merely hot. I suggest we consider adding an acpi hook to
attempt to avoid a critical scenario.
Currently, the user experience when critical gets hit is not good -
the system just shuts down with no warning whatsoever. This is
alarming in the extreme to users.
Ideas:
- proactively attempt to kill off power hogging processes (use powertop?)
- ramp fans to maximum and present the user with a warning window explaining
what is happening.
- present the user with a window of high-power processes and ask *them* to
select the processes they'd like to kill off in an effort
to avoid a system shutdown.
Problems:
- it is unclear (to me atleast) how close (in terms of degrees
centigrade) hot and critical are (is it different for all CPUs ?)
As such, it is unclear how long (time) it might take for a system that
is hot to go critical and just shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: acpi-support 0.140
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 17:22:09 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3788 F pulseaudio
/dev/snd/controlC0: james 3788 F pulseaudio
james 10267 F alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa214c,00100302
HDA:14f12c06,17aa2122,0010'
Controls : 9
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6IHT37WW-1.12'
Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
RelatedPackageVersions:
linux-restricted-modules-3.2.0-18-generic-pae N/A
linux-backports-modules-3.2.0-18-generic-pae N/A
linux-firmware1.71
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-18-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
dmi.bios.date: 08/27/2010
dmi.bios.vendor: LENOVO
[Kernel-packages] [Bug 955287] Re: Ubuntu should handle hot CPUs by taking preemptive action and warning users
@James, I've now packaged up thermald for Trusty, which will do auto
throttling if the CPU is too hot. Perhaps you can give that a spin.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu should handle hot CPUs by taking preemptive action and
warning users
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
If the kernel detects your CPU(s) is/are too hot currently (see bug
751689), the kernel calls /sbin/poweroff. This will provide a
graceful system shutdown. If /sbin/poweroff fails, the kernel just
forcibly shuts the system down. However, both strategies are last
resorts and are called when the system temperature has reached a
critical level.
However, the kernel seems to emit an ACPI event when it detects the
CPU(s) are merely hot. I suggest we consider adding an acpi hook to
attempt to avoid a critical scenario.
Currently, the user experience when critical gets hit is not good -
the system just shuts down with no warning whatsoever. This is
alarming in the extreme to users.
Ideas:
- proactively attempt to kill off power hogging processes (use powertop?)
- ramp fans to maximum and present the user with a warning window explaining
what is happening.
- present the user with a window of high-power processes and ask *them* to
select the processes they'd like to kill off in an effort
to avoid a system shutdown.
Problems:
- it is unclear (to me atleast) how close (in terms of degrees
centigrade) hot and critical are (is it different for all CPUs ?)
As such, it is unclear how long (time) it might take for a system that
is hot to go critical and just shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: acpi-support 0.140
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 17:22:09 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: james 3788 F pulseaudio
/dev/snd/controlC0: james 3788 F pulseaudio
james 10267 F alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 45'
Mixer name : 'Conexant CX20585'
Components : 'HDA:14f15069,17aa214c,00100302
HDA:14f12c06,17aa2122,0010'
Controls : 9
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6IHT37WW-1.12'
Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs
console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
RelatedPackageVersions:
linux-restricted-modules-3.2.0-18-generic-pae N/A
linux-backports-modules-3.2.0-18-generic-pae N/A
linux-firmware1.71
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-18-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
dmi.bios.date: 08/27/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET72WW (1.32 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
