From: Peter Chen <peter.chen@nxp.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: usb: chipidea: udc: BUG: sleeping function called from invalid context
Date: Fri, 6 Mar 2020 01:53:41 +0000 [thread overview]
Message-ID: <20200306015344.GA29800@b29397-desktop> (raw)
In-Reply-To: <7a142dd4-9ae8-2560-e5be-25648f88a864@gmail.com>
On 20-03-05 23:53:46, Dmitry Osipenko wrote:
> 05.03.2020 05:12, Peter Chen пишет:
> > On 20-03-04 19:10:08, Dmitry Osipenko wrote:
> >> Hello,
> >>
> >> I was trying out today's linux-next-20200304 and noticed this splat in KMSG:
> >>
> ...
> >> I haven't tried to figure out what change causes this problem, it didn't
> >> happen using next-20200218. Please take a look, thanks in advance.
> >
> > Dmitry, thanks for reporting. I haven't met that issue, it maybe I
> > enable runtime pm, but you have not? So I don't trigger
> > "dev->power.runtime_status != RPM_ACTIVE" condition below
> >
> > might_sleep_if(!(rpmflags & RPM_ASYNC) && !dev->power.irq_safe &&
> > dev->power.runtime_status != RPM_ACTIVE);
>
> The runtime PM always presents on Tegra, do you have
> CONFIG_DEBUG_ATOMIC_SLEEP=y in the kernel's config?
>
No, the reason should be "dev->power.runtime_status != RPM_ACTIVE", your
ci device's runtime may not be active at that time, if I move the spinlock
above pm_runtime_get_sync at ci_hdrc_gadget_connect, I could reproduce it
too.
I enabled CONFIG_DEBUG_ATOMIC_SLEEP, but can't reproduce the dump
without above changes.
--
Thanks,
Peter Chen
next prev parent reply other threads:[~2020-03-06 1:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 16:10 usb: chipidea: udc: BUG: sleeping function called from invalid context Dmitry Osipenko
2020-03-05 2:12 ` Peter Chen
2020-03-05 20:53 ` Dmitry Osipenko
2020-03-06 1:53 ` Peter Chen [this message]
2020-03-06 2:38 ` Dmitry Osipenko
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=20200306015344.GA29800@b29397-desktop \
--to=peter.chen@nxp.com \
--cc=digetx@gmail.com \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.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;
as well as URLs for NNTP newsgroup(s).