From: Peter Zijlstra <peterz@infradead.org>
To: Bruno Goncalves <bgoncalv@redhat.com>
Cc: arjan@linux.intel.com, rafael.j.wysocki@intel.com,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [6.5.0-rc1] unchecked MSR access error: RDMSR from 0xe2 at rIP: 0xffffffff87090227 (native_read_msr+0x7/0x40) (intel_idle_init_cstates_icpu)
Date: Tue, 11 Jul 2023 13:24:21 +0200 [thread overview]
Message-ID: <20230711112421.GI3062772@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+QYu4qSBdhEgFURu+ouAf2d_JNPbZgCSUaxCLoGzMqDQOLWsQ@mail.gmail.com>
On Tue, Jul 11, 2023 at 11:11:44AM +0200, Bruno Goncalves wrote:
> Hello Arjan and Rafael,
>
> I'm not sure if you are the right person to contact about this, but
> we've noticed the following call trace when booting on KVM machines
> using kernel 6.5.0-rc1:
>
> [ 1.089740] io scheduler kyber registered
> [ 1.091080] io scheduler bfq registered
> [ 1.094696] atomic64_test: passed for x86-64 platform with CX8 and with SSE
> [ 1.097371] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
> [ 1.099559] unchecked MSR access error: RDMSR from 0xe2 at rIP:
> 0xffffffffa60912d7 (native_read_msr+0x7/0x40)
> [ 1.102725] Call Trace:
> [ 1.103547] <TASK>
> [ 1.104236] ? ex_handler_msr+0x121/0x130
> [ 1.105545] ? fixup_exception+0x234/0x310
> [ 1.106858] ? gp_try_fixup_and_notify+0x1d/0xb0
> [ 1.108342] ? exc_general_protection+0x147/0x420
> [ 1.109838] ? pcpu_block_refresh_hint+0x87/0xb0
> [ 1.111309] ? asm_exc_general_protection+0x26/0x30
> [ 1.112866] ? native_read_msr+0x7/0x40
> [ 1.114099] intel_idle_init_cstates_icpu.constprop.0+0x762/0x7f0
> [ 1.116063] intel_idle_init+0x31b/0x4c0
> [ 1.117315] ? __pfx_intel_idle_init+0x10/0x10
> [ 1.118734] do_one_initcall+0x5a/0x320
> [ 1.119981] kernel_init_freeable+0x31b/0x470
> [ 1.121373] ? __pfx_kernel_init+0x10/0x10
> [ 1.122681] kernel_init+0x1a/0x1c0
> [ 1.123796] ret_from_fork+0x29/0x50
> [ 1.124963] </TASK>
> [ 1.126012] input: Power Button as
> /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
> [ 1.128477] ACPI: button: Power Button [PWRF]
> [ 1.163767] ACPI: \_SB_.LNKB: Enabled at IRQ 10
> [ 1.193831] ACPI: \_SB_.LNKC: Enabled at IRQ 11
You forgot to say on what host hardware, what qemu options and you
forgot to run the above through scripts/decode_stacktrace.sh.
next prev parent reply other threads:[~2023-07-11 11:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 9:11 [6.5.0-rc1] unchecked MSR access error: RDMSR from 0xe2 at rIP: 0xffffffff87090227 (native_read_msr+0x7/0x40) (intel_idle_init_cstates_icpu) Bruno Goncalves
2023-07-11 11:24 ` Peter Zijlstra [this message]
2023-07-11 12:25 ` Bruno Goncalves
2023-07-11 12:55 ` Peter Zijlstra
2023-07-11 13:15 ` Peter Zijlstra
2023-07-11 13:25 ` Peter Zijlstra
2023-07-11 18:37 ` Wysocki, Rafael J
2023-07-11 18:39 ` Arjan van de Ven
2023-07-14 21:11 ` Peter Zijlstra
2023-07-14 21:47 ` Arjan van de Ven
2023-07-14 22:02 ` Peter Zijlstra
2023-07-14 21:10 ` Peter Zijlstra
2023-07-14 21:45 ` Arjan van de Ven
2023-07-14 21:55 ` Peter Zijlstra
2023-07-14 22:28 ` Peter Zijlstra
2023-07-11 14:26 ` Arjan van de Ven
2023-07-11 15:32 ` Peter Zijlstra
2023-07-11 14:22 ` Arjan van de Ven
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=20230711112421.GI3062772@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arjan@linux.intel.com \
--cc=bgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=x86@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