All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Liu <b-liu-l0cyMroinI0@public.gmane.org>
To: Peter Ujfalusi <peter.ujfalusi-l0cyMroinI0@public.gmane.org>
Cc: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Linux OMAP List
	<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: usb: musb: regression since 4.9 on omap4-panda-es (caused by d8e5f0eca1e8)
Date: Tue, 4 Apr 2017 07:27:36 -0500	[thread overview]
Message-ID: <20170404122736.GA13673@uda0271908> (raw)
In-Reply-To: <2bf73b02-6e59-627a-c370-552ed94e7795-l0cyMroinI0@public.gmane.org>

On Tue, Apr 04, 2017 at 10:09:50AM +0300, Peter Ujfalusi wrote:
> Tony,
> 
> since 4.9 (4.8 was fine) I can not boot omap4-panda-es if the musb
> is compiled in. The kernel will stuck printing:
> 
> ** 206 printk messages dropped ** [    8.926727] musb_bus_suspend
> 2584: trying to suspend as a_idle while active

Does it sound a similar issue to
http://marc.info/?l=linux-usb&m=149036531809506&w=2

Regards,
-Bin.

> 
> The bisect (log is [1]) points to:
> d8e5f0eca1e8 usb: musb: Fix hardirq-safe hardirq-unsafe lock order error
> 
> and reverting the d8e5f0eca1e8 makes the board to boot up fine
> (Linux 4.11-rc5 and next-20170331).
> 
> any idea on how to fix this w/o reverting the commit?
> 
> [1] https://pastebin.com/Z2HJY229
> 
> - Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-04-04 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04  7:09 usb: musb: regression since 4.9 on omap4-panda-es (caused by d8e5f0eca1e8) Peter Ujfalusi
     [not found] ` <2bf73b02-6e59-627a-c370-552ed94e7795-l0cyMroinI0@public.gmane.org>
2017-04-04 12:27   ` Bin Liu [this message]
2017-04-04 14:03     ` Tony Lindgren
     [not found]       ` <20170404140341.GO10760-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-04-05  0:36         ` Tony Lindgren
     [not found]           ` <20170405003637.GB13234-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-04-05  7:13             ` Peter Ujfalusi
     [not found]               ` <dda7b6b0-b533-dfd6-1b12-b320bd69b623-l0cyMroinI0@public.gmane.org>
2017-04-05  7:29                 ` Peter Ujfalusi
2017-04-05 13:46                 ` Tony Lindgren
     [not found]                   ` <20170405134655.GD13234-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-04-05 15:29                     ` Tony Lindgren
     [not found]                       ` <20170405152954.GF13234-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-04-06 17:04                         ` Peter Ujfalusi
     [not found]                           ` <a86b6582-468f-04c8-cb22-0770f1e91e67-l0cyMroinI0@public.gmane.org>
2017-04-07 14:00                             ` Tony Lindgren
2017-04-06 19:07                         ` Bin Liu
2017-04-07 13:52                           ` Tony Lindgren
     [not found]                             ` <20170407135252.GG13234-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-04-07 14:18                               ` Bin Liu

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=20170404122736.GA13673@uda0271908 \
    --to=b-liu-l0cymroini0@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=peter.ujfalusi-l0cyMroinI0@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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 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.