Bug#880203: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored)

To: Ben Hutchings <ben@decadent.org.uk>, 880203@bugs.debian.org
Subject: Bug#880203: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored)
From: Leon Meier <Leon.Meier@yandex.ru>
Date: Wed, 1 Nov 2017 13:42:41 +0100
Message-id: <[🔎] 27aaf6c5-330b-f013-1805-8b766d6ad710@yandex.ru>
Reply-to: Leon Meier <Leon.Meier@yandex.ru>, 880203@bugs.debian.org
In-reply-to: <[🔎] 1509539926.2748.61.camel@decadent.org.uk>
References: <1509446219.2748.35.camel@decadent.org.uk> <d6a5f770-fdbe-9d6a-127a-4d6abfe4d191@yandex.ru> <handler.880203.D880203.150944624227212.notifdone@bugs.debian.org> <5587a8a5-0a7f-97f7-2452-d7ebbf5cdba0@yandex.ru> <[🔎] 1509539926.2748.61.camel@decadent.org.uk> <d6a5f770-fdbe-9d6a-127a-4d6abfe4d191@yandex.ru>

On 01.11.2017 13:38, Ben Hutchings wrote:

On Tue, 31 Oct 2017 13:25:11 +0100 Leon Meier <Leon.Meier@yandex.ru> wrote:

On 31.10.2017 11:39, Debian Bug Tracking System wrote:

Yes, but that doesn't mean we can do anything about it.


Why not simply re-issue the request setting the performance-level after
resume?


The driver does that.

Oh. But in this case the effect of this action is not visible on my machine.

Reply to:

References:
- Bug#880203: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored)
  - From: Ben Hutchings <ben@decadent.org.uk>