All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Papool Chaudhari <Papool@chaudharilaw.com>
Cc: regressions@lists.linux.dev
Subject: Re: [REGRESSION] 2017 Pixelbook backlight control doesn’t work with 7.1 kernel
Date: Sat, 11 Jul 2026 09:43:28 +0200	[thread overview]
Message-ID: <2026071153-wrench-operating-e32d@gregkh> (raw)
In-Reply-To: <CALcz8n4XCt8GK0X=JTDOkMn32Z73HpHKRNaRCdSf=mzr3+r27A@mail.gmail.com>

On Sat, Jul 11, 2026 at 01:11:06AM -0600, Papool Chaudhari wrote:
> I tried reverting commit b3793af3277f65d256d67f9949e760b434ff66dd on
> top of v7.1, but the resulting kernel completely hangs at 'Loading
> initial ramdisk'. Even when adding 'nomodeset' via GRUB, the crash
> happens so early that no kernel text or console output is ever
> printed. It appears this Intel THC merge cannot be cleanly isolated or
> reverted on v7.1 without causing an immediate early boot failure on
> this hardware.

A merge point is usually not a good place to revert, as that can be
"odd".  I also don't really see a diff at this point in time, so can you
try both sides of the merge to see if they both work, or not?

thanks,

greg k-h

  reply	other threads:[~2026-07-11  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 20:58 [REGRESSION] 2017 Pixelbook backlight control doesn’t work with 7.1 kernel Papool Chaudhari
2026-07-09  6:40 ` Greg KH
     [not found]   ` <CALcz8n6VtL5D20WCJEsiBRDRKOE6GsF+YPCc+XuS2xr-mqnSTg@mail.gmail.com>
2026-07-11  5:31     ` Greg KH
2026-07-11  7:11       ` Papool Chaudhari
2026-07-11  7:43         ` Greg KH [this message]
     [not found]           ` <CALcz8n7XoEvYK7PM+WWuQ2rBaWujc3YTQh1DWvLxoRHt3bAT9A@mail.gmail.com>
2026-07-12  5:50             ` Greg KH
2026-07-13  4:39               ` Thorsten Leemhuis

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=2026071153-wrench-operating-e32d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Papool@chaudharilaw.com \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.