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, 02 Jan 2021 13:43:27 +0000	[thread overview]
Message-ID: <bug-204765-62941-lvxcvjHdJj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204765-62941@https.bugzilla.kernel.org/>

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

Sergey Ivanov (icegood1980@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |icegood1980@gmail.com

--- Comment #13 from Sergey Ivanov (icegood1980@gmail.com) ---
Hi all. I don't see why only 5.11 fixes this. As for me I see such an issue
after BT was off and there was the sleep of laptop. 

debugfs: File 'force_bredr_smp' in directory 'hci0' already present!

uname -a
Linux ice-ubuntu 5.8.0-34-generic #37-Ubuntu SMP Thu Dec 10 18:01:14 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux

-- 
You may reply to this email to add a comment.

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

      parent reply	other threads:[~2021-01-02 13:44 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
2020-09-30 23:59 ` bugzilla-daemon
2020-12-02 10:54 ` bugzilla-daemon
2021-01-02 13:43 ` bugzilla-daemon [this message]

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-lvxcvjHdJj@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).