Yesterday my desktop stopped because of being overheated. In /var/log/syslog I see this near the end of the file:

Code: Select all

Mar 10 21:46:18 ludo-IXLs dbus[868]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Mar 10 21:51:20 ludo-IXLs dbus[868]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Mar 10 21:51:20 ludo-IXLs org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 10 21:51:20 ludo-IXLs dbus[868]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Mar 10 21:56:28 ludo-IXLs kernel: [30022.654657] CPU2: Package power limit notification (total events = 3)
Mar 10 21:56:28 ludo-IXLs kernel: [30022.654659] CPU3: Package power limit notification (total events = 3)
Mar 10 21:56:28 ludo-IXLs kernel: [30022.654662] CPU1: Package power limit notification (total events = 3)
Mar 10 21:56:28 ludo-IXLs kernel: [30022.654664] CPU0: Package power limit notification (total events = 3)
Mar 10 21:56:28 ludo-IXLs kernel: [30022.656937] CPU1: Package power limit normal
Mar 10 21:56:28 ludo-IXLs kernel: [30022.656939] CPU3: Package power limit normal
Mar 10 21:56:28 ludo-IXLs kernel: [30022.656942] CPU2: Package power limit normal
Mar 10 21:56:28 ludo-IXLs kernel: [30022.656944] CPU0: Package power limit normal
Mar 10 21:56:35 ludo-IXLs dbus[868]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Mar 10 21:56:35 ludo-IXLs org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 10 21:56:35 ludo-IXLs dbus[868]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'


Any idea how to solve this?
Any package I should try to downgrade maybe?

Have you since been able to reproduce the issue?
How exactly did it overheat the system?

I suspect that it may not have been able to find any backlight device, and so instead may have looped infinitely (using up 100% of one cpu core) which eventually led to the overheating condition occurring. Without any analysis or reproduction of the issue however, it is not possible to confirm that this is the case.

bcooksley wrote:Have you since been able to reproduce the issue?
How exactly did it overheat the system?

I suspect that it may not have been able to find any backlight device, and so instead may have looped infinitely (using up 100% of one cpu core) which eventually led to the overheating condition occurring. Without any analysis or reproduction of the issue however, it is not possible to confirm that this is the case.

The issue hasn't reoccurred since then.
I did take on the habit now to put my windows so that the temperature and cpu usage reading on the desktop is visible most times.

How exactly it overheated I don't know - I was watching a film and up/downloading some torrents, when suddenly the machine stopped and the box felt very warm.
I hope/guess it was a one off, but will keep monitoring it for a while.
I'm glad it didn't happen again so far.