From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <yujie.liu@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
fengwei.yin@intel.com, ying.huang@intel.com
Subject: Re: [tip:x86/core] [kallsyms] f138918162: WARNING:CPU:#PID:#at_fs/xfs/xfs_message.c:#xfs_buf_alert_ratelimited.cold-#[xfs]
Date: Wed, 26 Oct 2022 14:06:17 +0200 [thread overview]
Message-ID: <Y1kiuTIYobR4nexS@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <Y1kDEmLeRA2UGeF8@hirez.programming.kicks-ass.net>
On Wed, Oct 26, 2022 at 11:51:14AM +0200, Peter Zijlstra wrote:
> On Wed, Oct 26, 2022 at 05:10:28PM +0800, kernel test robot wrote:
> > Hi Peter,
> >
> > For below patch, we couldn't find any connection between the code
> > change of kallsyms and xfstests testcase, but we got very stable test
> > results. We tested commit f1389181622a and its parent commit
> > 7825451fa4dc for 12 runs each, parent was 100% good while this commit
> > was 100% bad, so we still send out this report FYI though we don't have
> > clear clue of the root cause. Please check the details below if
> > interested in further investigation. Thanks.
>
> *groan* I'll go have a poke.
>
dmesg starts at 42 seconds, you don't happen to have a complete one?
next prev parent reply other threads:[~2022-10-26 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 9:10 [tip:x86/core] [kallsyms] f138918162: WARNING:CPU:#PID:#at_fs/xfs/xfs_message.c:#xfs_buf_alert_ratelimited.cold-#[xfs] kernel test robot
2022-10-26 9:51 ` Peter Zijlstra
2022-10-26 12:06 ` Peter Zijlstra [this message]
2022-10-27 2:09 ` Yujie Liu
2022-10-27 2:24 ` Yujie Liu
2022-10-27 16:20 ` Darrick J. Wong
2022-10-27 16:51 ` Peter Zijlstra
2022-10-28 19:52 ` Peter Zijlstra
2022-11-02 9:20 ` [tip: x86/core] kallsyms: Revert "Take callthunks into account" tip-bot2 for Peter Zijlstra
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=Y1kiuTIYobR4nexS@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=yujie.liu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.