From: Tony Luck <tony.luck@intel.com>
To: rostedt@goodmis.org, Aristeu Rozanski <aris@ruivo.org>,
linux-kernel@vger.kernel.org
Subject: rasdaemon broke between v6.0 and v6.3?
Date: Wed, 19 Jul 2023 16:35:54 -0700 [thread overview]
Message-ID: <ZLhzWoyRCWN0FmqE@agluck-desk3> (raw)
[resend as plain text - sorry for the earlier HTML]
An internal team is seeing tests that worked on v6.0 fail on v6.3. The problem is that
rasdaemon isn’t waking up to process the “mce_record” trace events.
Manually checking for them works:
root@R-4251:/sys/kernel/debug/tracing>systemctl stop rasdaemon
root@R-4251:/sys/kernel/debug/tracing>
root@R-4251:/sys/kernel/debug/tracing>
root@R-4251:/sys/kernel/debug/tracing>echo 1 > events/mce/mce_record/enable
root@R-4251:/sys/kernel/debug/tracing>
root@R-4251:/sys/kernel/debug/tracing>cat trace_pipe
<...>-235 [000] ..... 596.892583: mce_record: CPU: 0, MCGc/s: f000c15/0, MC13: 8c00004200800090, IPID: 0000000000000000, ADDR/MISC/SYND: 0000000123450000/08000a80c2982086/0000000000000000, RIP: 00:<0000000000000000>, TSC: 14120b051a1, PROCESSOR: 0:c06f1, TIME: 1689802780, SOCKET: 0, APIC: 0
kworker/0:2-235 [000] ..... 597.204343: mce_record: CPU: 0, MCGc/s: f000c15/0, MC255: 9c0000000000009f, IPID: 0000000000000000, ADDR/MISC/SYND: 0000000123450000/000000000000008c/0000000000000000, RIP: 00:<0000000000000000>, TSC: 0, PROCESSOR: 0:c06f1, TIME: 1689802781, SOCKET: 0, APIC: 0
So their tests are injecting errors, and the trace event is firing.
Is there some updated version of rasdaemon needed?
Some kernel CONFIG option problem?
-Tony
next reply other threads:[~2023-07-19 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 23:35 Tony Luck [this message]
2023-07-20 3:03 ` Aristeu Rozanski
2023-07-20 10:40 ` Steven Rostedt
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=ZLhzWoyRCWN0FmqE@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=aris@ruivo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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®