On 3/10/21 8:55 AM, Babu Moger wrote: > > >> -----Original Message----- >> From: Paolo Bonzini <pbonzini@xxxxxxxxxx> >> Sent: Wednesday, March 10, 2021 3:09 AM >> To: Moger, Babu <Babu.Moger@xxxxxxx>; Jim Mattson >> <jmattson@xxxxxxxxxx> >> Cc: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>; Wanpeng Li >> <wanpengli@xxxxxxxxxxx>; kvm list <kvm@xxxxxxxxxxxxxxx>; Joerg Roedel >> <joro@xxxxxxxxxx>; the arch/x86 maintainers <x86@xxxxxxxxxx>; LKML <linux- >> kernel@xxxxxxxxxxxxxxx>; Ingo Molnar <mingo@xxxxxxxxxx>; Borislav Petkov >> <bp@xxxxxxxxx>; H . Peter Anvin <hpa@xxxxxxxxx>; Thomas Gleixner >> <tglx@xxxxxxxxxxxxx>; Makarand Sonare <makarandsonare@xxxxxxxxxx>; Sean >> Christopherson <seanjc@xxxxxxxxxx> >> 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@xxxxxxxxxx> >>> 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)? I couldn't reproduce the issue on any of the upstream versions. I have tried v4.9, v4.8 and even on latest v5.11. No issues there. There is no upstream version 4.9.258. Jim mentioned Debian 10 which is based of kernel version 4.19 is also fine. Issue appears to be only affecting Debian 9(kernel v4.9.0-14).
