[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4080cd7396e091b4864d58c452ecd13f6c3bbda9.camel@gmx.de>
Date: Tue, 08 Sep 2020 18:17:16 +0200
From: Mike Galbraith <efault@....de>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: v5.9-rc3-rt3 boot time networking lockdep splat
On Tue, 2020-09-08 at 18:02 +0200, Sebastian Andrzej Siewior wrote:
> On 2020-09-08 17:59:31 [+0200], Mike Galbraith wrote:
> > > I have no idea how to debug this based on this report. Can you narrow
> > > it down to something?
> >
> > I instrumented what I presume is still this problem once upon a time,
> > structures containing locks are allocated/initialized/freed again and
> > again with no cleanup until we increment into the wall.
>
> Any idea what it is?
No, that was quite some time ago.
> > > Is Lappy new, got a new something or has a new config switch? I'm just
> > > curious if this something or something that was always there but
> > > remained undetected.
> >
> > Nah, this is nothing new. Turn lockdep on in RT, it's just a matter of
> > time before it turns itself off. It's usually just not _that_ quick.
>
> Okay. So I have few boxes which run over the weekend without this splat.
Maybe obese config (attached) related. Lappy is an aging HP X360.
-Mike
View attachment "config" of type "text/plain" (214019 bytes)
Powered by blists - more mailing lists