All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Chou <max.chou@realtek.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	Hilda Wu <hildawu@realtek.com>
Cc: "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: Wed, 4 Oct 2023 03:07:24 +0000	[thread overview]
Message-ID: <b2ef2f1c457a4cf7a246b2e8b8598a30@realtek.com> (raw)
In-Reply-To: <ZRyqIn0_qqEFBPdy@debian.me>

Hi! Kirill,
I based on Kernel v6.5.5 and updated drivers/bluetooth to the last version of bluetooth-next tree for a test with RTL8761BUV.
The dmesg log and "hciconfig -a" are correct.
Could you share the dmesg for your failure case?

[56133.563293] usb 3-1: new full-speed USB device number 28 using xhci_hcd
[56133.712559] usb 3-1: New USB device found, idVendor=0bda, idProduct=8771, bcdDevice= 2.00
[56133.712577] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[56133.712582] usb 3-1: Product: Bluetooth Radio
[56133.712585] usb 3-1: Manufacturer: Realtek
[56133.712588] usb 3-1: SerialNumber: 00E04C239987
[56133.737812] usbcore: registered new interface driver btusb
[56133.742126] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[56133.743115] Bluetooth: hci0: RTL: rom_version status=0 version=1
[56133.743124] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[56133.743754] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[56133.743829] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[56133.913311] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[56133.980299] Bluetooth: MGMT ver 1.22

hci0:   Type: Primary  Bus: USB
        BD Address: 98:A2:35:85:56:F1  ACL MTU: 1021:6  SCO MTU: 255:12
        UP RUNNING
        RX bytes:1670 acl:0 sco:0 events:184 errors:0
        TX bytes:33917 acl:0 sco:0 commands:184 errors:0
        Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: PERIPHERAL ACCEPT
        Name: 'max-ThinkPad-X230'
        Class: 0x6c010c
        Service Classes: Rendering, Capturing, Audio, Telephony
        Device Class: Computer, Laptop
        HCI Version: 5.1 (0xa)  Revision: 0xdfc6
        LMP Version: 5.1 (0xa)  Subversion: 0xd922
        Manufacturer: Realtek Semiconductor Corporation (93)


BRs,
Max


> -----Original Message-----
> From: Bagas Sanjaya <bagasdotme@gmail.com>
> Sent: Wednesday, October 4, 2023 7:56 AM
> To: Kirill A. Shutemov <kirill@shutemov.name>; Hilda Wu
> <hildawu@realtek.com>
> Cc: 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
> 
> 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

  reply	other threads:[~2023-10-04  3:08 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 [this message]
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=b2ef2f1c457a4cf7a246b2e8b8598a30@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.