From: Steffen Pankratz <kratz00@gmx.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: hci_usb problem after rmmod/modprobe
Date: Thu, 1 Jan 2009 17:26:28 +0100 [thread overview]
Message-ID: <20090101172628.5aea09d7@hermes> (raw)
In-Reply-To: <1230800341.4530.4.camel@californication>
[-- Attachment #1.1: Type: text/plain, Size: 1777 bytes --]
On Thu, 01 Jan 2009 09:59:01 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Steffen,
>
> > > > everything is fine until I unload and reload hci_usb:
> > > >
> > > > hciconfig hci0 up
> > > > Can't init device hci0: Input/output error (5)
> > > >
> > > > from dmesg:
> > > > hci_usb_intr_rx_submit: hci0 intr rx submit failed urb f406cf54 err -2
> > > >
> > > > I tried 'modprobe hci_usb reset=1' which did not solve the problem.
> > > >
> > > > To get it working again I have to do:
> > > >
> > > > rmmod hci_usb bluetooth uhci_hcd
> > > > modprobe uhci_hcd
> > > > modprobe hci_usb
> > > >
> > > > Not sure what information could be helpful:
> > > >
> > > > Linux hermes 2.6.28 #2 PREEMPT Tue Dec 30 16:30:47 CET 2008 i686 i686
> > > > i386 GNU/Linux
> > >
> > > if you are using 2.6.28 kernel, then just use the btusb driver instead
> > > of hci_usb. The hci_usb will be removed with 2.6.29 anyway.
> >
> > thanks for your suggestion.
> > I am now using the btusb driver but the problem remains,
> > except the kernel message has changed:
> >
> > btusb_submit_intr_urb: hci0 urb f61e37c0 submission failed (2)
>
> run "hcidump -X -V" and see what is going on and what exactly fails.
Hi Marcel,
the only output hcidump gives is:
./hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
hciconfig hci0 up
Can't init device hci0: Input/output error (5)
dmesg:
btusb_submit_intr_urb: hci0 urb f6479b40 submission failed (2)
The attached log shows the output of 'hciconfig hci0 up'
after I reloaded uhci_hcd and btusb.
Happy New Year
-Steffen
--
Hermes powered by LFS SVN-20070420 (Linux 2.6.28)
Best regards, Steffen Pankratz.
[-- Attachment #1.2: log --]
[-- Type: application/octet-stream, Size: 2275 bytes --]
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Reset (0x03|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 4
Reset (0x03|0x0003) ncmd 1
status 0x00
< HCI Command: Read Local Supported Features (0x04|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 12
Read Local Supported Features (0x04|0x0003) ncmd 1
status 0x00
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
Read Local Version Information (0x04|0x0001) ncmd 1
status 0x00
HCI Version: 1.2 (0x2) HCI Revision: 0x2
LMP Version: 1.2 (0x2) LMP Subversion: 0x6965
Manufacturer: Broadcom Corporation (15)
< HCI Command: Read Buffer Size (0x04|0x0005) plen 0
> HCI Event: Command Complete (0x0e) plen 11
Read Buffer Size (0x04|0x0005) ncmd 1
status 0x00
ACL MTU 377:10 SCO MTU 16:0
< HCI Command: Read BD ADDR (0x04|0x0009) plen 0
> HCI Event: Command Complete (0x0e) plen 10
Read BD ADDR (0x04|0x0009) ncmd 1
status 0x00 bdaddr 00:10:C6:81:A4:7C
< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
Read Class of Device (0x03|0x0023) ncmd 1
status 0x00 class 0x000000
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
Read Local Name (0x03|0x0014) ncmd 1
status 0x00 name 'Broadcom Bluetooth Module'
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
Read Voice Setting (0x03|0x0025) ncmd 1
status 0x00 voice setting 0x0060
< HCI Command: Set Event Filter (0x03|0x0005) plen 1
type 0 condition 0
Clear all filters
> HCI Event: Command Complete (0x0e) plen 4
Set Event Filter (0x03|0x0005) ncmd 1
status 0x00
< HCI Command: Write Page Timeout (0x03|0x0018) plen 2
timeout 32768
> HCI Event: Command Complete (0x0e) plen 4
Write Page Timeout (0x03|0x0018) ncmd 1
status 0x00
< HCI Command: Write Connection Accept Timeout (0x03|0x0016) plen 2
timeout 32000
> HCI Event: Command Complete (0x0e) plen 4
Write Connection Accept Timeout (0x03|0x0016) ncmd 1
status 0x00
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-01 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 20:15 hci_usb problem after rmmod/modprobe Steffen Pankratz
2008-12-30 20:22 ` Marcel Holtmann
2008-12-31 9:43 ` Steffen Pankratz
2009-01-01 8:59 ` Marcel Holtmann
2009-01-01 16:26 ` Steffen Pankratz [this message]
2009-01-01 18:40 ` How do I get headset button events without .btscorc? Dave Schile
2009-01-09 11:50 ` hci_usb problem after rmmod/modprobe Steffen Pankratz
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=20090101172628.5aea09d7@hermes \
--to=kratz00@gmx.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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.