From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, linux-mm <linux-mm@kvack.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Shuah Khan <shuah@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: selftests: gpio: crash on arm64
Date: Thu, 9 Mar 2023 19:50:29 +0200 [thread overview]
Message-ID: <ZAocZRZh4FQRH3lc@smile.fi.intel.com> (raw)
In-Reply-To: <CA+G9fYv94gx8+-JMzbmQaue3q3y6QdBmsGUCdD-26X5XavL3Ag@mail.gmail.com>
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@linaro.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
next prev parent reply other threads:[~2023-03-09 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 16:03 Naresh Kamboju
2023-03-09 17:50 ` Andy Shevchenko [this message]
2023-04-10 9:16 ` Naresh Kamboju
2023-04-11 8:57 ` Linus Walleij
2023-04-11 13:11 ` Bartosz Golaszewski
2023-06-20 16:40 ` Andy Shevchenko
2023-11-07 13:51 ` Naresh Kamboju
2023-11-15 1:42 ` andy.shevchenko
2023-11-15 15:37 ` Naresh Kamboju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZAocZRZh4FQRH3lc@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox