From: Mark Brown <broonie@kernel.org>
To: Fei Shao <fshao@chromium.org>
Cc: Jiaxin Yu <jiaxin.yu@mediatek.com>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: mt8186: Fix mutex double unlock in GPIO request
Date: Fri, 17 Jun 2022 11:43:04 +0100 [thread overview]
Message-ID: <YqxauLOp2sWOU/uc@sirena.org.uk> (raw)
In-Reply-To: <20220617100632.1447811-1-fshao@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Fri, Jun 17, 2022 at 06:06:33PM +0800, Fei Shao wrote:
> The lockdep mechanism reveals an unbalanced unlocking on MT8186:
>
> [ 2.993966] WARNING: bad unlock balance detected!
> [ 2.993971] 5.15.46-421fef3b44d7-lockdep #16 Not tainted
> [ 2.993978] -------------------------------------
> [ 2.993983] kworker/u16:1/10 is trying to release lock (gpio_request_mutex) at:
> [ 2.993994] [<ffffffdcd9adebf8>] mt8186_afe_gpio_request+0xf8/0x210
> [ 2.994012] but there are no more locks to release!
> [ 2.994017]
> [ 2.994017] other info that might help us debug this:
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Fei Shao <fshao@chromium.org>
Cc: alsa-devel@alsa-project.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jiaxin Yu <jiaxin.yu@mediatek.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: mediatek: mt8186: Fix mutex double unlock in GPIO request
Date: Fri, 17 Jun 2022 11:43:04 +0100 [thread overview]
Message-ID: <YqxauLOp2sWOU/uc@sirena.org.uk> (raw)
In-Reply-To: <20220617100632.1447811-1-fshao@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Fri, Jun 17, 2022 at 06:06:33PM +0800, Fei Shao wrote:
> The lockdep mechanism reveals an unbalanced unlocking on MT8186:
>
> [ 2.993966] WARNING: bad unlock balance detected!
> [ 2.993971] 5.15.46-421fef3b44d7-lockdep #16 Not tainted
> [ 2.993978] -------------------------------------
> [ 2.993983] kworker/u16:1/10 is trying to release lock (gpio_request_mutex) at:
> [ 2.993994] [<ffffffdcd9adebf8>] mt8186_afe_gpio_request+0xf8/0x210
> [ 2.994012] but there are no more locks to release!
> [ 2.994017]
> [ 2.994017] other info that might help us debug this:
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Fei Shao <fshao@chromium.org>
Cc: Jiaxin Yu <jiaxin.yu@mediatek.com>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: mt8186: Fix mutex double unlock in GPIO request
Date: Fri, 17 Jun 2022 11:43:04 +0100 [thread overview]
Message-ID: <YqxauLOp2sWOU/uc@sirena.org.uk> (raw)
In-Reply-To: <20220617100632.1447811-1-fshao@chromium.org>
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
On Fri, Jun 17, 2022 at 06:06:33PM +0800, Fei Shao wrote:
> The lockdep mechanism reveals an unbalanced unlocking on MT8186:
>
> [ 2.993966] WARNING: bad unlock balance detected!
> [ 2.993971] 5.15.46-421fef3b44d7-lockdep #16 Not tainted
> [ 2.993978] -------------------------------------
> [ 2.993983] kworker/u16:1/10 is trying to release lock (gpio_request_mutex) at:
> [ 2.993994] [<ffffffdcd9adebf8>] mt8186_afe_gpio_request+0xf8/0x210
> [ 2.994012] but there are no more locks to release!
> [ 2.994017]
> [ 2.994017] other info that might help us debug this:
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-17 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:06 [PATCH] ASoC: mediatek: mt8186: Fix mutex double unlock in GPIO request Fei Shao
2022-06-17 10:06 ` Fei Shao
2022-06-17 10:06 ` Fei Shao
2022-06-17 10:06 ` Fei Shao
2022-06-17 10:43 ` Mark Brown [this message]
2022-06-17 10:43 ` Mark Brown
2022-06-17 10:43 ` Mark Brown
2022-06-17 11:07 ` Fei Shao
2022-06-17 11:07 ` Fei Shao
2022-06-17 11:07 ` Fei Shao
2022-06-17 23:19 ` Mark Brown
2022-06-17 23:19 ` Mark Brown
2022-06-17 23:19 ` Mark Brown
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=YqxauLOp2sWOU/uc@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=fshao@chromium.org \
--cc=jiaxin.yu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.