From: Steven Rostedt <rostedt@goodmis.org>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
linux-cxl@vger.kernel.org
Subject: Re: RIP: 0010:trace_check_vprintf 6.12-rc1 & CXL test
Date: Thu, 3 Oct 2024 10:03:30 -0400 [thread overview]
Message-ID: <20241003100330.63538bcd@gandalf.local.home> (raw)
In-Reply-To: <Zv4USZVyEctYiCgM@aschofie-mobl2.lan>
On Wed, 2 Oct 2024 20:49:29 -0700
Alison Schofield <alison.schofield@intel.com> wrote:
> > > [ 110.737704] trace_event_buffer_commit+0x13b/0x280
> >
> > Hmm, do you have "tp_printk" on the kernel command line?
>
> Yes I did and when I remove it the problem goes away.
>
I know exactly what the bug is. I'll fix it and also add a "tp_printk" test
to my test suite :-p
-- Steve
prev parent reply other threads:[~2024-10-03 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 1:31 RIP: 0010:trace_check_vprintf 6.12-rc1 & CXL test Alison Schofield
2024-10-03 2:11 ` Steven Rostedt
2024-10-03 3:49 ` Alison Schofield
2024-10-03 14:03 ` Steven Rostedt [this message]
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=20241003100330.63538bcd@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.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