From: Vince Weaver <vincent.weaver@maine.edu>
To: Kan Liang <kan.liang@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [perf] unchecked MSR access error: WRMSR to 0x689 in intel_pmu_lbr_restore
Date: Fri, 8 Jul 2022 12:13:43 -0400 (EDT) [thread overview]
Message-ID: <e71fa75-a718-ffb-c3f3-40cccf77ba9b@maine.edu> (raw)
In-Reply-To: <66961a7d-a6d8-2536-9ed3-68c2e7f4e03d@maine.edu>
On Wed, 6 Jul 2022, Vince Weaver wrote:
> Let the fuzzer running a long time on 5.19-rc1 and after a few weeks it
> triggered this weird trace. It is repeatable (although I haven't
> narrowed down exactly what's causing it).
>
> It's odd in that it just dumps a <TASK>, it doesn't provide any info on
> what the actual trigger is.
>
> This is on a Haswell machine.
I bumped up to current git and managed to trigger this again, this time
it actually managed to print the error message.
[ 7763.384369] unchecked MSR access error: WRMSR to 0x689 (tried to write 0x1fffffff8101349e) at rIP: 0xffffffff810704a4 (native_write_msr+0x4/0x20)
[ 7763.397420] Call Trace:
[ 7763.399881] <TASK>
[ 7763.401994] intel_pmu_lbr_restore+0x9a/0x1f0
[ 7763.406363] intel_pmu_lbr_sched_task+0x91/0x1c0
[ 7763.410992] __perf_event_task_sched_in+0x1cd/0x240
[ 7763.415879] ? __perf_event_task_sched_out+0x75/0x5c0
[ 7763.420939] finish_task_switch.isra.0+0x15b/0x2a0
[ 7763.425740] ? __switch_to+0x112/0x430
[ 7763.429503] __schedule+0x2cf/0x10d0
[ 7763.433088] ? send_signal_locked+0xc8/0x130
[ 7763.437364] schedule+0x4e/0xb0
[ 7763.440518] do_wait+0x15b/0x2f0
[ 7763.443757] kernel_wait4+0xa6/0x140
[ 7763.447337] ? thread_group_exited+0x60/0x60
[ 7763.451608] do_syscall_64+0x3b/0xc0
[ 7763.455199] entry_SYSCALL_64_after_hwframe+0x46/0xb0
[ 7763.460259] RIP: 0033:0x7f9063feba26
[ 7763.463838] Code: ff e9 0e 00 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 11 b8 3d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 5a c3 90 48 83 ec 28 89 54 24 14 48 89 74 24
[ 7763.482587] RSP: 002b:00007ffca3875c08 EFLAGS: 00000246 ORIG_RAX: 000000000000003d
[ 7763.490161] RAX: ffffffffffffffda RBX: 000000000000000c RCX: 00007f9063feba26
[ 7763.497303] RDX: 0000000000000000 RSI: 00007ffca3875c1c RDI: 0000000000002214
[ 7763.504441] RBP: 00007ffca3875c20 R08: 00007f90640f321c R09: 00007f90640f3240
[ 7763.511577] R10: 0000000000000000 R11: 0000000000000246 R12: 000055d6ce93c4f0
[ 7763.518718] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 7763.525850] </TASK>
next prev parent reply other threads:[~2022-07-08 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 21:14 [perf] odd fuzzer generated trace " Vince Weaver
2022-07-08 16:13 ` Vince Weaver [this message]
2022-07-11 15:25 ` [perf] unchecked MSR access error: WRMSR to 0x689 " Liang, Kan
2022-07-11 21:13 ` Vince Weaver
2022-07-12 0:11 ` Liang, Kan
2022-07-11 22:16 ` Pawan Gupta
2022-07-12 19:39 ` Vince Weaver
2022-07-12 20:48 ` Pawan Gupta
2022-07-12 21:26 ` Vince Weaver
2022-07-12 23:08 ` Liang, Kan
2022-07-14 16:12 ` Vince Weaver
2022-07-14 17:50 ` Liang, Kan
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=e71fa75-a718-ffb-c3f3-40cccf77ba9b@maine.edu \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®