From: Marcel Holtmann <marcel@holtmann.org>
To: wim delvaux <wim.delvaux@adaptiveplanet.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems
Date: Mon, 12 Apr 2004 15:33:48 +0200 [thread overview]
Message-ID: <1081776828.5398.109.camel@pegasus> (raw)
In-Reply-To: <200404121317.52361.wim.delvaux@adaptiveplanet.com>
Hi Wim,
> I have tried with that version. (Applied the 2.6.5-mh3 patch)
> However then I get these 'bad atomic' errors
where do you get them? In the hci_usb driver or in the USB subsystem?
> I just retried with the 2.6.3 kernel and saw
>
> 'device not accepting address' messages error -110
> And then
Know problem. Some broken device which needs a longer timeout value.
> drivers/usb/host/uhci-hcd.c: uhci_result_control() failed with status 440000
> [ceb01240] link (0eb011e2) element (0ecb9040)
> 0: [cecb9040] link (0ecb9080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0
> EndPt=0 Dev=0, PID=2d(SETUP) (buf=0bd05e40)
> 1: [cecb9080] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0
> Dev=0, PID=69(IN) (buf=00000000)
>
> after a few inserts it gives
>
> usb 1-1: new full speed USB device using address 10
> usb 1-1: new device strings: Mfr=0, Product=0, SerialNumber=0
> drivers/usb/core/usb.c: usb_hotplug
> usb 1-1: registering 1-1:1.0 (config #1, interface 0)
> drivers/usb/core/usb.c: usb_hotplug
> usb 1-1: registering 1-1:1.1 (config #1, interface 1)
> drivers/usb/core/usb.c: usb_hotplug
> usb 1-1: registering 1-1:1.2 (config #1, interface 2)
> drivers/usb/core/usb.c: usb_hotplug
> Bluetooth: HCI USB driver ver 2.4
> hci_usb 1-1:1.0: usb_probe_interface
> hci_usb 1-1:1.0: usb_probe_interface - got id
> hci_usb 1-1:1.1: usb_probe_interface
> hci_usb 1-1:1.2: usb_probe_interface
> hci_usb 1-1:1.2: usb_probe_interface - got id
> drivers/usb/core/usb.c: registered new driver hci_usb
> hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb c4d61214 err -22
> hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb c4d61214 err -22
Bug in the hci_usb driver. Disable CONFIG_BT_HCIUSB_SCO.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-12 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 1:49 [Bluez-devel] 2.6.5 problems turned to 2.6.3 but also problems wim delvaux
2004-04-12 10:55 ` Marcel Holtmann
2004-04-12 11:17 ` wim delvaux
2004-04-12 13:33 ` Marcel Holtmann [this message]
2004-04-12 14:21 ` wim delvaux
2004-04-12 14:55 ` Marcel Holtmann
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=1081776828.5398.109.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=wim.delvaux@adaptiveplanet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.