From: Max Chou <max.chou@realtek.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Hilda Wu <hildawu@realtek.com>,
"alex_lu@realsil.com.cn" <alex_lu@realsil.com.cn>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.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: Fri, 6 Oct 2023 01:22:28 +0000 [thread overview]
Message-ID: <732012844f544d0daf790434025c8fb3@realtek.com> (raw)
In-Reply-To: <20231004114609.dca6ebtmx37fsx5l@box.shutemov.name>
Hi!
Realtek will send a patch to fix this issue.
BRs,
Max
> -----Original Message-----
> From: Kirill A. Shutemov <kirill@shutemov.name>
> Sent: Wednesday, October 4, 2023 7:46 PM
> To: Max Chou <max.chou@realtek.com>
> Cc: Bagas Sanjaya <bagasdotme@gmail.com>; Hilda Wu
> <hildawu@realtek.com>; alex_lu@realsil.com.cn; Luiz Augusto von Dentz
> <luiz.von.dentz@intel.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
>
>
> External mail.
>
>
>
> On Wed, Oct 04, 2023 at 07:28:45AM +0000, Max Chou wrote:
> > Hi! Kirill,
> > I guess the root cause is as below.
> > ===
> > static int btrtl_register_devcoredump_support(struct hci_dev *hdev) {
> > int err;
> >
> > err = hci_devcd_register(hdev, btrtl_coredump, btrtl_dmp_hdr,
> > NULL);
> >
> > return err;
> > }
> > ===
> > If CONFIG_DEV_COREDUMP is not enabled, it would return -EOPNOTSUPP
> for hci_devcd_register().
> > Unfortunately, btrtl_register_devcoredump_support() will return it.
> > Finally, -EOPNOSTUPP will be returned for btrtl_setup_realtek().
> >
> > Could you have the following workaround for the root cause checked?
> > Please share dmesg as well. Thanks,
>
> Yes. It works and I see
>
> [ 3.640539] Bluetooth: hci0: RTL: btrtl_register_devcoredump_support():
> err = -95
>
> in dmesg. -EOPNOTSUPP indeed.
>
> --
> Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2023-10-06 1:23 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
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 [this message]
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=732012844f544d0daf790434025c8fb3@realtek.com \
--to=max.chou@realtek.com \
--cc=alex_lu@realsil.com.cn \
--cc=bagasdotme@gmail.com \
--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=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