[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zm/TyyfZqtSI911M@xsang-OptiPlex-9020>
Date: Mon, 17 Jun 2024 14:12:27 +0800
From: Oliver Sang <oliver.sang@...el.com>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
CC: <oe-lkp@...ts.linux.dev>, <lkp@...el.com>, Linux Memory Management List
<linux-mm@...ck.org>, <netdev@...r.kernel.org>, <oliver.sang@...el.com>
Subject: Re: [linux-next:master] [rtnetlink] 8c6540cb2d:
hwsim.mesh_sae_failure.fail
hi, Tetsuo Handa,
On Fri, Jun 14, 2024 at 06:34:13PM +0900, Tetsuo Handa wrote:
> On 2024/06/14 17:48, kernel test robot wrote:
> > kernel test robot noticed "hwsim.mesh_sae_failure.fail" on:
> >
> > commit: 8c6540cb2d020c59b6f7013a2e8a13832906eee0 ("rtnetlink: print rtnl_mutex holder/waiter for debug purpose")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> >
> > [test failed on linux-next/master 6906a84c482f098d31486df8dc98cead21cce2d0]
> >
> > in testcase: hwsim
> > version: hwsim-x86_64-07c9f183e-1_20240402
> > with following parameters:
> >
> > test: mesh_sae_failure
> >
>
> That patch adds debug printk(). But dmesg.xz does not include printk() messages from
> that patch nor any oops-like messages. What went wrong?
>
sorr that we don't have enough knowledge to connect the issue with code change.
we just rebuild kernels for this commit and its parent, confirmed they are still
built with the config we shared in the link in our original report, then rerun
the tests, found still clean on parent, but reproduciable on this commit.
this is just FYI what we observed in our tests. if you want to look at this
further and you have a debug patch, we could do more tests with it. Thanks
9dcaf7df2635eb1c 8c6540cb2d020c59b6f7013a2e8
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:15 87% 15:15 hwsim.mesh_sae_failure.fail
Powered by blists - more mailing lists