linux-kernel - [6.5.0-rc1] unchecked MSR access error: RDMSR from 0xe2 at rIP: 0xffffffff87090227 (native_read_msr+0x7/0x40) (intel_idle_init_cstates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+QYu4qSBdhEgFURu+ouAf2d_JNPbZgCSUaxCLoGzMqDQOLWsQ@mail.gmail.com>
Date:   Tue, 11 Jul 2023 11:11:44 +0200
From:   Bruno Goncalves <bgoncalv@...hat.com>
To:     arjan@...ux.intel.com, rafael.j.wysocki@...el.com
Cc:     x86@...nel.org, LKML <linux-kernel@...r.kernel.org>
Subject: [6.5.0-rc1] unchecked MSR access error: RDMSR from 0xe2 at rIP:
 0xffffffff87090227 (native_read_msr+0x7/0x40) (intel_idle_init_cstates_icpu)

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

We didn't bisect, but the first commit we hit this problem was [1] (6.4.0).

journal log [2], more logs [3] and cki issue tracker [4].

kernel build [5] and kernel config [6].

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d7868c41df58edabc4e408d119a1aef58a54d9d
[2] https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-public/926684240/4626306156/redhat%3A926684240/build_x86_64_redhat%3A926684240-x86_64-kernel/tests/6/results_0001/job.01/recipes/14200798/tasks/5/results/1689014206/logs/journalctl.log
[3] https://datawarehouse.cki-project.org/kcidb/tests/8725936
[4] https://datawarehouse.cki-project.org/issue/2128
[5] https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/926684240/publish%20x86_64/4626306101/artifacts/kernel-mainline.kernel.org-redhat_926684240-x86_64-kernel.tar.gz
[6] https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/926684240/build%20x86_64/4626306065/artifacts/kernel-mainline.kernel.org-redhat_926684240-x86_64-kernel.config

Thanks,
Bruno Goncalves