From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: usb0 failure
Date: Mon, 20 Jan 2014 12:53:44 +0000 [thread overview]
Message-ID: <52DD1C58.3040706@codethink.co.uk> (raw)
In-Reply-To: <52DD1B80.8090607@codethink.co.uk>
On 20/01/14 12:50, Ben Dooks wrote:
> I'm working with Simon's tree from 9th Jan with Valentin's patches
> as well as my own for FDT support and seeing the following failure
> for OHCI on channel0 failing to start. The other two channels are
> working fine.
I failed to mention that I was interested if anyone had seen the
following error before. I /think/ it may be a bridge initialisation
error as I've seen it on another architecture with badly configured
security.
> The OHCI for channel 0 initialising:
>
>> ohci-pci 0000:00:01.0: enabling bus mastering
>> ohci-pci 0000:00:01.0: OHCI PCI host controller
>> ohci-pci 0000:00:01.0: new USB bus registered, assigned bus number 4
>> ohci-pci 0000:00:01.0: irq 143, io mem 0xee080000
>> ohci-pci 0000:00:01.0: init err (00002edf 0000)
>> ohci-pci 0000:00:01.0: can't start
>> ohci-pci 0000:00:01.0: startup error -75
>> ohci-pci 0000:00:01.0: USB bus 4 deregistered
>> ohci-pci 0000:00:01.0: init 0000:00:01.0 fail, -75
>> ohci-pci: probe of 0000:00:01.0 failed with error -75
>
> For ref, the EHCI block for 0
>> ehci-pci 0000:01:02.0: EHCI Host Controller
>> ehci-pci 0000:01:02.0: new USB bus registered, assigned bus number 2
>> ehci-pci 0000:01:02.0: enabling Mem-Wr-Inval
>> ehci-pci 0000:01:02.0: irq 144, io mem 0xee0a1000
>> ehci-pci 0000:01:02.0: USB 2.0 started, EHCI 1.00
>
>
>
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
prev parent reply other threads:[~2014-01-20 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 12:50 usb0 failure Ben Dooks
2014-01-20 12:53 ` Ben Dooks [this message]
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=52DD1C58.3040706@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sh@vger.kernel.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).