From: Marcel Holtmann <marcel@holtmann.org>
To: Steffen Pankratz <kratz00@gmx.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: hci_usb problem after rmmod/modprobe
Date: Thu, 01 Jan 2009 09:59:01 +0100 [thread overview]
Message-ID: <1230800341.4530.4.camel@californication> (raw)
In-Reply-To: <20081231104354.1bf8f381@hermes>
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
next prev parent reply other threads:[~2009-01-01 8:59 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 [this message]
2009-01-01 16:26 ` Steffen Pankratz
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=1230800341.4530.4.camel@californication \
--to=marcel@holtmann.org \
--cc=kratz00@gmx.de \
--cc=linux-bluetooth@vger.kernel.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.