Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peter Chen <peter.chen-3arQi8VN3Tc@public.gmane.org>
Cc: "linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: usb: chipidea: udc: BUG: sleeping function called from invalid context
Date: Thu, 5 Mar 2020 23:53:46 +0300	[thread overview]
Message-ID: <7a142dd4-9ae8-2560-e5be-25648f88a864@gmail.com> (raw)
In-Reply-To: <20200305021226.GA12837@b29397-desktop>

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?

> I send the fix patch, but git send-email seems doesn't add auto cc
> according to reported-by tag, so you are not at cc list. Would you
> please have a test?

It fixes the problem, thanks!

  reply	other threads:[~2020-03-05 20: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
     [not found] ` <bfa5b2f7-cf52-0055-ffb2-2cb8278a1181-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-05  2:12   ` Peter Chen
2020-03-05 20:53     ` Dmitry Osipenko [this message]
     [not found]       ` <7a142dd4-9ae8-2560-e5be-25648f88a864-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-06  1:53         ` Peter Chen
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=7a142dd4-9ae8-2560-e5be-25648f88a864@gmail.com \
    --to=digetx-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=peter.chen-3arQi8VN3Tc@public.gmane.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