On 26 August 2017 at 14:42, <mad.scientist.at.large@xxxxxxxxxxxx> 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.
>
I did think that, but the box is brand new (aka 4 weeks old) but even
so I did open it up to find no clogs. It seems instead linked with
the updated kernel and drivers in CR. [There is only one laptop
involved in this problem.]
> 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@xxxxxxxxx:
>
>
>> 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
>> [Sat Aug 26 08:58:21 2017] CPU1: Package temperature/speed normal
>> [Sat Aug 26 08:58:21 2017] CPU5: Package temperature/speed normal
>> [Sat Aug 26 08:58:21 2017] CPU0: Package temperature/speed normal
>> [Sat Aug 26 08:58:21 2017] CPU6: Core temperature/speed normal
>> [Sat Aug 26 08:58:21 2017] CPU3: Package temperature/speed normal
>> [Sat Aug 26 08:58:21 2017] CPU7: Package temperature/speed normal
>> [Sat Aug 26 08:58:21 2017] CPU6: Package temperature/speed normal
>> [Sat Aug 26 08:58:21 2017] CPU2: Package temperature/speed normal
>>
>> This happened when logging into a Cinnamon desktop. The desktop
>> background would go black when this happened and the fans went to
>> 100%. After two minutes it quieted down. Logging in again with
>> Cinnamon repeated it. Using the default Gnome desktop does not have
>> this problem so this is more of a "if you are using Cinnamon you may
>> run into this."
>>
>> The second was that the new nouveau driver is very noisy on the
>> hardware. The message repeats:
>>
>> Sat Aug 26 13:42:36 2017] nouveau 0000:02:00.0: priv: HUB0: 6013d4
>> 00005700 (1f408200)
>> [Sat Aug 26 13:42:37 2017] nouveau 0000:02:00.0: priv: HUB0: 10ecc0
>> ffffffff (1940822c)
>> [Sat Aug 26 13:42:37 2017] nouveau 0000:02:00.0: DRM: resuming client
>> object trees...
>> [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: evicting buffers...
>> [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: waiting for
>> kernel channels to go idle...
>> [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: suspending
>> client object trees...
>> [Sat Aug 26 13:42:44 2017] nouveau 0000:02:00.0: DRM: suspending
>> kernel object tree...
>> [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: DRM: resuming kernel
>> object tree...
>> [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: priv: HUB0: 6013d4
>> ffff57ff (18408200)
>> [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: priv: HUB0: 10ecc0
>> ffffffff (1840822c)
>> [Sat Aug 26 13:42:45 2017] nouveau 0000:02:00.0: DRM: resuming client
>> object trees...
>>
>> fairly often. The system does seem to be running hotter with the fan
>> going louder than what i remember it being with 7.3. At this point I
>> am mostly reporting this as a "anyone else seeing this?" type report.
>>
>>
>>
>>
>>
>> --
>> Stephen J Smoogen.
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> https://lists.centos.org/mailman/listinfo/centos
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
