[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACTEcX7oa+Shj=uYiRMoWpng+RZXDeQrOa-VTRmzVVtXJMCgLQ@mail.gmail.com>
Date: Mon, 4 Aug 2025 22:49:43 +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
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
>
Powered by blists - more mailing lists