From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@kernel.org
Subject: [Bug 64671] hci0 command 0x1009 tx timeout, bluez can't find adapter
Date: Thu, 02 Mar 2017 00:55:12 +0000 [thread overview]
Message-ID: <bug-64671-62941-M0WWdiXX00@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-64671-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=64671
Maxim Moseychuk (franchesko.salias.hudro.pedros@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |franchesko.salias.hudro.ped
| |ros@gmail.com
--- Comment #8 from Maxim Moseychuk (franchesko.salias.hudro.pedros@gmail.com) ---
(In reply to Ongun Kanat from comment #7)
> I've got same behavior on 4.9.8 kernel on PC with Atheros AR3012 card.
(In reply to MOHAMMAD RASIM from comment #6)
> I have the same issue and the same dmesg error.
>
> My adapter is:
> Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727]
> (rev 01)
> I had the problem on archlinux but now I'm running linux mint and have the
> same problem.
>
> Current kernel:
> Linux mohammad-mint 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC
> 2016 x86_64 x86_64 x86_64 GNU/Linux
Can someone test my patch? This bug not always reproduce, and i need help for
test 1-2 week.
I can send raw patch, branch on github or PKGBUILD for archlinux.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-03-02 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64671-62941@https.bugzilla.kernel.org/>
2017-01-29 21:50 ` [Bug 64671] hci0 command 0x1009 tx timeout, bluez can't find adapter bugzilla-daemon
2017-01-30 7:14 ` bugzilla-daemon
2017-02-13 0:44 ` bugzilla-daemon
2017-03-02 0:55 ` bugzilla-daemon [this message]
2017-03-29 22:58 ` bugzilla-daemon
2017-03-30 5:29 ` bugzilla-daemon
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=bug-64671-62941-M0WWdiXX00@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@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 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).