Red Hat Bugzilla – Bug 198738
Dell Precision 360 dies under high load
Last modified: 2015-03-04 20:17:22 EST
Description of problem:
Each of my 3 Dell Precision 360 die under high load. They just switch off at
54Â°C processor temperature, without shutting down. I tried with Knoppix 4, the
problem does not exist here.
Version-Release number of selected component (if applicable):
always within 20 minutes, in 90% of the cases in 5 minutes
Steps to Reproduce:
1. while true; do i=5; done
2. try to wait 20 minutes
System stays alive
It sounds like your hitting some form of thermal trip in the processor, yes?
54C is 129F, which is pretty hot... No messsages in dmesg leading up to this?
The CPU fan is doing alright?
I tried on 3 equal computers and exchanged all fans (one). There is no related
message in /var/log/messages. The same problem occurs on FC 4.
Sometimes the system goes down at 52Â°C, sometimes at 54Â°C, sometimes at 53Â°C.
There is a message in the Bios log about a thermal shutdown.
Distro Error occurs Can start /etc/init.d/lm_sensors
Knoppix 4 no no
SLES 9 no no
SUSE 9.3 no no
Fedora 4 yes yes
Fedora 5 yes yes
SUSE 10 yes yes
SUSE 10.1 yes yes
SLES 10 yes yes
I wrote an Operating System stub as described under
That OS sends the processor into an endless loop. Running my Precision 360
with it, it never powers off. Note that the processor is running in real mode
Deleting /etc/sensors.conf and /etc/sysconfig/lm_sensors resolved the problem
Have you tried disabling lm-sensors on Fedora, too?
Read ya, Phil
On a fresh installation of FC5 without lm-sensors, the problem does not occur.
I would recommend to add a big warning when installing lm-sensors, or to take it
away from the distribution completely.
I found out, the "set" commands in the /etc/sensors.conf file cause that problem
- outcommenting some of them resolved the error. With FC5, sensors is not
functional, therefore no problems. Can we change this in the distribution ?
Do you still get the problem with updated lm_sensors packages in FC6 or Fedora
Read ya, Phil
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.