linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sat, 12 Sep 2020 10:04:39 +0000	[thread overview]
Message-ID: <bug-204765-62941-N8mQiCKdd3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204765-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204765

Maarten Fonville (maarten.fonville@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |maarten.fonville@gmail.com

--- Comment #10 from Maarten Fonville (maarten.fonville@gmail.com) ---
I am suddenly seeing the same error after suspend/hibernation on my laptop with
my Microsoft Surface bluetooth mouse, using latest Ubuntu kernel
5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux:


[82250.719088] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[82250.720091] Bluetooth: hci0: Device revision is 16
[82250.720092] Bluetooth: hci0: Secure boot is enabled
[82250.720093] Bluetooth: hci0: OTP lock is enabled
[82250.720094] Bluetooth: hci0: API lock is enabled
[82250.720094] Bluetooth: hci0: Debug lock is disabled
[82250.720095] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[82250.720099] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[82250.722178] done.
[82250.757394] PM: suspend exit
[82250.980766] Generic FE-GE Realtek PHY r8169-200:00: attached PHY driver
[Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
[82251.091652] r8169 0000:02:00.0 enp2s0: Link is Down
[82252.225425] Bluetooth: hci0: Waiting for firmware download to complete
[82252.226105] Bluetooth: hci0: Firmware loaded in 1472555 usecs
[82252.226211] Bluetooth: hci0: Waiting for device to boot
[82252.238154] Bluetooth: hci0: Device booted in 11754 usecs
[82252.238165] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
[82252.241173] Bluetooth: hci0: Applying Intel DDC parameters completed
[82326.333382] Lockdown: systemd-logind: hibernation is restricted; see man
kernel_lockdown.7
[82358.148284] debugfs: File 'le_min_key_size' in directory 'hci0' already
present!
[82358.148303] debugfs: File 'le_max_key_size' in directory 'hci0' already
present!

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2020-09-12 10:04 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
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 [this message]
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-N8mQiCKdd3@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 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).