2009/3/10 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > On Tue, 10 Mar 2009, Natale Vinto wrote: > >> 2009/3/10 Greg KH <greg@xxxxxxxxx>: >> > On Tue, Mar 10, 2009 at 04:39:52PM +0100, Natale Vinto wrote: >> >> Hi, >> >> I would have 4 bluetooth usb key working with a 4-port usb hub on some linux >> >> box with kernel 2.6 and debian. My problem is that only 2 of those bluetooth >> >> key really works and for the other ones I got error like this ( dmesg ): >> >> >> >> [ 189.879423] btusb_submit_intr_urb: hci2 urb f32da200 submission failed >> >> (28) >> > >> > Are there any other messages in the kernel log when you do this? Are >> > you sure these devices really even work? >> > >> > thanks, >> > >> > greg k-h >> > >> >> Hi, >> this is the full log: >> >> [10712.483361] hub 4-3:1.0: USB hub found >> [10712.483991] hub 4-3:1.0: 4 ports detected >> [10712.756345] usb 4-3.1: new full speed USB device using ehci_hcd and >> address 17 >> [10713.100681] usb 4-3.1: configuration #1 chosen from 1 choice >> [10713.184455] usb 4-3.2: new full speed USB device using ehci_hcd and >> address 18 >> [10713.315259] usb 4-3.2: configuration #1 chosen from 1 choice >> [10713.396579] usb 4-3.3: new full speed USB device using ehci_hcd and >> address 19 >> [10713.520897] usb 4-3.3: configuration #1 chosen from 1 choice >> [10713.559994] btusb_submit_intr_urb: hci2 urb e38c6b00 submission failed (28) >> [10713.608332] usb 4-3.4: new full speed USB device using ehci_hcd and >> address 20 >> [10713.733041] usb 4-3.4: configuration #1 chosen from 1 choice >> [10713.739768] btusb_submit_intr_urb: hci3 urb f165f680 submission failed (28) > > 28 is ENOSPC. It means that the driver can't allocate enough bandwidth > on your USB bus to carry the messages needed by those devices. > >> in this case I was trying the Trust usb hub with 4 sitecom bluetooth dongle >> >> Bus 004 Device 020: ID 0a12:0001 Cambridge Silicon Radio, Ltd >> Bluetooth Dongle (HCI mode) >> Bus 004 Device 019: ID 0a12:0001 Cambridge Silicon Radio, Ltd >> Bluetooth Dongle (HCI mode) >> Bus 004 Device 018: ID 0a12:0001 Cambridge Silicon Radio, Ltd >> Bluetooth Dongle (HCI mode) >> Bus 004 Device 017: ID 0a12:0001 Cambridge Silicon Radio, Ltd >> Bluetooth Dongle (HCI mode) >> >> and this is from hciconfig: >> >> hci0: Type: USB >> BD Address: 00:09:DD:50:69:7C ACL MTU: 310:10 SCO MTU: 64:8 >> UP RUNNING PSCAN >> RX bytes:880 acl:0 sco:0 events:48 errors:0 >> TX bytes:452 acl:0 sco:0 commands:47 errors:0 >> >> hci1: Type: USB >> BD Address: 00:09:DD:50:2D:F8 ACL MTU: 310:10 SCO MTU: 64:8 >> UP RUNNING PSCAN >> RX bytes:790 acl:0 sco:0 events:36 errors:0 >> TX bytes:398 acl:0 sco:0 commands:35 errors:0 >> >> hci2: 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 >> >> hci3: 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 >> >> >> the last ones are shown but are "DOWN" and I don't know why > > In this case you have four full-speed devices connected to a high-speed > controller. Linux isn't very good at handling that combination. > > It might possibly work better if you do > > echo 3 >/sys/class/usb_host/usb_host4/companion > > before plugging in the device. (Change the "3" and the "4" > appropriately if you plug the device into a different USB port.) > > Alan Stern > > Hi, I could see that on a ubuntu with its generic kernel 2.6.28-8 any hub works properly, so I think maybe I should fix something in the kernel but what? Is strange because the problem there is with the last 2.6.28.7 from kernel.org, and not in the ubuntu jaunty one -- Natale Vinto http://www.gotext.org -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
