[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1581058605.7924.15.camel@gmx.de>
Date: Fri, 07 Feb 2020 07:56:45 +0100
From: Mike Galbraith <efault@....de>
To: Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [ANNOUNCE] v5.4.17-rt9
On Thu, 2020-02-06 at 22:13 -0800, Fernando Lopez-Lezcano wrote:
> On 2/6/20 10:11 PM, Mike Galbraith wrote:
> > On Thu, 2020-02-06 at 15:59 -0800, Fernando Lopez-Lezcano wrote:
> >> On 2/4/20 8:58 AM, Sebastian Andrzej Siewior wrote:
> >>> Dear RT folks!
> >>>
> >>> I'm pleased to announce the v5.4.17-rt9 patch set.
> >>
> >> Thanks!
> >> I see a continuous stream of these:
> >
> > (snips gripage)
> >
> > Yup, d67739268cf0 annoys RT locking if lockdep is enabled. The below
> > shut it up for my i915 equipped lappy.
>
> Wow, Mike, thanks!, will try it out and report...
> (might take me a couple of days)
I suspect you could just change the IS_ENABLED line to exclude
CONFIG_PREEMPT_RT from the lockdep hack instead. Replacing
local_irq_disable() with a local lock is the routine fix, but in this
case it more closely resembles putting a bandaid on a bandaid :)
-Mike
Powered by blists - more mailing lists