All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr-l0cyMroinI0@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
	Felipe Balbi
	<felipe.balbi-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Greg KH
	<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
	Carlos Hernandez <ceh-l0cyMroinI0@public.gmane.org>,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: usb-related linux-next boot failures
Date: Wed, 28 Jun 2017 16:21:28 +0530	[thread overview]
Message-ID: <34a37d06-1929-814b-3476-6eaa5a45cd39@ti.com> (raw)
In-Reply-To: <20170628103014.GC3730-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>



On Wednesday 28 June 2017 04:00 PM, Tony Lindgren wrote:
>  Felipe Balbi <felipe.balbi-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> [170628 01:32]:
>> Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org> writes:
>>> On Tue, Jun 27, 2017 at 02:28:56PM -0400, Carlos Hernandez wrote:
>>>> Still seeing AM57xx/DRA72/DRA7x usb-related boot failures on linux-next...
>>>
>>> Is this a regression?  If so, any specific commit that caused it?
>>
>> I did ask for a bisection last time but nobody from TI replied ;-)
>>
>> https://marc.info/?i=87h8zi4gmx.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
>>
>> Can't really help without bisection logs :-)
> 
> Seems this warning got add with 04c848d39879 ("genirq: Warn when
> IRQ_NOAUTOEN is used with shared interrupts"). The fix is to get
> rid of IRQ_NOAUTOEN and enable_irq for a shared interrupt. Hard
> to say as the warning line does not match the version of next I
> have so this should be verified.
> 

There seems to be two different problems here.
One is what Tony is pointing to above that throws a first warn dump
during dwc3_omap_probe().

Second one is the imprecise external abort that happens later:
[   24.809939] Unhandled fault: imprecise external abort (0x1406) at
0x00000000

Bisecting the second issue lead to the first bad commit as:
commit f54edb539c1167e7a96073848d0afad100df4580
Author: Felipe Balbi <felipe.balbi-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Date:   Mon Jun 5 17:03:18 2017 +0300

    usb: dwc3: core: initialize ULPI before trying to get the PHY

    If don't reorder initialization like this, we will never be able to
    get a reference to ULPI PHYs.

    Signed-off-by: Felipe Balbi <felipe.balbi-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>



Reverting above commit from -next seems to help.


-- 
Regards
Vignesh
--
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-06-28 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 18:28 usb-related linux-next boot failures Carlos Hernandez
     [not found] ` <0d1a491c-41c4-a02d-cdf8-e1a95a1fe989-l0cyMroinI0@public.gmane.org>
2017-06-28  4:55   ` Greg KH
     [not found]     ` <20170628045543.GA28759-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-06-28  8:31       ` Felipe Balbi
     [not found]         ` <87r2y45x97.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-06-28 10:30           ` Tony Lindgren
     [not found]             ` <20170628103014.GC3730-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-06-28 10:51               ` Vignesh R [this message]
     [not found]                 ` <34a37d06-1929-814b-3476-6eaa5a45cd39-l0cyMroinI0@public.gmane.org>
2017-06-28 10:54                   ` Felipe Balbi
     [not found]                     ` <87k23w5qn2.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-06-28 13:38                       ` Vignesh R
     [not found]                         ` <71bae311-f85b-4fe1-06c2-d43bfee42b88-l0cyMroinI0@public.gmane.org>
2017-06-29  5:54                           ` Felipe Balbi
2017-06-28 17:13               ` Grygorii Strashko

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=34a37d06-1929-814b-3476-6eaa5a45cd39@ti.com \
    --to=vigneshr-l0cymroini0@public.gmane.org \
    --cc=ceh-l0cyMroinI0@public.gmane.org \
    --cc=felipe.balbi-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@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.