On Thu, Nov 12, 2020 at 05:54:30PM +0200, Tariq Toukan wrote:
>
>
> On 11/12/2020 5:46 PM, Ido Schimmel wrote:
> > On Thu, Nov 12, 2020 at 05:38:44PM +0200, Tariq Toukan wrote:
> > > Hi all,
> > >
> > > In the past ~2-3 weeks, we started seeing the following WARNING and traces
> > > in our regression testing systems, almost every day.
> > >
> > > Reproduction is not stable, and not isolated to a specific test, so it's
> > > hard to bisect.
> > >
> > > Any idea what could this be?
> > > Or what is the suspected offending patch?
> >
> > Do you have commit f8e48a3dca06 ("lockdep: Fix preemption WARN for spurious
> > IRQ-enable")? I think it fixed the issue for me
> >
>
> We do have it. Yet issue still exists.
I checked my mail and apparently we stopped seeing this warning after I
fixed a lockdep issue (spin_lock() vs spin_lock_bh()) in a yet to be
submitted patch. Do you see any other lockdep warnings in the log
besides this one? Maybe something in mlx4/5 which is why syzbot didn't
hit it?
