* usb0 failure
@ 2014-01-20 12:50 Ben Dooks
2014-01-20 12:53 ` Ben Dooks
0 siblings, 1 reply; 2+ messages in thread
From: Ben Dooks @ 2014-01-20 12:50 UTC (permalink / raw)
To: linux-sh
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.
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: usb0 failure
2014-01-20 12:50 usb0 failure Ben Dooks
@ 2014-01-20 12:53 ` Ben Dooks
0 siblings, 0 replies; 2+ messages in thread
From: Ben Dooks @ 2014-01-20 12:53 UTC (permalink / raw)
To: linux-sh
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-01-20 12:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-20 12:50 usb0 failure Ben Dooks
2014-01-20 12:53 ` Ben Dooks
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).