Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 26 Oct 2022 14:06:17 +0200
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]
Message-ID: <Y1kiuTIYobR4nexS@hirez.programming.kicks-ass.net>
References: <202210241614.2ae4c1f5-yujie.liu@intel.com>
 <Y1kDEmLeRA2UGeF8@hirez.programming.kicks-ass.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Y1kDEmLeRA2UGeF8@hirez.programming.kicks-ass.net>
Precedence: bulk

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?