Machine goes into controlled shutdown (possibly overheating) when converting books with calibre
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
I can replicably make my machine shut down (a controlled shutdown, not a pull-the-plug instant shutdown) by encoding books to epub with calibre. The syslog mentions something about overheating. However, high CPU use from other applications (Flash player, as an obvious example, which I often have to kill for high CPU use) does not seem to cause this problem, and it hasn't happened before so I think it may be a regression.
I planned to follow https:/
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.38-6-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6dfc000 irq 48'
Mixer name : 'Silicon Image SiI1392 HDMI'
Components : 'HDA:83847616,
Controls : 31
Simple ctrls : 19
Date: Thu Mar 17 19:33:28 2011
HibernationDevice: RESUME=
MachineType: Dell Inc. XPS M1330
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_US.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: root=UUID=
RelatedPackageV
linux-
linux-
linux-firmware 1.48
SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-01-18 (58 days ago)
WpaSupplicantLog:
dmi.bios.date: 12/26/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0N6705
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: XPS M1330
dmi.sys.vendor: Dell Inc.
Changed in linux (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: |
added: kernel-therm removed: kernel-uncat |
Stuart,
My apologies for the delay responding on this. The team is interested in seeing if the previous mainline kernels exhibit this behavior. Specifically, they want to see if the .38 mainline kernel has the issue, and if so, test .37, etc till it goes away. We want to nail down 2 things, 1) is this something that was fixed and then re-broken? 2) where was the fix/why is it now broken again.
Would you be willing to test the mainline kernels? Information on how is available at https:/ /wiki.ubuntu. com/Kernel/ MainlineBuilds? action= show&redirect= KernelTeam% 2FMainlineBuild s
Thanks!
~JFo