2008-12-30 20:15:26

by Steffen Pankratz

[permalink] [raw]
Subject: hci_usb problem after rmmod/modprobe

Hi,

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

lsusb -v output is attached
lspci -vv output is attached


Thanks
-Steffen

--
Hermes powered by LFS SVN-20070420 (Linux 2.6.28)

Best regards, Steffen Pankratz.


Attachments:
(No filename) (681.00 B)
lspci (18.60 kB)
lsusb (24.80 kB)
signature.asc (197.00 B)
Download all attachments

2008-12-31 09:43:54

by Steffen Pankratz

[permalink] [raw]
Subject: Re: hci_usb problem after rmmod/modprobe

On Tue, 30 Dec 2008 21:22:20 +0100
Marcel Holtmann <[email protected]> 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.
>
> Regards
>
> Marcel
>

Hi Marcel,

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)

Regards
-Steffen

--
Hermes powered by LFS SVN-20070420 (Linux 2.6.28)

Best regards, Steffen Pankratz.


Attachments:
signature.asc (197.00 B)

2008-12-30 20:22:20

by Marcel Holtmann

[permalink] [raw]
Subject: Re: hci_usb problem after rmmod/modprobe

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.

Regards

Marcel



2009-01-09 11:50:18

by Steffen Pankratz

[permalink] [raw]
Subject: Re: hci_usb problem after rmmod/modprobe

On Thu, 01 Jan 2009 09:59:01 +0100
Marcel Holtmann <[email protected]> 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,

this topic is gotten quiet,
is there anything else I can do to help?


Regards
-Steffen

--
Hermes powered by LFS SVN-20070420 (Linux 2.6.28)

Best regards, Steffen Pankratz.


Attachments:
(No filename) (1.36 kB)
log (2.22 kB)
signature.asc (197.00 B)
Download all attachments

2009-01-01 18:40:50

by Dave Schile

[permalink] [raw]
Subject: How do I get headset button events without .btscorc?

Hello.
I figured this one out all on my own! Here is a script in python that
uses dbus to get the bluetooth headset button press. I think it might be
helpful to add this to the wiki.

<pre>

def handler(sender=None):
os.system ('/usr/bin/twinkle --cmd answerbye') # <- that's the part
specific to twinkle
import dbus, os, gobject
from dbus.mainloop.glib import DBusGMainLoop
DBusGMainLoop(set_as_default=True)
bus = dbus.SystemBus()
bus.add_signal_receiver(handler, signal_name="AnswerRequested")
loop = gobject.MainLoop()
loop.run()

</pre>

Dave



2009-01-01 16:26:28

by Steffen Pankratz

[permalink] [raw]
Subject: Re: hci_usb problem after rmmod/modprobe

On Thu, 01 Jan 2009 09:59:01 +0100
Marcel Holtmann <[email protected]> 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.


Attachments:
(No filename) (1.67 kB)
log (2.22 kB)
signature.asc (197.00 B)
Download all attachments

2009-01-01 08:59:01

by Marcel Holtmann

[permalink] [raw]
Subject: Re: hci_usb problem after rmmod/modprobe

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.

Regards

Marcel