[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1kiuTIYobR4nexS@hirez.programming.kicks-ass.net>
Date: Wed, 26 Oct 2022 14:06:17 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: kernel test robot <yujie.liu@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, x86@...nel.org,
fengwei.yin@...el.com, ying.huang@...el.com
Subject: Re: [tip:x86/core] [kallsyms] f138918162:
WARNING:CPU:#PID:#at_fs/xfs/xfs_message.c:#xfs_buf_alert_ratelimited.cold-#[xfs]
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?
Powered by blists - more mailing lists