Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #71142 > unrolled thread

Bug#945055: closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs))

Started byChristoph Anton Mitterer <calestyo@scientia.net>
First post2021-05-02 15:50 +0200
Last post2021-05-02 16:30 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#945055: closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs)) Christoph Anton Mitterer <calestyo@scientia.net> - 2021-05-02 15:50 +0200
    Bug#945055: closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs)) Salvatore Bonaccorso <carnil@debian.org> - 2021-05-02 16:10 +0200
      Processed: Re: Bug#945055 closed by carnil@debian.org (Closing  this bug (BTS maintenance for src:linux bugs)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-05-02 16:10 +0200
      Bug#945055: closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs)) Christoph Anton Mitterer <calestyo@scientia.net> - 2021-05-02 16:30 +0200

#71142 — Bug#945055: closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs))

FromChristoph Anton Mitterer <calestyo@scientia.net>
Date2021-05-02 15:50 +0200
SubjectBug#945055: closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs))
Message-ID<CakDT-1ic-1@gated-at.bofh.it>
This bug has actually NOT been fixed.

It's NOT the one with the CPU not going into the RC6 state.

Cheers,
Chris.

[toc] | [next] | [standalone]


#71143

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-05-02 16:10 +0200
Message-ID<CakXf-1Ez-1@gated-at.bofh.it>
In reply to#71142
Control: reopen -1

Hi,

On Sun, May 02, 2021 at 03:40:20PM +0200, Christoph Anton Mitterer wrote:
> This bug has actually NOT been fixed.
> 
> It's NOT the one with the CPU not going into the RC6 state.

In this case I'm reopening the bug again. But I suggest to ping again
upstream in this case, because without progress/movement/ideas
upstream we cannot do anything here downstream.

Regards,
Salvatore, trying to do some maintenance on open src:linux bugs
without progress.

[toc] | [prev] | [next] | [standalone]


#71144 — Processed: Re: Bug#945055 closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs))

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2021-05-02 16:10 +0200
SubjectProcessed: Re: Bug#945055 closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs))
Message-ID<CakXf-1Ez-7@gated-at.bofh.it>
In reply to#71143
Processing control commands:

> reopen -1
Bug #945055 {Done: carnil@debian.org} [linux] huge CPU temperature increase from 5.2 to 5.5 ... and when using intel_pstate
Bug reopened
Ignoring request to alter fixed versions of bug #945055 to the same values previously set

-- 
945055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#71146

FromChristoph Anton Mitterer <calestyo@scientia.net>
Date2021-05-02 16:30 +0200
Message-ID<CalgC-1Ml-1@gated-at.bofh.it>
In reply to#71143
On Sun, 2021-05-02 at 15:56 +0200, Salvatore Bonaccorso wrote:
> In this case I'm reopening the bug again. But I suggest to ping again
> upstream in this case, because without progress/movement/ideas
> upstream we cannot do anything here downstream.

I'm afraid that upstream has shown pretty clearly that they have
basically no interest to look into that issue (guess Intel only spends
money on stuff they still sell).

Just look at the bug reports I've linked to (and the subsequent ones
linkes from there).
I put in many hours of testing and made many plots from which it should
be clear that something is quite wrong. But no further reaction.



For me, I found a workaround:

The CPU/GPU would (according to upstream devs) be very well capable of
controlling a HiDPI screen and doing FullHD playback there (actually
the developer said it should easily do several such stream).
And the notebook in fact has a HiDPI screen.

Now starting around after kernel 5.2, with HiDPI resolutions enabled,
the issues I've described show up:
- even little GPU loads like moving windows in circles leading to
extremely high temperatures ~70-90°C
- video playback in fullscreen generally 100°C.
- even non-GPU related load seemed to have caused such issues, as my
tests showed.


At some point, by chance I reduced the screen resolution to "just"
1920x1080 (from the HiDPI default of 3840x2160).

That immediately solved all issues.


Well, actually, e.g. Cinnamon still seems to run under higher CPU
temperatures than e.g. GNOME Classic (and I'm not only talking about
the idle temperature, but also when doing things like moving Windows),
but it's all so low now that I can live with it.

Under HiDPI, the difference bettween Cinnamon and GNOME Classic was
sometimes quite considerable, IIRC.



That being said, I think you may further lower the severity if you
wish, but it makes perhaps sense to keep the bug open for a while (I
guess until the CPU/GPU is so old, nobody would likely still use it),
so that people have an easier chance of finding it (and the
workaround)?


Cheers,
Chris.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web