From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 204765] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
Date: Wed, 22 Jan 2020 05:31:07 +0000 [thread overview]
Message-ID: <bug-204765-62941-57pwpSMIZh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204765-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204765
Alfonso Chacón (alfonso.chacon@protonmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alfonso.chacon@protonmail.c
| |om
--- Comment #3 from Alfonso Chacón (alfonso.chacon@protonmail.com) ---
I have the same issue
Device was discovered and connected fine the first time, then it was
disconnected immediately.
Every time I try to connect it again, it disconnects.
s@OrangeDemon:~$ sudo hciconfig hci0 -a
hci0: Type: Primary Bus: USB
BD Address: DC:FB:48:28:FA:95 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN
RX bytes:76148 acl:16 sco:0 events:2184 errors:0
TX bytes:13222 acl:14 sco:0 commands:589 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'OrangeDemon'
Class: 0x100104
Service Classes: Object Transfer
Device Class: Computer, Desktop workstation
HCI Version: 5.0 (0x9) Revision: 0x100
LMP Version: 5.0 (0x9) Subversion: 0x100
Manufacturer: Intel Corp. (2)
dmesg:
[ 4.172065] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.172066] Bluetooth: BNEP filters: protocol multicast
[ 4.172068] Bluetooth: BNEP socket layer initialized
..
[ 13.392448] Bluetooth: RFCOMM TTY layer initialized
[ 13.392452] Bluetooth: RFCOMM socket layer initialized
[ 13.392456] Bluetooth: RFCOMM ver 1.11
[ 246.531147] debugfs: File 'le_min_key_size' in directory 'hci0' already
present!
[ 246.531153] debugfs: File 'le_max_key_size' in directory 'hci0' already
present!
[ 275.658457] debugfs: File 'le_min_key_size' in directory 'hci0' already
present!
[ 275.658463] debugfs: File 'le_max_key_size' in directory 'hci0' already
present!
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-01-22 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204765-62941@https.bugzilla.kernel.org/>
2019-11-02 9:54 ` [Bug 204765] debugfs: File 'le_min_key_size' in directory 'hci0' already present! bugzilla-daemon
2020-01-22 5:31 ` bugzilla-daemon [this message]
2020-04-11 2:06 ` bugzilla-daemon
2020-04-11 2:06 ` bugzilla-daemon
2020-04-11 10:26 ` bugzilla-daemon
2020-09-12 10:04 ` bugzilla-daemon
2020-09-30 23:59 ` bugzilla-daemon
2020-12-02 10:54 ` bugzilla-daemon
2021-01-02 13:43 ` 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-204765-62941-57pwpSMIZh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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.