From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Hilda Wu <hildawu@realtek.com>
Cc: Alex Lu <alex_lu@realsil.com.cn>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Max Chou <max.chou@realtek.com>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Juerg Haefliger <juerg.haefliger@canonical.com>,
Linux Bluetooth <linux-bluetooth@vger.kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression: devcoredump patch broke Realtek usb bluetooth adapter
Date: Wed, 4 Oct 2023 06:56:18 +0700 [thread overview]
Message-ID: <ZRyqIn0_qqEFBPdy@debian.me> (raw)
In-Reply-To: <20231003182038.k57nirtt4sonvt7c@box.shutemov.name>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
On Tue, Oct 03, 2023 at 09:20:38PM +0300, Kirill A. Shutemov wrote:
> Hi,
>
> Commit 044014ce85a1 ("Bluetooth: btrtl: Add Realtek devcoredump support")
> broke Realtek-based ASUS USB-BT500, ID 0b05:190e.
>
> Devices failed to connect. hciconfig showed a controller with all-zero BD
> address.
What is its output then? And dmesg log?
>
> I reverted the commit as well as bd003fb338af that depends on the commit.
> It made the problem go away.
>
> I know virtually nothing about bluetooth. Let me know what info you need
> to debug the issue.
>
Hilda, it looks like this regression is caused by a commit of yours. Would
you like to take a look on it?
Regardless, thanks for the regression report. I'm adding it to regzbot:
#regzbot ^introduced: 044014ce85a17c
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-03 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 18:20 Regression: devcoredump patch broke Realtek usb bluetooth adapter Kirill A. Shutemov
2023-10-03 23:56 ` Bagas Sanjaya [this message]
2023-10-04 3:07 ` Max Chou
2023-10-04 4:49 ` Kirill A. Shutemov
2023-10-04 5:44 ` Max Chou
2023-10-04 7:28 ` Max Chou
2023-10-04 11:46 ` Kirill A. Shutemov
2023-10-06 1:22 ` Max Chou
2023-10-13 13:24 ` Linux regression tracking #update (Thorsten Leemhuis)
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=ZRyqIn0_qqEFBPdy@debian.me \
--to=bagasdotme@gmail.com \
--cc=alex_lu@realsil.com.cn \
--cc=hildawu@realtek.com \
--cc=johan.hedberg@gmail.com \
--cc=juerg.haefliger@canonical.com \
--cc=kirill@shutemov.name \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=regressions@lists.linux.dev \
/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