stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: me@meirisoda.online
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Kernel 6.11 breaks power-profiles-daemon on NixOS unstable
Date: Thu, 7 Nov 2024 16:03:51 +0100	[thread overview]
Message-ID: <2024110729-paddle-selected-cabd@gregkh> (raw)
In-Reply-To: <Xw3BDSu6nGp8D43shw707_3JcIzRhictWhTjZpThlOWIyF69jtxhq11eV2ExaObroqAhGypRaS86DmN2f2e2IgmGSC4U1AFRW95qOLometo=@meirisoda.online>

On Thu, Nov 07, 2024 at 02:55:57PM +0000, me@meirisoda.online wrote:
> Upgrading to kernel version 6.11 breaks the ability to switch between power modes on KDE Plasma 6.2.2 and NixOS 24.11 (unstable). I am using a ROG Zephyrus 14 GA401 with a 4060.
> 
> I thought it may be Nvidia acting up so I've tried:
> 
>     Re-enabling power-profiles-daemon in my NixOS configuration (did not fix the issues)
>     Disabling supergfxctl on NixOS configuration (did not fix the issue)
>     Switching between nvidia latest and beta (did not fix the issue)
> 
> Switching back to kernel version 6.10 fixes the issue. Since 6.10 is considered EOL upstream, I had to manually switch back to a specific commit hash to get 6.10 to work.
> 
> Hoping this gets fixed on 6.11.

Can you do a 'git bisect' between 6.10 and 6.11 to find out what the
offending commit is?

thanks,

greg k-h

      reply	other threads:[~2024-11-07 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tRrhWMFNiTeCGps2p7WCa6mrpbeCMCgYfeXGsJNOjttrbCyth-0_5EsgpkAZ9zqeMBR4kS6axOZrZxJwnA3LhYtGMgmRnmL2-xrpI0oVkxk=@meirisoda.online>
2024-11-07 14:55 ` Kernel 6.11 breaks power-profiles-daemon on NixOS unstable me
2024-11-07 15:03   ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024110729-paddle-selected-cabd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=me@meirisoda.online \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).