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 198303] Bluetooth dies after a while.
Date: Mon, 17 Dec 2018 09:29:32 +0000	[thread overview]
Message-ID: <bug-198303-62941-DAFXLDTKhj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198303-62941@https.bugzilla.kernel.org/>

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

Mika Norén (mika.noren@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |PATCH_ALREADY_AVAILABLE

--- Comment #7 from Mika Norén (mika.noren@gmail.com) ---
(In reply to Grzegorz from comment #4)
> It would be helpfull if you attach logs from btmon (example: sudo btmon -i 0
> -w btmon.log) and from bluetoothd (sudo valgrind ./bluetoothd -n -d) -
> bluetoothd from bluez sources (you can checkout to 5.47-4 tag).
> 
> Regards,
> Grzegorz

As this issue has been solved in later kernel versions, I see no reason to keep
this open. Can be marked as solved. 

I'm not sure when it was solved though. Everything started to work as intended
after an update some time ago.

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

  parent reply	other threads:[~2018-12-17  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-198303-62941@https.bugzilla.kernel.org/>
2018-12-16  6:34 ` [Bug 198303] Bluetooth dies after a while bugzilla-daemon
2018-12-16  6:38 ` bugzilla-daemon
2018-12-17  9:29 ` bugzilla-daemon [this message]
2018-12-17  9:33 ` bugzilla-daemon
2018-12-17 20:07 ` bugzilla-daemon
2018-12-18 12:51 ` 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-198303-62941-DAFXLDTKhj@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).