might also use many of the nice gui applications, i frequently use gkrellm (sp?) if i suspect a problem or just want a good idea of everything happening (it also shows all drive activity per partition, network info, etc. including all the temperature sensors it can fine. alternately you might try a recent veraion of "hiren's" utilities, easy to find for download, very, very usefull and it include utilities to load the processor and heat it up to check stability. then again, i know the cd for windows xp and the installer are a good check aswell, if stability is marginal the installer will repeatedly fail in the same place when it's decompressing all the files which is of course a lot of math, and math makes cpus run hotter. lm sensors is always one of the first things i install, then you can also watch drive temps in the panel. after you install lm_sensors you need to run , i believe, sensors-detect with root privalages so it can prob for all the sensors, there are a lot of little known busses in most machines and it tries to search them all looking for sensors. though i don't know how to monitor the fan sensors. -- The Power Of the People Is Stronger Than The People In Charge. 26. Aug 2017 13:05 by vychytraly at gmail.com: > Also try package lm_sensors and its command sensors-detect, maybe just the > temperature sensors are not properly initialized > > On Sat, Aug 26, 2017 at 8:42 PM, <> mad.scientist.at.large at tutanota.com> > > wrote: > >> It means it's time to open up your' laptop and evict all the dust >> bunnies. it's overheating on one desktop but not the other because one of >> your' desktops, as configured on your system is using the processor more. >> this is how laptops die as most people just whine and complain as their' >> laptop gets slower and less stable. >> >> the first part to fail is often the hard drive. hard drives can operate >> hot but it greatly shortens the drives lifetime. on my desktop i try to >> keep my drives below 100deg F. they last forever practically then, where as >> around 120-130 you get fairly rapid failures. >> >> It's a major, major pain to work on most laptop hardware but you have to >> do it. i have such a laptop that ran hot until the drive failed, so i got >> a nice laptop free that needs a new drive and cleaning, or possibly a new >> fan (they aren't running, either due to dust bunnies or failure". it's a >> $300 laptop on ebay and i got it free because people ran it into the ground >> and they new i might be able to fix it. if you do clean it out look for >> the repair manual so you can take it apart and get it back together >> correctly, and there are often good videos on youtube showing how for most >> models. >> >> -- >> The Power Of the People Is Stronger Than The People In Charge. >> >> >> 26. Aug 2017 12:11 by >> smooge at gmail.com>> : >> >> >> > I have updated my laptop to 7.4 CR this morning and found that there >> > have been a lot of logs on two fronts for the first time. >> > >> > 1. The kernel has indicated overheating: >> > >> > [Sat Aug 26 08:58:21 2017] CPU2: Core temperature above threshold, cpu >> > clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU4: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU6: Core temperature above threshold, cpu >> > clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU0: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU6: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] mce: [Hardware Error]: Machine check events >> logged >> > [Sat Aug 26 08:58:21 2017] CPU2: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] mce: [Hardware Error]: Machine check events >> logged >> > [Sat Aug 26 08:58:21 2017] CPU1: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU5: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU3: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU7: Package temperature above threshold, >> > cpu clock throttled (total events = 1) >> > [Sat Aug 26 08:58:21 2017] CPU2: Core temperature/speed normal >> > [Sat Aug 26 08:58:21 2017] CPU4: Package temperature/speed normal