[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZAocZRZh4FQRH3lc@smile.fi.intel.com>
Date: Thu, 9 Mar 2023 19:50:29 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>, linux-mm <linux-mm@...ck.org>,
Arnd Bergmann <arnd@...db.de>,
Anders Roxell <anders.roxell@...aro.org>,
Shuah Khan <shuah@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>
Subject: Re: selftests: gpio: crash on arm64
On Thu, Mar 09, 2023 at 09:33:29PM +0530, Naresh Kamboju wrote:
> Following kernel warnings and crash notices on arm64 Rpi4 device while
> running selftests: gpio on Linux mainline 6.3.0-rc1 kernel and Linux next.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
...
> [ 61.177432] *** DEADLOCK ***
> [ 61.177432]
> [ 61.177434] 3 locks held by modprobe/510:
> [ 61.177436] #0: ffff000040000698 (&n->list_lock){-.-.}-{2:2}, at:
> get_partial_node.part.0 (mm/slub.c:2271)
> [ 61.177448] #1: ffff80000b227f18 (console_lock){+.+.}-{0:0}, at:
> vprintk_emit (kernel/printk/printk.c:1936 kernel/printk/printk.c:2315)
> [ 61.177460] #2: ffff80000b228388 (console_srcu){....}-{0:0}, at:
> console_flush_all (include/linux/srcu.h:200 kernel/printk/printk.c:290
> kernel/printk/printk.c:2934)
How is it related to the GPIO?
Can you bisect if it's a regression somewhere?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists