linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Haun <haunma@keteu.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Loic Poulain <loic.poulain@intel.com>
Subject: Re: Intel 7260 spontaneous USB disconnect/reconnect every 23h18m07s
Date: Tue, 25 Aug 2015 13:49:11 -0700	[thread overview]
Message-ID: <20150825204911.GA3479@hau.nz> (raw)
In-Reply-To: <20150825191523.GA3220@hau.nz>

Mark Haun [haunma@keteu.org] wrote:
> Took me a while to figure out you have to bring down the hci0 interface and
> stop bluetoothd before running bluemoon.  Otherwise I get "Failed to open
> HCI user channel."  So now when I run bluemoon -T it just sits there forever
> after the welcome message.  Is this expected behavior?  Should I then
> restart bluetoothd in another console and leave the whole thing for a couple
> of days to catch the USB disconnect?

Ok, I think I am seeing a bug very similar to this one reported by Loic
Poulain:

http://marc.info/?l=linux-bluetooth&m=143220351521634&w=2
("bluetooth-next HCI user channel issue")

I have the same symptom of bluemoon hanging, and I figured out that I can
recover the system without rebooting by forcing hci0 down again.  "hciconfig
hci0 down" takes about ten seconds to return, and then I have a 0xfc3f
timeout in dmesg:

[ 5563.562554] Bluetooth: hci0 command 0xfc3f tx timeout
[ 5571.557618] Bluetooth: hci0: turning off Intel device LED failed (-110)

This is the same error Loic was getting, I assume because the commit in
question has now made it into my kernel (4.2.0-rc4).

Mark

  reply	other threads:[~2015-08-25 20:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  5:20 Intel 7260 spontaneous USB disconnect/reconnect every 23h18m07s Mark A. Haun
2015-08-20  7:57 ` Ge, Ethan
2015-08-25 16:52   ` Mark Haun
2015-08-25 17:06     ` Marcel Holtmann
2015-08-25 17:16       ` Mark Haun
2015-08-25 17:23         ` Marcel Holtmann
2015-08-25 18:11           ` Mark Haun
2015-08-25 19:15           ` Mark Haun
2015-08-25 20:49             ` Mark Haun [this message]
2015-08-25 21:40               ` Marcel Holtmann
2015-08-25 21:36             ` Marcel Holtmann
2015-08-25 23:46               ` Mark Haun
2015-08-26  5:56     ` Ge, Ethan

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=20150825204911.GA3479@hau.nz \
    --to=haunma@keteu.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=loic.poulain@intel.com \
    --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 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).