From: Nam Cao <namcao@linutronix.de>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Tomas Glozar <tglozar@redhat.com>, Juri Lelli <jlelli@redhat.com>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH v5 7/9] rv: Replace tss and sncid monitors with more complete sts
Date: Wed, 30 Jul 2025 16:16:43 +0200 [thread overview]
Message-ID: <20250730141643.RD-uucXa@linutronix.de> (raw)
In-Reply-To: <20250730125224.ScWqm03r@linutronix.de>
On Wed, Jul 30, 2025 at 02:52:25PM +0200, Nam Cao wrote:
> I do not have trace-cmd in the riscv image, but I do have perf. I will give
> it a try.
Instead, I replaced with tracepoints with trace_printk() and managed to
captured the log moments before disaster below.
I'm not sure what I'm seeing, just dumping this here, maybe you have an
idea.
Quite interesting that the last "normal" line for cpu1 is:
test-762 [001] dn... 112.407548: da_event_sts: cant_sched x irq_enable -> can_sched (final)
But in the next error line, it mentions the "enable_to_exit". Where did
this state come from??
<...>-1621 [001] d.... 119.919846: da_event_sts: rv: monitor sts does not allow event sched_switch on state enable_to_exit
Something very strange is going on here..
Nam
test-1198 [000] d.... 112.407332: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-762 [001] d.... 112.407338: da_event_sts: can_sched x irq_disable -> cant_sched
test-762 [001] d.... 112.407347: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-1198 [000] d.... 112.407351: da_event_sts: can_sched x irq_disable -> cant_sched
test-762 [001] d.... 112.407363: da_event_sts: can_sched x irq_disable -> cant_sched
test-1198 [000] d.h.. 112.407370: da_event_sts: cant_sched x irq_entry -> cant_sched
test-762 [001] d.h.. 112.407383: da_event_sts: cant_sched x irq_entry -> cant_sched
test-637 [002] dn... 112.407413: da_event_sts: cant_sched x irq_enable -> can_sched (final)
illegal-1091 [003] dns.. 112.407418: da_event_sts: in_irq x irq_enable -> scheduling
test-637 [002] .n... 112.407424: da_event_sts: can_sched x schedule_entry -> scheduling
illegal-1091 [003] dns.. 112.407431: da_event_sts: scheduling x irq_disable -> disable_to_switch
test-637 [002] dn... 112.407433: da_event_sts: scheduling x irq_disable -> disable_to_switch
illegal-1091 [003] dns.. 112.407438: da_event_sts: disable_to_switch x irq_enable -> enable_to_exit
illegal-1091 [003] dns.. 112.407448: da_event_sts: enable_to_exit x irq_disable -> enable_to_exit
test-1198 [000] dns.. 112.407459: da_event_sts: cant_sched x irq_enable -> can_sched (final)
illegal-1091 [003] dns.. 112.407460: da_event_sts: enable_to_exit x irq_enable -> enable_to_exit
test-637 [002] d.... 112.407468: da_event_sts: disable_to_switch x sched_switch -> switching
test-1198 [000] dns.. 112.407472: da_event_sts: can_sched x irq_disable -> cant_sched
illegal-1091 [003] dns.. 112.407472: da_event_sts: enable_to_exit x irq_disable -> enable_to_exit
illegal-1091 [003] dn... 112.407481: da_event_sts: enable_to_exit x irq_enable -> enable_to_exit
test-1198 [000] dns.. 112.407483: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-762 [001] dns.. 112.407488: da_event_sts: cant_sched x irq_enable -> can_sched (final)
illegal-1091 [003] dn... 112.407492: da_event_sts: enable_to_exit x irq_disable -> enable_to_exit
test-1198 [000] dns.. 112.407493: da_event_sts: can_sched x irq_disable -> cant_sched
test-762 [001] dns.. 112.407501: da_event_sts: can_sched x irq_disable -> cant_sched
test-1198 [000] dns.. 112.407501: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-762 [001] dns.. 112.407508: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-1198 [000] dns.. 112.407513: da_event_sts: can_sched x irq_disable -> cant_sched
test-649 [002] d.... 112.407517: da_event_sts: switching x irq_enable -> enable_to_exit
test-762 [001] dns.. 112.407518: da_event_sts: can_sched x irq_disable -> cant_sched
test-1198 [000] dns.. 112.407521: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-762 [001] dns.. 112.407529: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-649 [002] ..... 112.407530: da_event_sts: enable_to_exit x schedule_exit -> can_sched (final)
test-1198 [000] dns.. 112.407541: da_event_sts: can_sched x irq_disable -> cant_sched
test-762 [001] dns.. 112.407541: da_event_sts: can_sched x irq_disable -> cant_sched
test-1198 [000] dns.. 112.407548: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-762 [001] dn... 112.407548: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-1198 [000] dns.. 112.407560: da_event_sts: can_sched x irq_disable -> cant_sched
test-1198 [000] dns.. 112.407567: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-1198 [000] dns.. 112.407578: da_event_sts: can_sched x irq_disable -> cant_sched
test-1198 [000] dns.. 112.407585: da_event_sts: cant_sched x irq_enable -> can_sched (final)
test-649 [002] d.... 112.407596: da_event_sts: can_sched x irq_disable -> cant_sched
illegal-1091 [003] d.... 112.410126: da_event_sts: rv: monitor sts does not allow event sched_switch on state enable_to_exit
<...>-1621 [001] d.... 119.919846: da_event_sts: rv: monitor sts does not allow event sched_switch on state enable_to_exit
test-642 [001] d.... 121.459650: da_event_sts: rv: monitor sts does not allow event sched_switch on state enable_to_exit
next prev parent reply other threads:[~2025-07-30 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250728135022.255578-1-gmonaco@redhat.com>
2025-07-28 13:50 ` [PATCH v5 7/9] rv: Replace tss and sncid monitors with more complete sts Gabriele Monaco
2025-07-28 15:53 ` Nam Cao
2025-07-29 8:46 ` Gabriele Monaco
2025-07-29 9:25 ` Nam Cao
2025-07-29 9:37 ` Nam Cao
2025-07-29 14:06 ` Gabriele Monaco
2025-07-30 12:52 ` Nam Cao
2025-07-30 14:16 ` Nam Cao [this message]
2025-07-30 14:44 ` Nam Cao
2025-07-30 15:09 ` Nam Cao
2025-07-30 16:28 ` Nam Cao
2025-07-28 13:50 ` [PATCH v5 8/9] rv: Add nrp and sssw per-task monitors Gabriele Monaco
2025-07-28 15:56 ` Nam Cao
2025-07-28 13:50 ` [PATCH v5 9/9] rv: Add opid per-cpu monitor Gabriele Monaco
2025-07-28 15:58 ` Nam Cao
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=20250730141643.RD-uucXa@linutronix.de \
--to=namcao@linutronix.de \
--cc=gmonaco@redhat.com \
--cc=jkacur@redhat.com \
--cc=jlelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.com \
--cc=williams@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).