Skip to contentSkip to conversation

[2.6.8 ->] Problems, hci_usb dosn't work.

Bluez-devel Ian Kumlien 2 participants 11 messages Sep 21, 2004 – Sep 22, 2004 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

Hi,

Since some kernel version i can't exactly remember which, i have been unable to use usb, i have tested with with 2.6.8 -> 2.6.9-rc2-bk7 and i also applied your patches for 2.6.8.

I have 2 usb dongles, one old that did work once, and one new that seems to be working like the older but it doesn't work with linux.

Both are based on the CSR chipset, here is the new ones entry from the hw support list:
MSI MS-6967 CSR 1.1 hci_usb working Dave Beckett

Som logs from insertions:
usb 1-3.4: new full speed USB device using address 12 ehci_hcd 0000:00:02.2: qh f7e54780 (#0) state 1
hci_usb_intr_rx_submit: hci0 intr rx submit failed urb d968cd74 err -28

usb 1-4.4: new full speed USB device using address 13 ehci_hcd 0000:00:02.2: qh f7e54900 (#0) state 1
hci_usb_intr_rx_submit: hci1 intr rx submit failed urb d315eef4 err -28

both of these are connected to usb 2.0 hubs (this machine does usb 2.0)

Output from hciconfig:
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0

hci1: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0

From a strace:

socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 3
ioctl(3, 0x800448d3, 0x804eae0)         = 0
ioctl(3, 0x400448c9, 0)                 = -1 EIO (Input/output error)

fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7fe8000
write(1, "Can\'t init device hci0. Input/ou"..., 46Can't init device hci0. Input/output error(5)
) = 46

Basically, it just stopped working and i dunno why, any clues? at all?

Signature · 1 line
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
maintainer
#1 lore raw

Hi Ian,

Quoted 16 lines

Since some kernel version i can't exactly remember which, i have been unable to use usb, i have tested with with 2.6.8 -> 2.6.9-rc2-bk7 and i also applied your patches for 2.6.8.

I have 2 usb dongles, one old that did work once, and one new that seems to be working like the older but it doesn't work with linux.

Both are based on the CSR chipset, here is the new ones entry from the hw support list:
MSI MS-6967 CSR 1.1 hci_usb working Dave Beckett

Som logs from insertions:
usb 1-3.4: new full speed USB device using address 12 ehci_hcd 0000:00:02.2: qh f7e54780 (#0) state 1
hci_usb_intr_rx_submit: hci0 intr rx submit failed urb d968cd74 err -28

Quoted 5 lines

usb 1-4.4: new full speed USB device using address 13 ehci_hcd 0000:00:02.2: qh f7e54900 (#0) state 1
hci_usb_intr_rx_submit: hci1 intr rx submit failed urb d315eef4 err -28

both of these are connected to usb 2.0 hubs (this machine does usb 2.0)

this looks like an USB problem to me. Try to connect it to USB 1.1 ports and see if this works.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#2 lore raw
Quoted 18 lines · Marcel Holtmann

Hi Ian,

Quoted 16 lines

Since some kernel version i can't exactly remember which, i have been unable to use usb, i have tested with with 2.6.8 -> 2.6.9-rc2-bk7 and i also applied your patches for 2.6.8.

I have 2 usb dongles, one old that did work once, and one new that seems to be working like the older but it doesn't work with linux.

Both are based on the CSR chipset, here is the new ones entry from the hw support list:
MSI MS-6967 CSR 1.1 hci_usb working Dave Beckett

Som logs from insertions:
usb 1-3.4: new full speed USB device using address 12 ehci_hcd 0000:00:02.2: qh f7e54780 (#0) state 1
hci_usb_intr_rx_submit: hci0 intr rx submit failed urb d968cd74 err -28

Quoted 8 lines
Quoted 5 lines

usb 1-4.4: new full speed USB device using address 13 ehci_hcd 0000:00:02.2: qh f7e54900 (#0) state 1
hci_usb_intr_rx_submit: hci1 intr rx submit failed urb d315eef4 err -28

both of these are connected to usb 2.0 hubs (this machine does usb 2.0)

this looks like an USB problem to me. Try to connect it to USB 1.1 ports and see if this works.

The problem is, this computer doesn't have a usb 1.1 port. But it should basically fallback, and afair it worked with a cable direct to the computer, i haven't tested that since... because i need the hubs.

But if it indeed is a usb 1.1 vs 2.0 problem then it has to be something broken in the kernel... Anyone else using this with usb 2.0?

Signature · 1 line
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
maintainer
#3 lore raw

Hi Ian,

Quoted 7 lines

The problem is, this computer doesn't have a usb 1.1 port. But it should basically fallback, and afair it worked with a cable direct to the computer, i haven't tested that since... because i need the hubs.

But if it indeed is a usb 1.1 vs 2.0 problem then it has to be something broken in the kernel... Anyone else using this with usb 2.0?

this problem was reported two or three times, but I am unable to reproduce it with my USB 2.0 host controllers.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#4 lore raw
Quoted 7 lines · Marcel Holtmann

Hi Ian,

Quoted 5 lines

The problem is, this computer doesn't have a usb 1.1 port. But it should basically fallback, and afair it worked with a cable direct to the computer, i haven't tested that since... because i need the hubs.

Quoted 5 lines
Quoted 2 lines

But if it indeed is a usb 1.1 vs 2.0 problem then it has to be something broken in the kernel... Anyone else using this with usb 2.0?

this problem was reported two or three times, but I am unable to reproduce it with my USB 2.0 host controllers.

ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2) ohci_hcd 0000:00:02.1: irq 185, pci mem f8818000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3

What controller do you use? and what usb1.1 driver?

Quoted 3 lines

Regards

Marcel

Signature · 1 line
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
maintainer
#5 lore raw

Hi Ian,

Quoted 6 lines
Quoted 2 lines

this problem was reported two or three times, but I am unable to reproduce it with my USB 2.0 host controllers.

ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2) ohci_hcd 0000:00:02.1: irq 185, pci mem f8818000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3

your IRQ looks very weird. I have never seen an IO-APIC system assigning IRQ 185 to any device. Does any other USB device works in conjunction with this controller?

Quoted 1 line

What controller do you use? and what usb1.1 driver?

I use a NEC controller with an OHCI for USB 1.1 stuff.

0000:02:0c.0 USB Controller: NEC Corporation USB (rev 43) 0000:02:0c.1 USB Controller: NEC Corporation USB (rev 43) 0000:02:0c.2 USB Controller: NEC Corporation USB 2.0 (rev 04)

ACPI: PCI interrupt 0000:02:0c.0[A] -> GSI 20 (level, low) -> IRQ 20 ohci_hcd 0000:02:0c.0: OHCI Host Controller
ohci_hcd 0000:02:0c.0: irq 20, pci mem e1352000
ohci_hcd 0000:02:0c.0: new USB bus registered, assigned bus number 3 hub 3-0:1.0: USB hub found
hub 3-0:1.0: 3 ports detected
ACPI: PCI interrupt 0000:02:0c.1[B] -> GSI 21 (level, low) -> IRQ 21 ohci_hcd 0000:02:0c.1: OHCI Host Controller
ohci_hcd 0000:02:0c.1: irq 21, pci mem e137a000
ohci_hcd 0000:02:0c.1: new USB bus registered, assigned bus number 4 hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:02:0c.2[C] -> GSI 22 (level, low) -> IRQ 22 ehci_hcd 0000:02:0c.2: EHCI Host Controller
ehci_hcd 0000:02:0c.2: irq 22, pci mem e137c000
ehci_hcd 0000:02:0c.2: new USB bus registered, assigned bus number 5 ehci_hcd 0000:02:0c.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10 hub 5-0:1.0: USB hub found
hub 5-0:1.0: 5 ports detected

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#6 lore raw
Quoted 5 lines · Marcel Holtmann

Hi Ian,

Quoted 3 lines
Quoted 2 lines

this problem was reported two or three times, but I am unable to reproduce it with my USB 2.0 host controllers.

Quoted 7 lines
Quoted 3 lines

ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2) ohci_hcd 0000:00:02.1: irq 185, pci mem f8818000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3

your IRQ looks very weird. I have never seen an IO-APIC system assigning IRQ 185 to any device. Does any other USB device works in conjunction with this controller?

2 joysticks, one 6in1 card reader and one muvodrive, it all works. And, it registers the device correctly it just can't read from it.

And yeah i know, it's part of the nvidia workaround:
cat /proc/interrupts
CPU0

  0:   91522201          XT-PIC  timer
  1:      17141    IO-APIC-edge  i8042
  8:          4    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 14:     341508    IO-APIC-edge  ide0
 15:    1917703    IO-APIC-edge  ide1
177:          0   IO-APIC-level  ohci_hcd
185:          0   IO-APIC-level  ohci_hcd
193:     347701   IO-APIC-level  ehci_hcd
201:    4266340   IO-APIC-level  EMU10K1
209:    3869397   IO-APIC-level  eth0
217:   11455874   IO-APIC-level  nvidia
NMI:       8253
LOC:   91523920
ERR:          0
MIS:          0

hurrm ohci_hcd should have data... hurrrm, it might be LKML related after all.. =P
(I might have left the experimental 'ohci' support in ehci on in this kernel.)

Quoted 3 lines
Quoted 1 line

What controller do you use? and what usb1.1 driver?

I use a NEC controller with an OHCI for USB 1.1 stuff.

Heh ok

Signature · 1 line
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
maintainer
#7 lore raw

Hi Ian,

Quoted 10 lines
Quoted 7 lines
Quoted 3 lines

ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2) ohci_hcd 0000:00:02.1: irq 185, pci mem f8818000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3

your IRQ looks very weird. I have never seen an IO-APIC system assigning IRQ 185 to any device. Does any other USB device works in conjunction with this controller?

2 joysticks, one 6in1 card reader and one muvodrive, it all works. And, it registers the device correctly it just can't read from it.

are these devices all USB 2.0 capable? If yes, then they are handled by the ehci_hcd host controller driver.

Quoted 20 lines

And yeah i know, it's part of the nvidia workaround:
cat /proc/interrupts
CPU0

  0:   91522201          XT-PIC  timer
  1:      17141    IO-APIC-edge  i8042
  8:          4    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 14:     341508    IO-APIC-edge  ide0
 15:    1917703    IO-APIC-edge  ide1
177:          0   IO-APIC-level  ohci_hcd
185:          0   IO-APIC-level  ohci_hcd
193:     347701   IO-APIC-level  ehci_hcd
201:    4266340   IO-APIC-level  EMU10K1
209:    3869397   IO-APIC-level  eth0
217:   11455874   IO-APIC-level  nvidia
NMI:       8253
LOC:   91523920
ERR:          0
MIS:          0
Quoted 4 lines

hurrm ohci_hcd should have data... hurrrm, it might be LKML related after all.. =P
(I might have left the experimental 'ohci' support in ehci on in this kernel.)

Check that first and then report it to the Linux USB mailing list. It is more an USB issue then LKML related.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#8 lore raw
Quoted 5 lines · Marcel Holtmann
Quoted 2 lines

2 joysticks, one 6in1 card reader and one muvodrive, it all works. And, it registers the device correctly it just can't read from it.

are these devices all USB 2.0 capable? If yes, then they are handled by the ehci_hcd host controller driver.

All except the monitor that also registers it self via usb, =) (I am really surprised about that actually)

Sam Sung Electronics

Manufacturer: Samsung Electronics
Serial Number: HVAWA04398
Speed: 1.5Mb/s (low)
USB Version:  1.10
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 8
Number of Configurations: 1
Vendor Id: 0419
Product Id: 8002
Revision Number:  2.00

And here is the usb dongle output
hci_usb

Speed: 12Mb/s (full)
USB Version:  1.10
Device Class: e0(unk. ) <== Looks like something missing
Device Subclass: 01
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0db0
Product Id: 1967
Revision Number:  5.25

Should i change some identifier and test some?

Quoted 2 lines

Check that first and then report it to the Linux USB mailing list. It is more an USB issue then LKML related.

yep... Assumed, i just assumed that some small thing might be broken and that you usb ppl would be quicker to spot it =)

Signature · 1 line
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
maintainer
#9 lore raw

Hi Ian,

Quoted 36 lines
Quoted 5 lines
Quoted 2 lines

2 joysticks, one 6in1 card reader and one muvodrive, it all works. And, it registers the device correctly it just can't read from it.

are these devices all USB 2.0 capable? If yes, then they are handled by the ehci_hcd host controller driver.

All except the monitor that also registers it self via usb, =) (I am really surprised about that actually)

Sam Sung Electronics

Manufacturer: Samsung Electronics
Serial Number: HVAWA04398
Speed: 1.5Mb/s (low)
USB Version:  1.10
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 8
Number of Configurations: 1
Vendor Id: 0419
Product Id: 8002
Revision Number:  2.00

And here is the usb dongle output
hci_usb

Speed: 12Mb/s (full)
USB Version:  1.10
Device Class: e0(unk. ) <== Looks like something missing
Device Subclass: 01
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0db0
Product Id: 1967
Revision Number:  5.25
Quoted 1 line

Should i change some identifier and test some?

here is nothing really important missing, because 0xe0 means wireless class or so.

This looks really like an ohci_hcd problem with interrupt URBs.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#10 lore raw
Quoted 1 line · Marcel Holtmann

This looks really like an ohci_hcd problem with interrupt URBs.

The reply i received:
Error -28 is -ENOSPC, which means the USB bandwidth was exhausted. Too many devices were plugged into the same controller. Unplugging some of the other devices ought to help. Or even plugging the BT controller into one of the other ports rather than the external high-speed hub, since it is only a full-speed device.

Alan Stern
---

Then i moved the usb dongle around in the newly discovered 2 usb ports...and suddenly it worked (only in one of the two usb ports though) and now i'm not touching it! =)

Thanks for all the help =)

Signature · 1 line
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net