From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209867] CPU soft lockup/stall with nested KVM and SMP
Date: Fri, 27 Nov 2020 10:21:53 +0000 [thread overview]
Message-ID: <bug-209867-28872-xcp34crhy1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209867-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209867
Frantisek Sumsal (frantisek@sumsal.cz) changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version|5.9.9-arch1-1 |5.9.10-arch1-1
--- Comment #5 from Frantisek Sumsal (frantisek@sumsal.cz) ---
I noticed there's a MSR access error when trying to online secondary CPUs,
which may be relevant:
[ 3.969876] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
[ 3.973256] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user
pointer sanitization
[ 3.976544] Spectre V2 : Mitigation: Full AMD retpoline
[ 3.979874] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on
context switch
[ 3.983210] Spectre V2 : mitigation: Enabling conditional Indirect Branch
Prediction Barrier
[ 3.986544] Speculative Store Bypass: Mitigation: Speculative Store Bypass
disabled via prctl and seccomp
[ 3.990704] Freeing SMP alternatives memory: 32K
[ 3.997866] smpboot: CPU0: AMD Opteron 63xx class CPU (family: 0x15, model:
0x2, stepping: 0x0)
[ 4.001938] Performance Events: Fam15h core perfctr, AMD PMU driver.
[ 4.003261] ... version: 0
[ 4.006576] ... bit width: 48
[ 4.009900] ... generic registers: 6
[ 4.013234] ... value mask: 0000ffffffffffff
[ 4.016567] ... max period: 00007fffffffffff
[ 4.019900] ... fixed-purpose events: 0
[ 4.023233] ... event mask: 000000000000003f
[ 4.026887] rcu: Hierarchical SRCU implementation.
[ 4.030952] smp: Bringing up secondary CPUs ...
[ 4.034030] x86: Booting SMP configuration:
[ 4.036581] .... node #0, CPUs: #1
[ 1.328014] kvm-clock: cpu 1, msr 8801041, secondary cpu clock
[ 1.328014] smpboot: CPU 1 Converting physical 0 to logical die 1
[ 1.328014] unchecked MSR access error: WRMSR to 0x48 (tried to write
0x0000000000000000) at rIP: 0xffffffff9da6c984 (native_write_msr+0x4/0x20)
[ 1.328014] Call Trace:
[ 1.328014] x86_spec_ctrl_setup_ap+0x34/0x50
[ 1.328014] identify_secondary_cpu+0x6c/0x80
[ 1.328014] smp_store_cpu_info+0x45/0x50
[ 1.328014] start_secondary+0x58/0x160
[ 1.328014] secondary_startup_64+0xb6/0xc0
[ 6.088346] kvm-guest: stealtime: cpu 1, msr 1e66e080
[ 6.094247] #2
[ 1.328014] kvm-clock: cpu 2, msr 8801081, secondary cpu clock
[ 1.328014] smpboot: CPU 2 Converting physical 0 to logical die 2
[ 6.123987] kvm-guest: stealtime: cpu 2, msr 1e6ae080
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-11-27 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 12:13 [Bug 209867] New: CPU soft lockup/stall with nested KVM and SMP bugzilla-daemon
2020-10-26 13:10 ` [Bug 209867] " bugzilla-daemon
2020-10-26 13:10 ` bugzilla-daemon
2020-10-26 20:05 ` bugzilla-daemon
2020-11-02 16:16 ` bugzilla-daemon
2020-11-02 16:24 ` bugzilla-daemon
2020-11-09 10:59 ` bugzilla-daemon
2020-11-12 10:02 ` bugzilla-daemon
2020-11-21 16:19 ` bugzilla-daemon
2020-11-27 10:21 ` bugzilla-daemon [this message]
2020-12-01 8:39 ` bugzilla-daemon
2020-12-04 11:57 ` bugzilla-daemon
2020-12-23 12:31 ` 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=bug-209867-28872-xcp34crhy1@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).