From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 21CE3C28D13 for ; Mon, 22 Aug 2022 23:46:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238787AbiHVXqx (ORCPT ); Mon, 22 Aug 2022 19:46:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49464 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238766AbiHVXqv (ORCPT ); Mon, 22 Aug 2022 19:46:51 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 260194F189 for ; Mon, 22 Aug 2022 16:46:50 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id A8CA9B81992 for ; Mon, 22 Aug 2022 23:46:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 547B4C433B5 for ; Mon, 22 Aug 2022 23:46:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661212007; bh=qmKeJvdI4nusV207vEeZodET7bTpKi7mbdZJYUjZy+8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OPnparmXMyPD1NP+Ew+SQMefPJn73CmLlYPzdGTORpEaGsl/NI6P9H6ScIQzefEhM sTuQ4qkN/GX35BERm3S/9axvuV1KeQO4fuqaltTAGbSMw+gvy0y5gH8wPqooZ3ofVB xThRqRNyUabQVmC1Ik5+BnzMxhK24szhM0kGuiINOQYNjrmM66tOKsiPBlZme60BVd MuYxCv+5XdjsPC61JvAisqefGJUQjKkxIUmQx4bLczl1wa01YlXwYmUX3Adw1QFEuJ UBFrMBKlm7I0U21k4wVuVtZir+VwnIHRBeA3aPgaVf88Q5C2CWCK1TEjuHBjxKi2bY T0ve4v6f2FQHQ== Received: by aws-us-west-2-korg-bugzilla-1.web.codeaurora.org (Postfix, from userid 48) id 3AC5AC433EA; Mon, 22 Aug 2022 23:46:47 +0000 (UTC) From: bugzilla-daemon@kernel.org To: kvm@vger.kernel.org Subject: [Bug 216388] On Host, kernel errors in KVM, on guests, it shows CPU stalls Date: Mon, 22 Aug 2022 23:46:47 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo virtualization_kvm@kernel-bugs.osdl.org X-Bugzilla-Product: Virtualization X-Bugzilla-Component: kvm X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: high X-Bugzilla-Who: zhenyuw@linux.intel.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: virtualization_kvm@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=3D216388 --- Comment #2 from zhenyuw@linux.intel.com --- On 2022.08.22 17:50:33 +0000, Sean Christopherson wrote: > +GVT folks > > On Sun, Aug 21, 2022, bugzilla-daemon@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=3D216388 > >=20 > > Bug ID: 216388 > > Summary: On Host, kernel errors in KVM, on guests, it shows = CPU > > stalls > > Product: Virtualization > > Version: unspecified > > Kernel Version: 5.19.0 / 5.19.1 / 5.19.2 > > Hardware: All > > OS: Linux > > Tree: Mainline > > Status: NEW > > Severity: high > > Priority: P1 > > Component: kvm > > Assignee: virtualization_kvm@kernel-bugs.osdl.org > > Reporter: nanook@eskimo.com > > Regression: No > >=20 > > Created attachment 301614 > > --> https://bugzilla.kernel.org/attachment.cgi?id=3D301614&action=3De= dit > > The configuration file used to Comile this kernel. > >=20 > > This behavior has persisted across 5.19.0, 5.19.1, and 5.19.2. While t= he > > kernel I am taking this example from is tainted (owing to using Intel > > development drivers for GPU virtualization), it is also occurring on > > non-tainted kernels on servers with no development or third party modul= es > > installed. > >=20 > > INFO: task CPU 2/KVM:2343 blocked for more than 1228 seconds. > > [207177.050049] Tainted: G U I 5.19.2 #1 > > [207177.050050] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disa= bles > > this message. > > [207177.050051] task:CPU 2/KVM state:D stack: 0 pid: 2343 ppid= :=20=20=20 > 1 > > flags:0x00000002 > > [207177.050054] Call Trace: > > [207177.050055] > > [207177.050056] __schedule+0x359/0x1400 > > [207177.050060] ? kvm_mmu_page_fault+0x1ee/0x980 > > [207177.050062] ? kvm_set_msr_common+0x31f/0x1060 > > [207177.050065] schedule+0x5f/0x100 > > [207177.050066] schedule_preempt_disabled+0x15/0x30 > > [207177.050068] __mutex_lock.constprop.0+0x4e2/0x750 > > [207177.050070] ? aa_file_perm+0x124/0x4f0 > > [207177.050071] __mutex_lock_slowpath+0x13/0x20 > > [207177.050072] mutex_lock+0x25/0x30 > > [207177.050075] intel_vgpu_emulate_mmio_read+0x5d/0x3b0 [kvmgt] >=20 > This isn't a KVM problem, it's a KVMGT problem (despite the name, KVMGT is > very > much not KVM). >=20 > > [207177.050084] intel_vgpu_rw+0xb8/0x1c0 [kvmgt] > > [207177.050091] intel_vgpu_read+0x20d/0x250 [kvmgt] > > [207177.050097] vfio_device_fops_read+0x1f/0x40 > > [207177.050100] vfs_read+0x9b/0x160 > > [207177.050102] __x64_sys_pread64+0x93/0xd0 > > [207177.050104] do_syscall_64+0x58/0x80 > > [207177.050106] ? kvm_on_user_return+0x84/0xe0 > > [207177.050107] ? fire_user_return_notifiers+0x37/0x70 > > [207177.050109] ? exit_to_user_mode_prepare+0x41/0x200 > > [207177.050111] ? syscall_exit_to_user_mode+0x1b/0x40 > > [207177.050112] ? do_syscall_64+0x67/0x80 > > [207177.050114] ? irqentry_exit+0x54/0x70 > > [207177.050115] ? sysvec_call_function_single+0x4b/0xa0 > > [207177.050116] entry_SYSCALL_64_after_hwframe+0x63/0xcd > > [207177.050118] RIP: 0033:0x7ff51131293f > > [207177.050119] RSP: 002b:00007ff4ddffa260 EFLAGS: 00000293 ORIG_RAX: > > 0000000000000011 > > [207177.050121] RAX: ffffffffffffffda RBX: 00005599a6835420 RCX: > > 00007ff51131293f > > [207177.050122] RDX: 0000000000000004 RSI: 00007ff4ddffa2a8 RDI: > > 0000000000000027 > > [207177.050123] RBP: 0000000000000004 R08: 0000000000000000 R09: > > 00000000ffffffff > > [207177.050124] R10: 0000000000065f10 R11: 0000000000000293 R12: > > 0000000000065f10 > > [207177.050124] R13: 00005599a6835330 R14: 0000000000000004 R15: > > 0000000000065f10 > > [207177.050126] > >=20 > > I am seeing this on Intel i7-6700k, i7-6850k, and i7-9700k platfor= ms. One recent regression fix on Comet Lake is https://patchwork.freedesktop.org/patch/496987/, it's on the way to 6.0-rc and would be pushed to 5.19 stable as well. But l= ooks this report impacts on more platforms? We'll double check. Thanks > >=20 > > This did not happen on 5.17 kernels, and 5.18 kernels never ran st= able > > enough on my platforms to actually run them for more than a few minutes. > >=20 > > Likewise 6.0-rc1 has not been stable enough to run in production.= =20 > After > > less than three hours running on my workstation it locked hard with even > the > > magic sys-request key being unresponsive and only power cycling the mac= hine > got > > it back. > >=20 > > The operating system in use for the host on all machines is Ubuntu > 22.04. > >=20 > > Guests vary with Ubuntu 22.04 being the most common but also Mint, > Debian, > > Manjaro, Centos, Fedora, ScientificLinux, Zorin, and Windows being in u= se. > >=20 > > I see the same issue manifest on platforms running only Ubuntu gue= sts > as > > with guests of varying operating systems.=20=20 > >=20 > > The configuration file I used to compile this kernel is attached. = I > > compiled it with gcc 12.1.0. > >=20 > > This behavior does not manifest itself instantly, typically the > machine > > needs to be running 3-7 days before it does. Once it does guests keep > stalling > > and restarting libvirtd does not help. Only thing that seems to is a h= ard > > reboot of the physical host. For this reason I believe the issue lies > strictly > > with the host and not the guests. > >=20 > > I have listed it as a severity of high since it is completely serv= ice > > interrupting. > >=20 > > --=20 > > You may reply to this email to add a comment. > >=20 > > You are receiving this mail because: > > You are watching the assignee of the bug. --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=