All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: bugzilla-daemon@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 218949] Kernel panic after upgrading to 6.10-rc2
Date: Mon, 10 Jun 2024 07:45:26 -0700	[thread overview]
Message-ID: <ZmcOCPprnmn1vYyn@google.com> (raw)
In-Reply-To: <bug-218949-28872-vNF0xS1i0R@https.bugzilla.kernel.org/>

On Mon, Jun 10, 2024, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218949
> 
> --- Comment #2 from Gino Badouri (badouri.g@gmail.com) ---
> Alright, it's not a regression in the kernel but caused by a bios update (I
> guess).
> I get the same on my previous kernel 6.9.0-rc1.

The WARNs are not remotely the same.  The below issue in svm_vcpu_enter_exit()
was resolved in v6.9 final[1].

The lockdep warnings in track_pfn_remap() and remap_pfn_range_notrack() is a
known issue in vfio_pci_mmap_fault(), with an in-progress fix[2] that is destined
for 6.10.

[1] https://lore.kernel.org/all/1d10cd73-2ae7-42d5-a318-2f9facc42bbe@alu.unizg.hr
[2] https://lore.kernel.org/all/20240530045236.1005864-1-alex.williamson@redhat.com

> Both my 6.9.0-rc1 6.10.0-rc2 kernels are vanilla builds from kernel.org
> (unpatched).
> 
> After updating the bios/firmware of my mainboard Asus ROG Zenith II Extreme
> from 1802 to 2102, it always seems to spawn the error:
> 
> [ 1150.380137] ------------[ cut here ]------------
> [ 1150.380141] Unpatched return thunk in use. This should not happen!
> [ 1150.380144] WARNING: CPU: 3 PID: 4849 at arch/x86/kernel/cpu/bugs.c:2935
> __warn_thunk+0x40/0x50

...

> [ 1150.380266] CPU: 3 PID: 4849 Comm: CPU 0/KVM Not tainted 6.9.0-rc1 #1
> [ 1150.380269] Hardware name: ASUS System Product Name/ROG ZENITH II EXTREME,
> BIOS 2102 02/16/2024
> [ 1150.380271] RIP: 0010:__warn_thunk+0x40/0x50

...

> [ 1150.380298] Call Trace:
> [ 1150.380300]  <TASK>
> [ 1150.380344]  warn_thunk_thunk+0x16/0x30
> [ 1150.380351]  svm_vcpu_enter_exit+0x71/0xc0 [kvm_amd]
> [ 1150.380364]  svm_vcpu_run+0x1e7/0x850 [kvm_amd]
> [ 1150.380377]  kvm_arch_vcpu_ioctl_run+0xca3/0x16d0 [kvm]
> [ 1150.380458]  kvm_vcpu_ioctl+0x295/0x800 [kvm]

  reply	other threads:[~2024-06-10 14:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 21:27 [Bug 218949] New: Kernel panic after upgrading to 6.10-rc2 bugzilla-daemon
2024-06-10  5:36 ` [Bug 218949] " bugzilla-daemon
2024-06-10 10:57 ` bugzilla-daemon
2024-06-10 11:03 ` bugzilla-daemon
2024-06-10 14:45   ` Sean Christopherson [this message]
2024-06-10 11:04 ` bugzilla-daemon
2024-06-10 11:05 ` bugzilla-daemon
2024-06-10 14:45 ` bugzilla-daemon
2024-06-10 16:17 ` bugzilla-daemon
2024-06-11  7:22 ` bugzilla-daemon

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=ZmcOCPprnmn1vYyn@google.com \
    --to=seanjc@google.com \
    --cc=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.kernel.org \
    /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.