linux-kernel - Re: [REGRESSION] tty lockup and WWAN loss after hibernate/suspend in 6.8+ on ThinkPad X1 Carbon Gen 10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACTEcX7hsRkzYEBg4pQd5s36p_ZXJM=dtxSGmBjfkt5sWrXP8g@mail.gmail.com>
Date: Wed, 6 Aug 2025 11:40:07 +0300
From: Andy Mindful <andy.mindful@...il.com>
To: regressions@...ts.linux.dev
Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, 
	intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org, 
	linux-acpi@...r.kernel.org, rafael@...nel.org, ville.syrjala@...ux.intel.com, 
	tglx@...utronix.de, Christian Brauner <brauner@...nel.org>, 
	Jani Nikula <jani.nikula@...el.com>, Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: [REGRESSION] tty lockup and WWAN loss after hibernate/suspend in
 6.8+ on ThinkPad X1 Carbon Gen 10

Hello,

Can somebody advise how to properly bisect issues in linux-stable
repository between v6.7.11 to v6.8-rc1 tags?

I tried two options:

1. No skip

git checkout v6.7.11
git bisect start
git bisect good 6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1
git bisect bad 6613476e225e090cc9aad49be7fa504e290dd33d
git bisect bad 0dd3ee31125508cd67f7e7172247f05b7fd1753a

Leads to:
The merge base 0dd3ee31125508cd67f7e7172247f05b7fd1753a is bad.
This means the bug has been fixed between
0dd3ee31125508cd67f7e7172247f05b7fd1753a and
[6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1].

What should be done next?

2. Skip
git checkout v6.7.11
git bisect start
git bisect good 6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1
git bisect bad 6613476e225e090cc9aad49be7fa504e290dd33d
git bisect bad 0dd3ee31125508cd67f7e7172247f05b7fd1753a
git bisect skip 0dd3ee31125508cd67f7e7172247f05b7fd1753a
git bisect good ba5afb9a84df2e6b26a1b6389b98849cd16ea757
git bisect good 61da593f4458f25c59f65cfd9ba1bda570db5db7
git bisect bad e38f734add21d75d76dbcf7b214f4823131c1bae
git bisect bad 5d197e97fb106c09d3d013be341e5961fd70ec8a
git bisect good 1b1934dbbdcf9aa2d507932ff488cec47999cf3f
git bisect bad 8c9244af4dc8680a453e759331f0c93d5bde1898
git bisect bad 783288010035e4c250a0b6491a4642cdb8d30548
git bisect bad 1c3c87d720cbd1ff86dc1bfc6df8ee9adce5879b
git bisect good 8d99e347c097ab3f9fb93d0f88dddf20051d7c88
git bisect bad 6c370dc65374db5afbc5c6c64c662f922a2555ad
git bisect good 43f623f350ce1c46c53b6b77f4dbe741af8c44f3
git bisect good 8a89efd43423cb3005c5e641e846184e292c1465
git bisect good 5d74316466f4aabdd2ee1e33b45e4933c9bc3ea1

Leads to:

# first bad commit: [6c370dc65374db5afbc5c6c64c662f922a2555ad] Merge
branch 'kvm-guestmemfd' into HEAD

Which is incorrect as per Paolo Bonzini comment.

I'd like to test this thing, because hibernation is quite crucial in a
multi-boot environment and may save a lot of time while working with
different systems.

Thank you in advance.

пн, 4 серп. 2025 р. о 22:49 Andy Mindful <andy.mindful@...il.com> пише:
>
> Can you please advise on how to bisect further?
>
> andy@...ovo:~/linux-stable$ git bisect bad
> The merge base 0dd3ee31125508cd67f7e7172247f05b7fd1753a is bad.
> This means the bug has been fixed between
> 0dd3ee31125508cd67f7e7172247f05b7fd1753a and
> [6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1].
>
> andy@...KTOP-0R165CF:~/linux-stable$ git bisect log
> git bisect start
> # status: waiting for both good and bad commits
> # good: [6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1] Linux 6.7.11
> git bisect good 6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1
> # status: waiting for bad commit, 1 good commit known
> # bad: [6613476e225e090cc9aad49be7fa504e290dd33d] Linux 6.8-rc1
> git bisect bad 6613476e225e090cc9aad49be7fa504e290dd33d
> # bad: [0dd3ee31125508cd67f7e7172247f05b7fd1753a] Linux 6.7
> git bisect bad 0dd3ee31125508cd67f7e7172247f05b7fd1753a
>
> andy@...ovo:~/linux-stable$ git status
> HEAD detached at 0dd3ee311255
> You are currently bisecting, started from branch '6fc5460ed8dd'.
> (use "git bisect reset" to get back to the original branch)
>
> It is not moving further.
>
> пн, 4 серп. 2025 р. о 17:50 Paolo Bonzini <pbonzini@...hat.com> пише:
> >
> > On Mon, Aug 4, 2025 at 12:57 PM Andy Mindful <andy.mindful@...il.com> wrote:
> > > Double-checked bisect, looks like I've have found broken commit:
> > >
> > > > > git bisect bad
> > > > > The merge base ba5afb9a84df2e6b26a1b6389b98849cd16ea757 is bad.
> > > > > This means the bug has been fixed between
> > > > > ba5afb9a84df2e6b26a1b6389b98849cd16ea757 and
> > > > > [1b1934dbbdcf9aa2d507932ff488cec47999cf3f
> > > > > 61da593f4458f25c59f65cfd9ba1bda570db5db7
> > > > > 6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1
> > > > > ba5afb9a84df2e6b26a1b6389b98849cd16ea757].
> >
> > This skip is messing up the results:
> >
> > # skip: [0dd3ee31125508cd67f7e7172247f05b7fd1753a] Linux 6.7
> > git bisect skip 0dd3ee31125508cd67f7e7172247f05b7fd1753a
> >
> > and there are still 3858 commits in
> > ba5afb9a84df2e6b26a1b6389b98849cd16ea757..{1b1934dbbdcf9aa2d507932ff488cec47999cf3f,61da593f4458f25c59f65cfd9ba1bda570db5db7,ba5afb9a84df2e6b26a1b6389b98849cd16ea757}
> >
> > Any chance you can get 6.7 to work and restrict the range further?
> >
> > Thanks,
> >
> > Paolo
> >