public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Cc: linux-usb <linux-usb@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	sarah.a.sharp@linux.intel.com
Subject: Re: Missing USB XHCI and EHCI reset for kexec
Date: Sat, 07 Jun 2014 18:15:42 +1000	[thread overview]
Message-ID: <1402128942.3247.292.camel@pasglop> (raw)
In-Reply-To: <1397588067.21321.11.camel@vger.seibold.net>

On Tue, 2014-04-15 at 20:54 +0200, Stefani Seibold wrote:

> > > > > >>>>[    1.170029] xhci_hcd 0001:03:00.0: xHCI Host Controller
> > > > > >>>>[    1.175306] xhci_hcd 0001:03:00.0: new USB bus registered,
> > > > > >>>>assigned bus number 1
> > > > > >>>>[    1.212561] xhci_hcd 0001:03:00.0: Host not halted after 16000
> > > > > >>>>microseconds.
> > > > > >>>>[    1.219621] xhci_hcd 0001:03:00.0: can't setup: -110
> > > > > >>>>[    1.224597] xhci_hcd 0001:03:00.0: USB bus 1 deregistered
> > > > > >>>>[    1.230021] xhci_hcd 0001:03:00.0: init 0001:03:00.0 fail, -110
> > > > > >>>>[    1.235955] xhci_hcd: probe of 0001:03:00.0 failed with error -110
> > > > > >>>>

Cascardo, Alan,

Bringing back that old thread..

I'm trying to kexec from our OPAL FW bootloader (3.10.23 based) to a
fedora 3.14.3 on a new machine and am still seeing the above.

A reset brings the chip back.

Do we have any resolution here ? It looks like the xHCI remains active
on the way out and is clagged up on the way back in, at least in a
state the driver really doesn't like.

And this is a "clean" kexec, not a forced one... This is killing USB on
the upcoming OpenPower dev machines.

Cheers,
Ben.



  reply	other threads:[~2014-06-07  8:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 19:22 Missing USB XHCI and EHCI reset for kexec Stefani Seibold
2014-04-14  2:14 ` Alan Stern
2014-04-14 13:54   ` stefani
2014-04-14 14:49     ` Alan Stern
2014-04-14 15:25       ` stefani
2014-04-14 16:27         ` Alan Stern
2014-04-14 16:35           ` Stefani Seibold
2014-04-14 17:58             ` Alan Stern
2014-04-15 18:32               ` Stefani Seibold
2014-04-15 19:05                 ` Alan Stern
2014-04-15 19:08                   ` Stefani Seibold
2014-04-15 18:30           ` Stefani Seibold
2014-04-15 19:02             ` Alan Stern
2014-04-15 19:06               ` Stefani Seibold
2014-04-15 19:14                 ` Alan Stern
2014-04-15 19:17                   ` Stefani Seibold
2014-04-15 19:14               ` Stefani Seibold
2014-04-15 19:34                 ` Alan Stern
2014-04-14  9:42 ` Benjamin Herrenschmidt
2014-04-14 15:44   ` stefani
2014-04-14 21:48     ` Thadeu Lima de Souza Cascardo
2014-04-15 10:04       ` stefani
2014-04-15 12:20         ` Thadeu Lima de Souza Cascardo
2014-04-15 15:00           ` stefani
2014-04-15 18:33             ` Thadeu Lima de Souza Cascardo
2014-04-15 18:42               ` Stefani Seibold
2014-04-15 18:49                 ` Thadeu Lima de Souza Cascardo
2014-04-15 18:54                   ` Stefani Seibold
2014-06-07  8:15                     ` Benjamin Herrenschmidt [this message]
2014-06-07 15:40                       ` Alan Stern
2014-06-07 21:11                         ` Benjamin Herrenschmidt
2014-06-07 22:35                         ` Benjamin Herrenschmidt
2014-06-08  1:09                           ` Alan Stern

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=1402128942.3247.292.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=cascardo@linux.vnet.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=stern@rowland.harvard.edu \
    /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