Problems with usb-ohci on 2.4.22-preX

Problems with usb-ohci on 2.4.22-preX

[Ruben Puettmann]

        hy,

i try to install linux on my new motherboard EPOX 8RDA3+ 
with nvidia nforce2 chipset.

If I try to attached some usb devices ( usb memory stick ) I got this
errors ( 2.4.22-pre5 pre2..): 


PCI: Setting latency timer of device 00:02.2 to 64
ehci_hcd 00:02.2: nVidia Corporation nForce2 USB Controller
ehci_hcd 00:02.2: irq 20, pci mem f88eb000
usb.c: new USB bus registered, assigned bus number 1
PCI: 00:02.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
PCI: 00:02.2 PCI cache line size corrected to 64.
ehci_hcd 00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
hub.c: USB hub found
hub.c: 6 ports detected
PCI: Setting latency timer of device 00:02.0 to 64
usb-ohci.c: USB OHCI at membase 0xf88f3000, IRQ 20
usb-ohci.c: usb-00:02.0, nVidia Corporation nForce2 USB Controller
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
PCI: Setting latency timer of device 00:02.1 to 64
usb-ohci.c: USB OHCI at membase 0xf88f5000, IRQ 22
usb-ohci.c: usb-00:02.1, nVidia Corporation nForce2 USB Controller (#2)
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 3 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1
usb-uhci.c: $Revision: 1.275 $ time 15:11:40 Jul 12 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:02.1-3, assigned address 2
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=2 (error=-110)
hub.c: new USB device 00:02.1-3, assigned address 3
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=3 (error=-110)
eth0: Setting 10mbps full-duplex based on auto-negotiated partner ability 4461.
eth0.2: add 01:00:5e:00:00:01 mcast address to master interface
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (7168 buckets, 57344 max) - 292 bytes per conntrack
hub.c: new USB device 00:02.0-3, assigned address 2
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: unable to get device descriptor (error=-12)
hub.c: new USB device 00:02.0-3, assigned address 3
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=3 (error=-110)
hub.c: new USB device 00:02.1-2, assigned address 4
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=4 (error=-110)
hub.c: new USB device 00:02.1-2, assigned address 5
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=5 (error=-110)

This happend's with usb-ohci and usb-ehci loaded or only with usb-ohci.


        thanks for help 

                Ruben


-- 
Ruben Puettmann
ruben@puettmann.net
http://www.puettmann.net

Re: Problems with usb-ohci on 2.4.22-preX

[Greg KH]

On Sat, Jul 12, 2003 at 04:14:31PM +0200, Ruben Puettmann wrote:
> 
>         hy,
> 
> i try to install linux on my new motherboard EPOX 8RDA3+ 
> with nvidia nforce2 chipset.
> 
> If I try to attached some usb devices ( usb memory stick ) I got this
> errors ( 2.4.22-pre5 pre2..): 

Do any other USB devices work?
Can you boot with/without acpi (the opposite of whatever you just did.)
How about booting with noapic?

thanks,

greg k-h

Re: Problems with usb-ohci on 2.4.22-preX

[Ruben Puettmann]

On Sat, Jul 12, 2003 at 09:21:31PM -0700, Greg KH wrote:
 > 
> > i try to install linux on my new motherboard EPOX 8RDA3+ 
> > with nvidia nforce2 chipset.
> > 
> > If I try to attached some usb devices ( usb memory stick ) I got this
> > errors ( 2.4.22-pre5 pre2..): 
> 
> Do any other USB devices work?

soory no no other usb device here. I mean that the internal CF/SD/MMC
reader runs with usb-storage too.

> Can you boot with/without acpi (the opposite of whatever you just did.)

I disable ACPI in bios and boot with noacpi I get the message:

spurious 8259A Interrupt 7

But usb storage seems to work ( the usb-storage found the internal
CF/SD/MMC card reader.

But then the System is frozen. No reaktion from system on attaching the
usb stick or making any keypress. SYSREQ does not work. 

Nothing in the logfiles.

> How about booting with noapic?

I have try this but it will not do :

First try :

booting with noapic :

There were much CPU(0) APIC error's so the System was unusable.

APIC error on CPU0: 40(40)


After disable apic in bios and boot with noapic ext3 can not mount my
filesystem and there is an oops. The oops was not logged so I can't make
an backtrace.

So it seems that the usb-storage problem seems an acpi problem but
without acpi the systems is unusable.

I hope this will help you.


            thx for help

                Ruben


-- 
Ruben Puettmann
ruben@puettmann.net
http://www.puettmann.net

Re: Problems with usb-ohci on 2.4.22-preX

[Roger Larsson]

I am not alone then...

On lördagen den 12 juli 2003 16.14, Ruben Puettmann wrote:
>         hy,
>
> i try to install linux on my new motherboard EPOX 8RDA3+
> with nvidia nforce2 chipset.
>
> If I try to attached some usb devices ( usb memory stick ) I got this
> errors ( 2.4.22-pre5 pre2..):

I used a Creative MuVo 64.

>
>
> PCI: Setting latency timer of device 00:02.2 to 64
> ehci_hcd 00:02.2: nVidia Corporation nForce2 USB Controller
> ehci_hcd 00:02.2: irq 20, pci mem f88eb000
> usb.c: new USB bus registered, assigned bus number 1
> PCI: 00:02.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
> PCI: 00:02.2 PCI cache line size corrected to 64.
> ehci_hcd 00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4

Is ehci compatible with ohci? Or does it get rejected later?

> hub.c: USB hub found
> hub.c: 6 ports detected
> PCI: Setting latency timer of device 00:02.0 to 64
> usb-ohci.c: USB OHCI at membase 0xf88f3000, IRQ 20
> usb-ohci.c: usb-00:02.0, nVidia Corporation nForce2 USB Controller
> usb.c: new USB bus registered, assigned bus number 2
> hub.c: USB hub found
> hub.c: 3 ports detected
> PCI: Setting latency timer of device 00:02.1 to 64
> usb-ohci.c: USB OHCI at membase 0xf88f5000, IRQ 22
> usb-ohci.c: usb-00:02.1, nVidia Corporation nForce2 USB Controller (#2)
> usb.c: new USB bus registered, assigned bus number 3
> hub.c: USB hub found
> hub.c: 3 ports detected

> uhci.c: USB Universal Host Controller Interface driver v1.1
> usb-uhci.c: $Revision: 1.275 $ time 15:11:40 Jul 12 2003
> usb-uhci.c: High bandwidth mode enabled
> usb-uhci.c: v1.275:USB Universal Host Controller Interface driver

The mix of drivers are confusing... Is usb-uhci rejected?
Check with lsmod.

> hub.c: new USB device 00:02.1-3, assigned address 2
> usb_control/bulk_msg: timeout
> usb-ohci.c: unlink URB timeout
> usb.c: USB device not accepting new address=2 (error=-110)

This is exactly what I get (2.4.20). But I use quite different hardware.
STPC Atlas (100MHz, for an embedded project)

>
> This happend's with usb-ohci and usb-ehci loaded or only with usb-ohci.
>

Our suspects:
* Power consumption of device related to how much we can drive.
  (but this should not be a problem in your case)
* BIOS/Linux memory IO mapping - cachable... e.t.c.
* Something in the driver,
  - a timing mismatch with the HW that was used to develop the driver?
  - a corrected hardware bug?
  (we got the driver to work with the USB memory unit on another PC with
   ohci - so we had almost accepted that the driver was correct... but now...)

/RogerL

-- 
Roger Larsson
Skellefteå
Sweden

Re: [linux-usb-devel] Re: Problems with usb-ohci on 2.4.22-preX

[David Brownell]

Roger Larsson wrote:
> I am not alone then...
> 
>>hub.c: new USB device 00:02.1-3, assigned address 2
>>usb_control/bulk_msg: timeout
>>usb-ohci.c: unlink URB timeout
>>usb.c: USB device not accepting new address=2 (error=-110)
> 
> 
> This is exactly what I get (2.4.20). But I use quite different hardware.
> STPC Atlas (100MHz, for an embedded project)

Q:  Why doesn't USB work at all? I get "device not accepting address".

   http://www.linux-usb.org/FAQ.html#ts6

Basically, if your PCI IRQ routing is broken, USB won't work.  Likely
that FAQ entry could stand updating (ACPI vs APCI etc).  There are
still significant issues there in 2.6 kernels; and I've hardly ever
seen ACPI do anything except break USB.

- Dave

Re: [linux-usb-devel] Re: Problems with usb-ohci on 2.4.22-preX

[Greg KH]

On Tue, Jul 15, 2003 at 11:34:03AM -0700, David Brownell wrote:
> 
> I've hardly ever seen ACPI do anything except break USB.

Heh, my laptop _requires_ ACPI to get USB to work properly :)

greg k-h

Re: [linux-usb-devel] Re: Problems with usb-ohci on 2.4.22-preX

[David Brownell]

Greg KH wrote:
> On Tue, Jul 15, 2003 at 11:34:03AM -0700, David Brownell wrote:
> 
>>I've hardly ever seen ACPI do anything except break USB.
> 
> 
> Heh, my laptop _requires_ ACPI to get USB to work properly :)

The fact that I've seen one laptop work with ACPI is the
entire reason I said "hardly ever" ... ;)   I've seen some
hardware work with "pci=noacpi", which still counts as
broken in my book.

Desktop hardware has uniformly broken if I enable ACPI in
the build.  The usual rule of thumb seems to be that when
ACPI assigns the USB IRQs to values over 16, they won't
work for me ... example, 2.5.75 on an SN41G2 assigned
all four USB controllers (including a net2280!) that way.

That was a curious symptom though:  /proc/interrupts
showed endless streams of IRQs going to the devices,
rather than the somewhat-more-typical "no IRQs".  I had
not seen that before.  (It was almost a 2.6-test1 kernel.)

In theory, this is just a bug that will get fixed, but
in practice, the behavior has never yet changed.

- dave