Your message dated Sun, 21 Jun 2009 05:19:36 +0100
with message-id <1245557976.7980.63.ca...@deadeye>
and subject line Re: lm-sensors: Conflict with kernel ACPI temperatures causes
shutdown
has caused the Debian Bug report #530303,
regarding lm-sensors: Conflict with kernel ACPI temperatures causes shutdown
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
530303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530303
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lm-sensors
Version: 1:3.0.2-1+b2
Severity: important
It seems I can cause my system to spontaneously reboot by continually
polling the 'sensors' command (eg. with `watch sensors`) for long periods.
I get the following errors:
May 23 16:10:13 tank kernel: [18847.999540] ACPI: Critical trip point
May 23 16:10:13 tank kernel: [18847.999569] ACPI: Unable to turn cooling device
[ffff8101af06f8b0] 'on'
Sometimes they are repeated, sometimes not. My system turns off shortly
after on its own. This bug has only occurred since I started using
lm-sensors, and I found mention of a similar conflict online, hence my
diagnosis.
Upstream bug at http://www.lm-sensors.org/ticket/2072 I suspect
(closed as WONTFIX, but no warnings are issued, yadda yadda).
Output of lsmod:
parport_pc 31016 0
lp 14724 0
parport 41776 3 ppdev,parport_pc,lp
autofs4 24200 1
ipv6 288328 30
bridge 53544 0
nls_utf8 6272 6
ntfs 188416 2
nls_base 12932 3 cifs,nls_utf8,ntfs
dm_snapshot 19400 0
dm_mirror 20608 0
dm_log 13956 1 dm_mirror
dm_mod 58864 3 dm_snapshot,dm_mirror,dm_log
coretemp 11008 0
w83627ehf 26512 0
hwmon_vid 7296 1 w83627ehf
tun 14084 0
kvm_intel 39776 0
kvm 127464 1 kvm_intel
loop 19468 0
snd_emu10k1_synth 10752 0
joydev 14848 0
wacom 22144 0
snd_emux_synth 36864 1 snd_emu10k1_synth
snd_seq_virmidi 10112 1 snd_emux_synth
snd_seq_midi_emul 10496 1 snd_emux_synth
snd_hda_intel 434904 0
snd_seq_dummy 7428 0
snd_emu10k1 141536 3 snd_emu10k1_synth
snd_seq_oss 33152 0
firmware_class 12544 1 snd_emu10k1
snd_ac97_codec 115416 1 snd_emu10k1
ac97_bus 6272 1 snd_ac97_codec
snd_seq_midi 11072 0
snd_pcm_oss 41760 0
snd_mixer_oss 18816 1 snd_pcm_oss
snd_rawmidi 26784 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi
snd_seq_midi_event 11904 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_pcm 81672 5
snd_hda_intel,snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq 54304 9
snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_seq_device 11668 8
snd_emu10k1_synth,snd_emux_synth,snd_seq_dummy,snd_emu10k1,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd_timer 25744 3 snd_emu10k1,snd_pcm,snd_seq
snd_util_mem 8960 2 snd_emux_synth,snd_emu10k1
i2c_i801 13596 0
emu10k1_gp 7552 0
usb_storage 94528 0
snd_hwdep 12040 2 snd_emux_synth,snd_emu10k1
i2c_core 27936 1 i2c_i801
pcspkr 7040 0
usbhid 45792 0
snd 63688 17
snd_emux_synth,snd_seq_virmidi,snd_hda_intel,snd_emu10k1,snd_seq_oss,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_rawmidi,snd_pcm,snd_seq,snd_seq_device,snd_timer,snd_hwdep
hid 41792 1 usbhid
usblp 16896 0
gameport 17040 2 emu10k1_gp
iTCO_wdt 15696 0
ff_memless 9224 1 usbhid
soundcore 12064 1 snd
snd_page_alloc 13072 3 snd_hda_intel,snd_emu10k1,snd_pcm
button 11680 0
intel_agp 31728 0
evdev 14208 10
ext3 125072 3
jbd 51240 1 ext3
mbcache 12804 1 ext3
sg 36448 0
sr_mod 19652 0
cdrom 37928 1 sr_mod
sd_mod 29376 7
ata_generic 10116 0
ata_piix 22660 6
libata 165472 2 ata_generic,ata_piix
scsi_mod 160760 5 usb_storage,sg,sr_mod,sd_mod,libata
dock 14112 1 libata
ohci1394 32564 0
ide_pci_generic 9220 0 [permanent]
floppy 61672 0
ide_core 128284 1 ide_pci_generic
ieee1394 93816 1 ohci1394
r8169 31492 0
ehci_hcd 36108 0
uhci_hcd 25760 0
thermal 22688 0
processor 42304 1 thermal
fan 9352 0
thermal_sys 17728 3 thermal,processor,fan
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (990, 'stable'), (800, 'testing'), (700, 'unstable'), (600,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.utf8)
Shell: /bin/sh linked to /bin/bash
Versions of packages lm-sensors depends on:
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libsensors4 1:3.0.2-1+b2 library to read temperature/voltag
ii perl 5.10.0-19 Larry Wall's Practical Extraction
ii sed 4.1.5-6 The GNU sed stream editor
lm-sensors recommends no packages.
Versions of packages lm-sensors suggests:
pn i2c-tools <none> (no description available)
pn read-edid <none> (no description available)
pn sensord <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
I do not consider this to be a kernel bug. The hardware monitor in your
system appears to be used by the BIOS. The kernel tries to avoid
conflicting with such use, but the BIOS is not providing the necessary
information to do so. You should be able to read the temperatures via
ACPI using the thermal and thermal_sys drivers instead of using the I2C
drivers.
Ben.
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
