linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	"Kim Phillips" <kim.phillips@freescale.com>
Subject: USB failure on mpc8347 based board
Date: Tue, 20 Nov 2007 13:26:11 -0700	[thread overview]
Message-ID: <fa686aa40711201226o74b526fchebb547a8d08886fa@mail.gmail.com> (raw)

I'm seeing the following error on an MPC8347 based board.  The
physical board is wired up with the fsl-usb2-dr controller setup as a
USB device using port0 and fsl-usb2-mph as a USB host using port1.
The EHCI driver fails with the following error when initializing the
fsl-usb2-mph controller:

In particular I'm wondering if anyone knows the cause of "HC died; cleaning up".

The board has a hard wired USB hub connected to port1, and the host
controller seems to be dying while probing that device.

Cheers,
g.

[    0.754259] usbmon: debugfs is not available
[    0.758862] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
[    0.765948] fsl-ehci fsl-ehci.0: new USB bus registered, assigned
bus number 1
[    0.795863] fsl-ehci fsl-ehci.0: irq 39, io base 0xe0022000
[    0.801475] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[    0.809948] usb usb1: configuration #1 chosen from 1 choice
[    0.815971] hub 1-0:1.0: USB hub found
[    0.819778] hub 1-0:1.0: 2 ports detected
[    0.928972] USB Universal Host Controller Interface driver v3.0
[    0.935257] Initializing USB Mass Storage driver...
[    1.167836] usb 1-1: new high speed USB device using fsl-ehci and address 2
[    1.175150] fsl-ehci fsl-ehci.0: fatal error
[    1.179467] fsl-ehci fsl-ehci.0: HC died; cleaning up
[    1.184585] hub 1-0:1.0: cannot reset port 1 (err = -19)
[    1.189934] hub 1-0:1.0: cannot disable port 1 (err = -19)
[    1.195465] hub 1-0:1.0: cannot reset port 1 (err = -19)
[    1.200809] hub 1-0:1.0: cannot disable port 1 (err = -19)
[    1.206327] hub 1-0:1.0: cannot reset port 1 (err = -19)
[    1.211666] hub 1-0:1.0: cannot disable port 1 (err = -19)
[    1.217189] hub 1-0:1.0: cannot reset port 1 (err = -19)
[    1.222527] hub 1-0:1.0: cannot disable port 1 (err = -19)
[    1.228044] hub 1-0:1.0: cannot disable port 1 (err = -19)
[    1.233558] hub 1-0:1.0: hub_port_status failed (err = -19)
[    1.239246] usbcore: registered new interface driver usb-storage


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

                 reply	other threads:[~2007-11-20 20:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=fa686aa40711201226o74b526fchebb547a8d08886fa@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=kim.phillips@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).