From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 201731] New: Bluetooth hardware not initializing with kernel 4.18.18 and 4.18.19
Date: Mon, 19 Nov 2018 12:16:43 +0000 [thread overview]
Message-ID: <bug-201731-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201731
Bug ID: 201731
Summary: Bluetooth hardware not initializing with kernel
4.18.18 and 4.18.19
Product: Drivers
Version: 2.5
Kernel Version: 4.18.19
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: admiral0@tuxfamily.org
Regression: No
Created attachment 279525
--> https://bugzilla.kernel.org/attachment.cgi?id=279525&action=edit
Bluetooth unusable after minor update [4.18]
Logs:
It started after I upgraded from 4.18.3 to 4.18.18. I cannot post full dmesg
unfortunately, but will try to bisect this weekend.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-11-19 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 12:16 bugzilla-daemon [this message]
2018-11-19 13:35 ` [Bug 201731] Bluetooth hardware not initializing with kernel 4.18.18 and 4.18.19 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-201731-62941@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).