linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Erik Dobák" <erik.dobak@gmail.com>,
	"Linux Stable" <stable@vger.kernel.org>,
	"Linux Bluetooth" <linux-bluetooth@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"Linux Mediatek" <linux-mediatek@lists.infradead.org>,
	"Linux Regressions" <regressions@lists.linux.dev>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
	"Johan Hedberg" <johan.hedberg@gmail.com>,
	"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Tomasz Moń" <tomasz.mon@nordicsemi.no>
Subject: Re: bluetooth issues since kernel 6.4 - not discovering other bt devices - /linux/drivers/bluetooth/btusb.c
Date: Tue, 3 Oct 2023 06:46:58 +0700	[thread overview]
Message-ID: <ZRtWcgiH5JhD5NU2@debian.me> (raw)
In-Reply-To: <CAH7-e5sb+kT_LRb1_y-c5JaFN0=KrrRT97otUPKzTCgzGsVdrQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2049 bytes --]

On Sun, Oct 01, 2023 at 07:47:54AM +0200, Erik Dobák wrote:
> Hello!
> 
> I bought a new laptop fujitsu life book and everything is going fine
> on artix just the bt makes trouble:
> 
> /var/log/error.log
> Sep 30 18:43:48 nexus bluetoothd[2266]:
> src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv
> Monitors: Failed (0x03)
> Sep 30 18:43:48 nexus bluetoothd[2266]: Failed to clear UUIDs: Failed (0x03)
> Sep 30 18:43:48 nexus bluetoothd[2266]: Failed to add UUID: Failed (0x03)
> Sep 30 18:43:48 nexus bluetoothd[2266]: Failed to add UUID: Failed (0x03)
> 
> i searched a bit the webs and found a new commit at kernel org that
> does do the trouble:
> https://bugs.archlinux.org/task/78980
> 
> follow the linkeys inside the commits there or read this one:
> 
> ---------------before------------------------------------
> /* interface numbers are hardcoded in the spec */
>         if (intf->cur_altsetting->desc.bInterfaceNumber != 0) {
>                 if (!(id->driver_info & BTUSB_IFNUM_2))
>                         return -ENODEV;
>                 if (intf->cur_altsetting->desc.bInterfaceNumber != 2)
>                         return -ENODEV;
>         }
> -----------after----------------------------------------------------
> if ((id->driver_info & BTUSB_IFNUM_2) &&
>     (intf->cur_altsetting->desc.bInterfaceNumber != 0) &&
>     (intf->cur_altsetting->desc.bInterfaceNumber != 2))
> return -ENODEV;
> --------------------------------------------------------
> 
> the dude just hooked up 3 conditions in a row with && where before it
> was 2 conditions in 1 condition. + the comment was removed.
> 
> 

Try latest mainline first (currently v6.6-rc4). Because you have to
compile your own kernel, please refer to
Documentation/admin-guide/quickly-build-trimmed-linux.rst if you don't know how to do the compilation.

Also, don't top-post when replying; reply inline with appropriate context
instead.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

       reply	other threads:[~2023-10-02 23:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH7-e5sb+kT_LRb1_y-c5JaFN0=KrrRT97otUPKzTCgzGsVdrQ@mail.gmail.com>
2023-10-02 23:46 ` Bagas Sanjaya [this message]
2023-10-03 12:25   ` bluetooth issues since kernel 6.4 - not discovering other bt devices - /linux/drivers/bluetooth/btusb.c Erik Dobák
2023-10-03 12:31     ` Tomasz Moń
2023-10-03 12:42       ` Erik Dobák
2023-10-03 13:08         ` Tomasz Moń
2023-10-03 16:10           ` Erik Dobák
2023-10-04  5:20             ` Linux regression tracking (Thorsten Leemhuis)
2023-10-04  6:35               ` Erik Dobák

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=ZRtWcgiH5JhD5NU2@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=erik.dobak@gmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=matthias.bgg@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tomasz.mon@nordicsemi.no \
    /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).