From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Hci Reset Problem - Caused by USB Hub
Date: Mon, 31 Jul 2006 20:19:40 +0200 [thread overview]
Message-ID: <1154369980.4982.14.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20060731182135.488b017c@localhost.localdomain>
Hi Andreas,
> further tests proofed that the problem described here are caused by
> the USB-hub used. It seems to be unable to handle the load and just
> breaks down. The same operations are working on other (higher quality) hubs.
>
> Watch out for lines like
>
> usb 1-1: USB disconnect, address 29
>
> in syslog and/or dmesg to check if your problem is similar. Make sure
> not to mess with real physical disconnects which produce the same log
> output.
does this also happens if you load the hci_usb driver with "isoc=0" to
disable all ISOC transfers.
> I guess the HCI_RESET is issued by bluez after the device comes back on.
This could be the case.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-07-31 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 16:06 [Bluez-users] Hci Reset Problem Lan Zhang
2006-07-28 1:56 ` Marcel Holtmann
2006-07-28 10:37 ` Andreas Gaufer
2006-07-28 11:39 ` Andreas Gaufer
2006-07-31 16:21 ` [Bluez-users] Hci Reset Problem - Caused by USB Hub Andreas Gaufer
2006-07-31 18:19 ` Marcel Holtmann [this message]
2006-08-01 13:39 ` Andreas Gaufer
2006-08-02 1:21 ` 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=1154369980.4982.14.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).