Bug#945055: closed by carnil@debian.org (Closing this bug (BTS maintenance for src:linux bugs))
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.
Reply to: