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 213829] Intel AX210 Bluetooth controller doesn't start from warm boot
Date: Thu, 06 Jan 2022 12:58:16 +0000	[thread overview]
Message-ID: <bug-213829-62941-D4VdCZB5hO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213829-62941@https.bugzilla.kernel.org/>

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

--- Comment #52 from Apostolos B. (barz621@gmail.com) ---
> What kind of errors?

Some like that:

Ιαν 05 18:20:53 mainland bluetoothd[25908]: Loading LTKs timed out for hci0
Ιαν 05 18:20:53 mainland kernel: Bluetooth: hci0: command 0x0c52 tx timeout
Ιαν 05 18:20:55 mainland kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Ιαν 05 18:20:57 mainland kernel: Bluetooth: hci0: command 0x0c1a tx timeout
Ιαν 05 18:20:59 mainland kernel: Bluetooth: hci0: command 0x0405 tx timeout
Ιαν 05 18:20:59 mainland kernel: Bluetooth: hci0: No way to reset. Ignoring and
continuing
Ιαν 05 18:21:36 mainland kernel: Bluetooth: hci0: command 0x0408 tx timeout
Ιαν 05 18:21:36 mainland kernel: Bluetooth: hci0: No way to reset. Ignoring and
continuing

I think those are the ones that are logged when i cant use the mouse any more
and need to shutdown completely.

Might be usb related since afai understand the bluetooth adapter is connected
via USB.

-- 
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:[~2022-01-06 12:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-213829-62941@https.bugzilla.kernel.org/>
2021-09-10  4:41 ` [Bug 213829] Intel AX210 Bluetooth controller doesn't start from warm boot bugzilla-daemon
2021-10-17 18:05 ` bugzilla-daemon
2021-11-02 13:57 ` bugzilla-daemon
2021-11-02 20:02 ` bugzilla-daemon
2021-11-11  1:11 ` bugzilla-daemon
2021-11-11  3:12 ` bugzilla-daemon
2021-11-13  3:43 ` bugzilla-daemon
2021-11-13  9:19 ` bugzilla-daemon
2021-11-13 17:55 ` bugzilla-daemon
2021-11-14  8:07 ` bugzilla-daemon
2021-11-14 14:36 ` bugzilla-daemon
2021-11-25 12:19 ` bugzilla-daemon
2021-11-26 14:49 ` bugzilla-daemon
2022-01-02 20:37 ` bugzilla-daemon
2022-01-02 21:07 ` bugzilla-daemon
2022-01-06 12:58 ` bugzilla-daemon [this message]
2022-01-06 13:03 ` 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-213829-62941-D4VdCZB5hO@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).