[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUdgSr5+rWijSmsg8DWGO8AXvD59D7YDT-wDyutHcS5Ww@mail.gmail.com>
Date: Tue, 17 Apr 2018 15:11:09 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Simon Horman <horms+renesas@...ge.net.au>
Cc: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
Magnus Damm <magnus.damm@...il.com>,
netdev <netdev@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Masaru Nagai <masaru.nagai.vx@...esas.com>,
Kazuya Mizuguchi <kazuya.mizuguchi.ks@...esas.com>
Subject: Re: [PATCH/RFC net-next 1/5] ravb: fix inconsistent lock state at
enabling tx timestamp
Hi Simon,
On Tue, Apr 17, 2018 at 10:50 AM, Simon Horman
<horms+renesas@...ge.net.au> wrote:
> From: Masaru Nagai <masaru.nagai.vx@...esas.com>
>
> [ 58.490829] =================================
> [ 58.495205] [ INFO: inconsistent lock state ]
> [ 58.499583] 4.9.0-yocto-standard-00007-g2ef7caf #57 Not tainted
Can this be triggered on contemporary kernels, too?
> [ 58.505529] ---------------------------------
> [ 58.509904] inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists