[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1451b13e-c67f-8948-64ff-5c01cfb47ea7@redhat.com>
Date: Wed, 10 Mar 2021 10:08:56 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Babu Moger <babu.moger@....com>, Jim Mattson <jmattson@...gle.com>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
kvm list <kvm@...r.kernel.org>, Joerg Roedel <joro@...tes.org>,
the arch/x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Makarand Sonare <makarandsonare@...gle.com>,
Sean Christopherson <seanjc@...gle.com>
Subject: Re: [PATCH v6 00/12] SVM cleanup and INVPCID feature support
On 10/03/21 02:04, Babu Moger wrote:
> Debian kernel 4.10(tag 4.10~rc6-1~exp1) also works fine. It appears the
> problem is on Debian 4.9 kernel. I am not sure how to run git bisect on
> Debian kernel. Tried anyway. It is pointing to
>
> 47811c66356d875e76a6ca637a9d384779a659bb is the first bad commit
> commit 47811c66356d875e76a6ca637a9d384779a659bb
> Author: Ben Hutchings<benh@...ian.org>
> Date: Mon Mar 8 01:17:32 2021 +0100
>
> Prepare to release linux (4.9.258-1).
>
> It does not appear to be the right commit. I am out of ideas now.
> hanks
Have you tried bisecting the upstream stable kernels (from 4.9.0 to
4.9.258)?
Paolo
Powered by blists - more mailing lists