All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jinpu Wang <jinpu.wang@ionos.com>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
	kvm@vger.kernel.org
Subject: Re: 5.10.131-rc1 crash with int3: RIP 0010:xaddw_ax_dx+0x9/0x10 [kvm]
Date: Wed, 13 Jul 2022 15:01:09 +0200	[thread overview]
Message-ID: <Ys7CFYqA62YcIFiT@kroah.com> (raw)
In-Reply-To: <CAMGffEnTobhKvwKcRTnSz1JgNBVeTTtbOvP2OtAMgceqOOhN4A@mail.gmail.com>

On Wed, Jul 13, 2022 at 02:26:44PM +0200, Jinpu Wang wrote:
> On Wed, Jul 13, 2022 at 12:49 PM Jinpu Wang <jinpu.wang@ionos.com> wrote:
> >
> > Hi, all,
> >
> > When I test with 5.10.131-rc1 with kvm-uint-tests on Intel Broadwell
> > and Skylake server, it panic also immediately with following call
> > trace:
> >
> > [ 1867.769328] APIC base relocation is unsupported by KVM
> > [ 1895.977424] kvm: emulating exchange as write
> > [ 1895.979316] int3: 0000 [#1] SMP
> > [ 1895.979317] CPU: 40 PID: 14811 Comm: qemu-6.1 Kdump: loaded
> > Tainted: G           O      5.10.131-pserver
> > #5.10.131-1+feature+linux+5.10.y+20220712.1850+30f4172c~deb11
> > [ 1895.979317] Hardware name: Supermicro SBI-7228R-T2F2/B10DRT-IBF2,
> > BIOS 3.0a 03/05/2018
> > [ 1895.979318] RIP: 0010:xaddw_ax_dx+0x9/0x10 [kvm]
> > [ 1895.979318] Code: 00 0f bb d0 c3 cc cc cc cc 48 0f bb d0 c3 cc cc
> > cc cc 0f 1f 80 00 00 00 00 0f c0 d0 c3 cc cc cc cc 66 0f c1 d0 c3 cc
> > cc cc cc <0f> 1f 80 00 00 00 00 0f c1 d0 c3 cc cc cc cc 48 0f c1 d0 c3
> > cc cc
> > [ 1895.979319] RSP: 0018:ffffab6e63c6fd30 EFLAGS: 00000202
> > [ 1895.979320] RAX: 0000000089abcdef RBX: 0000000000000001 RCX: 0000000000000000
> > [ 1895.979321] RDX: 0000000076543210 RSI: ffffffffc0f3e4a0 RDI: 0000000000000200
> > [ 1895.979321] RBP: ffff997c29c214e0 R08: ffff997c29c214e0 R09: 0000000000000002
> > [ 1895.979321] R10: 0000000000000001 R11: 0000000000000000 R12: ffffffffc0f73540
> > [ 1895.979322] R13: 0000000000000000 R14: ffff997c29c214e0 R15: 0000000000000000
> > [ 1895.979322] FS:  00007fc44a5a3700(0000) GS:ffff999a7fc80000(0000)
> > knlGS:0000000000000000
> > [ 1895.979322] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 1895.979323] CR2: 0000000000000000 CR3: 000000012bf16004 CR4: 00000000003726e0
> > [ 1895.979324] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > [ 1895.979324] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > [ 1895.979325] Call Trace:
> > [ 1895.979325]  ? fastop+0x59/0xa0 [kvm]
> > [ 1895.979326]  ? x86_emulate_insn+0x73a/0xe00 [kvm]
> > [ 1895.979326]  ? x86_emulate_instruction+0x2d0/0x750 [kvm]
> > [ 1895.979326]  ? vmx_vcpu_load+0x21/0x70 [kvm_intel]
> > [ 1895.979327]  ? complete_emulated_mmio+0x236/0x310 [kvm]
> > [ 1895.979327]  ? kvm_arch_vcpu_ioctl_run+0x1744/0x1920 [kvm]
> > [ 1895.979327]  ? kvm_vcpu_ioctl+0x211/0x5a0 [kvm]
> > [ 1895.979328]  ? __fget_files+0x79/0xb0
> > [ 1895.979328]  ? __fget_files+0x79/0xb0
> > [ 1895.979328]  ? __x64_sys_ioctl+0x8b/0xc0
> > [ 1895.979329]  ? do_syscall_64+0x33/0x40
> > [ 1895.979329]  ? entry_SYSCALL_64_after_hwframe+0x61/0xc6
> > [ 1895.979329] Modules linked in: nfnetlink_cttimeout nft_nat
> > nft_counter nft_chain_nat nft_meta_bridge bridge openvswitch nsh
> > nf_conncount nf_nat dummy nf_log_ipv6 nf_log_ipv4 nf_log_common
> > nft_log nft_limit rnbd_client(O) intel_rapl_msr rtrs_client(O)
> > intel_rapl_common rtrs_core(O) ib_ipoib rdma_ucm rdma_cm iw_cm ib_cm
> > ib_umad sb_edac x86_pkg_temp_thermal coretemp kvm_intel mlx4_ib nft_ct
> > kvm nf_conntrack ib_uverbs nf_defrag_ipv6 ib_core nf_defrag_ipv4
> > irqbypass crc32_pclmul aesni_intel sd_mod libaes t10_pi crypto_simd
> > crc_t10dif nf_tables crct10dif_generic cryptd glue_helper
> > crct10dif_pclmul crct10dif_common vhost_net sg rapl intel_cstate
> > nfnetlink tun(O) ethoip6_pmtud(O) vhost vhost_iotlb ahci tap iTCO_wdt
> > libahci input_leds mei_me libata iTCO_vendor_support mlx4_core ioatdma
> > scsi_mod led_class watchdog evdev acpi_ipmi mei ipmi_si 8021q garp stp
> > mrp llc ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad button
> > fuse ip_tables x_tables autofs4 loop raid10 raid456 async_raid6_recov
> > [ 1895.979349]  async_memcpy async_pq async_xor async_tx xor raid6_pq
> > libcrc32c raid1 raid0 linear md_mod crc32c_intel igb i2c_i801
> > i2c_algo_bit i2c_smbus xhci_pci dca lpc_ich ptp i2c_core mfd_core
> > pps_core xhci_hcd
> >
> > Is this bug known, any hint how to fix it?
> I did more tests on different Servers, so far all the machine
> checked(Skylake/Icelake/Haswell/Broadwell/EPYC) crash immediately
> except AMD Opteron.
> kvm-unit-tests succeeded without regression.

Same issue on Linus's tree right now as well?  Or does that pass just
fine?

thanks,

greg k-h

  reply	other threads:[~2022-07-13 13:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 10:49 5.10.131-rc1 crash with int3: RIP 0010:xaddw_ax_dx+0x9/0x10 [kvm] Jinpu Wang
2022-07-13 12:26 ` Jinpu Wang
2022-07-13 13:01   ` Greg Kroah-Hartman [this message]
2022-07-13 13:18     ` Jinpu Wang
2022-07-13 21:11       ` Sean Christopherson
2022-07-14  7:16         ` Jinpu Wang

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=Ys7CFYqA62YcIFiT@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jinpu.wang@ionos.com \
    --cc=kvm@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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.