Linux-Serial Archive mirror
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	linux-serial@vger.kernel.org
Cc: Peter Collingbourne <pcc@google.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [Bug] staging: rtl8723bs: Bluetooth stops working after patch: serial: 8250_dw: Do not reclock if already at correct rate
Date: Tue, 14 May 2024 06:32:37 +0200	[thread overview]
Message-ID: <8fe72cec-adba-42dd-9185-15e777714a81@gmail.com> (raw)

Hi,

I have a ODYS Trendbook next 14 with the wlan/bluetooth module rtl8723bs.

Bluetooth stops working with the following commit:
commit e5d6bd25f93d6ae158bb4cd04956cb497a85b8ef (HEAD)
Author: Peter Collingbourne <pcc@google.com>
Date:   Thu Feb 22 11:26:34 2024 -0800
     serial: 8250_dw: Do not reclock if already at correct rate

Please find dmesg below. Module has issues to load firmware.

To enshure that this is the function breaking commit I applied the 
commit reversed on top of the latest kernel from the staging tree. Then 
bluetooth is working again.

I can support with further tests. I do not have a good proposal for a 
fix as I expect a lot of side effects. Please send me proposals for a 
fix. Comming Thursday I will be OOO.

Thanks for your support.

Bye Philipp


dmesg when not working:
[   26.904914] Bluetooth: Core ver 2.22
[   26.905130] NET: Registered PF_BLUETOOTH protocol family
[   26.905136] Bluetooth: HCI device and connection manager initialized
[   26.905154] Bluetooth: HCI socket layer initialized
[   26.905161] Bluetooth: L2CAP socket layer initialized
[   26.905184] Bluetooth: SCO socket layer initialized
[   27.291346] audit: type=1130 audit(1715629261.116:39): pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=systemd-tmpfiles-setup comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   27.335410] audit: type=1334 audit(1715629261.160:40): prog-id=57 op=LOAD
[   29.472422] usb 1-4: Found UVC 1.00 device USB 2.0 Camera (058f:5608)
[   29.494762] usbcore: registered new interface driver uvcvideo
[   29.506692] RPC: Registered named UNIX socket transport module.
[   29.506704] RPC: Registered udp transport module.
[   29.506707] RPC: Registered tcp transport module.
[   29.506709] RPC: Registered tcp-with-tls transport module.
[   29.506711] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   29.532484] Bluetooth: HCI UART driver ver 2.3
[   29.532503] Bluetooth: HCI UART protocol H4 registered
[   29.532507] Bluetooth: HCI UART protocol BCSP registered
[   29.532594] Bluetooth: HCI UART protocol LL registered
[   29.532599] Bluetooth: HCI UART protocol ATH3K registered
[   29.533139] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   29.533325] Bluetooth: HCI UART protocol Intel registered
[   29.533506] Bluetooth: HCI UART protocol Broadcom registered
[   29.533541] Bluetooth: HCI UART protocol QCA registered
[   29.533546] Bluetooth: HCI UART protocol AG6XX registered
[   29.533572] Bluetooth: HCI UART protocol Marvell registered
[   30.114887] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
[   30.172864] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   30.175628] Loaded X.509 cert 'wens: 
61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   30.269514] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b 
lmp_ver=06 lmp_subver=8723
[   30.273192] Bluetooth: hci0: RTL: rom_version status=0 version=1
[   30.273218] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723bs_fw.bin
[   30.300067] Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8723bs_config-OBDA8723.bin
[   30.328993] Bluetooth: hci0: RTL: cfg_sz 64, total sz 24508
[   30.617609] input: chtnau8824 Headset as 
/devices/pci0000:00/808622A8:00/cht-bsw-nau8824/sound/card1/input15
[   31.630950] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   31.630966] Bluetooth: BNEP filters: protocol multicast
[   31.631013] Bluetooth: BNEP socket layer initialized
[   32.388997] Bluetooth: hci0: command 0xfc20 tx timeout
[   33.397774] NET: Registered PF_QIPCRTR protocol family
[   35.872260] r8723bs: module is from the staging directory, the 
quality is unknown, you have been warned.
[   36.008866] pnetdev = 0000000086c577c1
[   38.957652] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin
[   39.065930] ax88179_178a 2-1:1.0 enp0s20u1: ax88179 - Link status is: 1
[   40.516641] Bluetooth: hci0: RTL: download fw command failed (-110)
[   41.754022] ax88179_178a 2-1:1.0 enp0s20u1: ax88179 - Link status is: 1
[   62.939117] rfkill: input handler disabled
[   66.873746] intel_sst_acpi 808622A8:00: FW Version 01.0b.02.02
[   95.201213] systemd-journald[587]: 
/var/log/journal/deb6c1cc9b434036821e1d20b20e14ec/user-1000.journal: 
Journal file uses a different sequence number ID, rotating.
[   96.212917] rfkill: input handler enabled
[  104.357628] rfkill: input handler disabled
[  124.215728]  mmcblk1: p1 p2 p3
[  169.291952] netfs: FS-Cache loaded
[  169.343759] Key type dns_resolver registered
[  170.689598] Key type cifs.spnego registered
[  170.689677] Key type cifs.idmap registered
[  170.691671] CIFS: Attempting to mount //192.168.2.110/kernelcomp
[  181.038648]  mmcblk1: p1 p2 p3

             reply	other threads:[~2024-05-14  4:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  4:32 Philipp Hortmann [this message]
2024-05-14 12:55 ` [Bug] staging: rtl8723bs: Bluetooth stops working after patch: serial: 8250_dw: Do not reclock if already at correct rate Andy Shevchenko

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=8fe72cec-adba-42dd-9185-15e777714a81@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=pcc@google.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).