https://bugzilla.kernel.org/show_bug.cgi?id=15946
--- Comment #82 from Xavier Hourcade <public....@xapaho.com> 2012-05-14 22:12:18 --- Created an attachment (id=73296) --> (https://bugzilla.kernel.org/attachment.cgi?id=73296) acpi readings, dump, dmesg and heat watchdog (no shutdown) Here is a first data set, despite the devil being on my side today :) grep . /proc/acpi/*/* grep . /sys/class/thermal/*/* ls -la /proc/acpi/ /proc/acpi/* ls -la /sys/class/thermal/*/* acpidump dmesg sed -n '/May 14 21/{h;b};H;${x;p}' /var/log/messages \ | grep -E "(ºC|temperature|ACPI|\(proc\) stopped|kmsg started)" Fresh booted (now 3.3.5-2.fc16.x86_64), switched tty at KDM login, started my heat.sh screen (didn't extend sensor readings, yet) and collected the above a first time cf. acpi-kdm.log Then I launched KDE session, attached an external display, stressed the system quite a lot and collect the above a second time: cf. acpi-session.log Tree under /proc/acpi is smaller than reported in previous comments (?) Both trip points are, also, very close to each other (all defaults) Highest temperatures were 75 & 80 ºC respectively, all fine. Should I collect these again, or anything else, once only or via the watcher prior to future shutdowns ? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are watching the assignee of the bug. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
