[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <352f0709-f026-cd45-e60c-60dfd97f73f3@maine.edu>
Date: Wed, 11 Jun 2025 10:45:37 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org
cc: "Liang, Kan" <kan.liang@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>, Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>
Subject: [perf] crashing bug in icl_update_topdown_event
Hello
the perf_fuzzer found a hard-lock crash with current git on my RaptorLake
machine. Appears to be in icl_update_topdown_event()
this crashes the machine so hard that I had to take a picture with a
camera and transcribe the oops, let me know if there's missing info that
would help. (Also what's current best practices for getting dumps like
this on machines without serial ports for serial console?)
This does seem to be reproducible so I will try to investigate a bit more
too.
Vince
Oops: general protection fault, maybe for address 0xffff89aeceab400: 0000
CPU: 23 UID: 0 PID: 0 Comm: swapper/23
Tainted: [W]=WARN
Hardware name: Dell Inc. Precision 9660/0VJ762
RIP: 0010:native_read_pmc+0x7/0x40
Code: cc e8 8d a9 01 00 48 89 03 5b cd cc cc cc cc 0f 1f ...
RSP: 000:fffb03100273de8 EFLAGS: 00010046
....
Call Trace:
<TASK>
icl_update_topdown_event+0x165/0x190
? ktime_get+0x38/0xd0
intel_pmu_read_event+0xf9/0x210
__perf_event_read+0xf9/0x210
? __pfx___perf_event_read+0x10/0x10
__flush_smp_call_function_queue+0x37/0x70
do_idle+0x144/0x240
cpu_startup_entry+0x29/0x30
start_secondary+0x119/0x140
common_startup_64+0x13e/0x141
</TASK>
Modules linked in: ...
Powered by blists - more mailing lists