Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #84327 > unrolled thread

Bug#1085850: regression: bluetooth game controller no longer connects

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1085850: regression: bluetooth game controller no longer connects Forest <forestix@nom.one> - 2024-10-22 23:40 +0200
    Processed: Re: Bug#1085850: regression: bluetooth game controller  no longer connects "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-10-23 16:00 +0200
    Bug#1085850: regression: bluetooth game controller no longer connects Salvatore Bonaccorso <carnil@debian.org> - 2024-10-23 16:00 +0200
      Bug#1085850: regression: bluetooth game controller no longer connects Forest <forestix@nom.one> - 2024-10-23 19:10 +0200
        Bug#1085850: regression: bluetooth game controller no longer connects Forest <forestix@nom.one> - 2024-10-25 20:40 +0200
        Bug#1085850: regression: bluetooth game controller no longer connects Salvatore Bonaccorso <carnil@debian.org> - 2024-10-27 08:40 +0100
          Bug#1085850: regression: bluetooth game controller no longer connects Forest <forestix@nom.one> - 2024-10-30 18:00 +0100
    Bug#1085850: regression: bluetooth game controller no longer connects Nick Sal <specialroumpa@proton.me> - 2024-10-24 02:00 +0200
    Processed: Re: Bug#1085850: regression: bluetooth game controller  no longer connects "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-10-25 20:40 +0200

#84327 — Bug#1085850: regression: bluetooth game controller no longer connects

Package: src:linux
Version: 6.11.4-1
Severity: normal
X-Debbugs-Cc: forestix@nom.one

Dear Maintainer,

After upgrading from linux-image-6.11.2-amd64 to
linux-image-6.11.4-amd64, my Sony DualShock 4 v2 game controller no
longer connects over bluetooth.

I don't see any messages in dmesg or syslog when trying to
connect, nor any obviously relevant messages when I grep dmesg for
"bluetooth" or the driver names that I think are used on my system.
The device just seems to be ignored, and eventually gives up trying to
connect.

I haven't bisected this, but a local build of upstream kernel 6.11.5
(with Debian's config-6.11.4-amd64 as the .config file) restores
functionality. Also, I see several bluetooth fixes in the 6.11.5
changelog. I therefore suspect this regression originated upstream and
is fixed upstream.

-- Package-specific info:
** Kernel log: boot messages should be attached


-- System Information:
Debian Release: 12.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)

Versions of packages linux-image-6.11.4-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142+deb12u1
ii  kmod                                    30+20221128-1
ii  linux-base                              4.9

Versions of packages linux-image-6.11.4-amd64 recommends:
ii  apparmor  3.0.8-3

Versions of packages linux-image-6.11.4-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  firmware-linux-free     20200122-1
ii  grub-efi-amd64          2.06-13+deb12u1
pn  linux-doc-6.11          <none>

Versions of packages linux-image-6.11.4-amd64 is related to:
ii  firmware-amd-graphics     20240709-2~bpo12+1
ii  firmware-atheros          20230210-5
ii  firmware-bnx2             20230210-5
ii  firmware-bnx2x            20230210-5
ii  firmware-brcm80211        20230210-5
ii  firmware-cavium           20230210-5
ii  firmware-intel-sound      20230210-5
pn  firmware-intelwimax       <none>
ii  firmware-ipw2x00          20230210-5
ii  firmware-ivtv             20230210-5
ii  firmware-iwlwifi          20230210-5
ii  firmware-libertas         20230210-5
ii  firmware-linux-nonfree    20240709-2~bpo12+1
ii  firmware-misc-nonfree     20240709-2~bpo12+1
ii  firmware-myricom          20230210-5
ii  firmware-netxen           20230210-5
ii  firmware-qlogic           20230210-5
ii  firmware-realtek          20230210-5
ii  firmware-samsung          20230210-5
ii  firmware-siano            20230210-5
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#84329 — Processed: Re: Bug#1085850: regression: bluetooth game controller no longer connects

Processing control commands:

> tags -1 + moreinfo
Bug #1085850 [src:linux] regression: bluetooth game controller no longer connects
Added tag(s) moreinfo.

-- 
1085850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085850
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#84331

Control: tags -1 + moreinfo

Hi,

On Tue, Oct 22, 2024 at 02:31:03PM -0700, Forest wrote:
> Package: src:linux
> Version: 6.11.4-1
> Severity: normal
> X-Debbugs-Cc: forestix@nom.one
> 
> Dear Maintainer,
> 
> After upgrading from linux-image-6.11.2-amd64 to
> linux-image-6.11.4-amd64, my Sony DualShock 4 v2 game controller no
> longer connects over bluetooth.
> 
> I don't see any messages in dmesg or syslog when trying to
> connect, nor any obviously relevant messages when I grep dmesg for
> "bluetooth" or the driver names that I think are used on my system.
> The device just seems to be ignored, and eventually gives up trying to
> connect.
> 
> I haven't bisected this, but a local build of upstream kernel 6.11.5
> (with Debian's config-6.11.4-amd64 as the .config file) restores
> functionality. Also, I see several bluetooth fixes in the 6.11.5
> changelog. I therefore suspect this regression originated upstream and
> is fixed upstream.

having the possibility to identify the fixing commit would indeed be
nice, but I can understand knowing 6.11.5 fixes the issue this looks
like additional unnecessary work.

Do you maybe can share dmesg information from booting with the old
kernel with the controller available?

I wonder if this might be related to 2c1dda2acc41 ("Bluetooth: btusb:
Fix regression with fake CSR controllers 0a12:0001") which was
backported to 6.11.5.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#84332

On Wed, 23 Oct 2024 15:46:26 +0200, Salvatore Bonaccorso wrote:

>Do you maybe can share dmesg information from booting with the old
>kernel with the controller available?

Given that we're talking about a wireless controller that is never connected
at boot time, do you expect dmesg to show anything about it?

>I wonder if this might be related to 2c1dda2acc41 ("Bluetooth: btusb:
>Fix regression with fake CSR controllers 0a12:0001") which was
>backported to 6.11.5.

I saw that and wondered the same thing. If that turned out to be the
applicable commit, then I would be skeptical of its description, because I
have every reason to believe this is a genuine Sony game controller. (It has
all the visual signs of one, and was purchased directly from a major
brick-and-mortar retailer.) It would be a little surprising if there was a
fake CSR chip inside, as I don't think Sony is known for using fake parts,
although I guess it's always possible that a manufacturer used one without
telling Sony.

[toc] | [prev] | [next] | [standalone]

#84356

Control: tags -1 - moreinfo

I still don't know any examples of an unpaired bluetooth device triggering
dmesg entries at boot time.  (If this ever happens with any such device, I
would be interested in knowing how and why.)

But since you asked, I tried it anyway.  The device enters pairing mode as
soon as I press the wake button, and goes back to sleep if not paired after
several seconds, so I had to carefully synchronize it with choosing a boot
entry in GRUB.  As expected, dmesg | grep -E '( bt)|bluetooth' yielded
nothing interesting.  So btusb (the module affected by 2c1dda2acc41) was
apparently not complaining.

[toc] | [prev] | [next] | [standalone]

#84368

Hi,

On Wed, Oct 23, 2024 at 09:53:47AM -0700, Forest wrote:
> On Wed, 23 Oct 2024 15:46:26 +0200, Salvatore Bonaccorso wrote:
> 
> >Do you maybe can share dmesg information from booting with the old
> >kernel with the controller available?
> 
> Given that we're talking about a wireless controller that is never connected
> at boot time, do you expect dmesg to show anything about it?
> 
> >I wonder if this might be related to 2c1dda2acc41 ("Bluetooth: btusb:
> >Fix regression with fake CSR controllers 0a12:0001") which was
> >backported to 6.11.5.
> 
> I saw that and wondered the same thing. If that turned out to be the
> applicable commit, then I would be skeptical of its description, because I
> have every reason to believe this is a genuine Sony game controller. (It has
> all the visual signs of one, and was purchased directly from a major
> brick-and-mortar retailer.) It would be a little surprising if there was a
> fake CSR chip inside, as I don't think Sony is known for using fake parts,
> although I guess it's always possible that a manufacturer used one without
> telling Sony.

As per https://lists.debian.org/debian-kernel/2024/10/msg00267.html I
uploaded 6.11.5-1 now to unstable. As we were not identifying the
upstream change fixing the issue, I have manually marked the bug as
fixed with 6.11.5-1, so once ftp-master accepts it through NEW and
packages build you should be able to get the controller back working.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#84401

On Sun, 27 Oct 2024 08:37:32 +0100, Salvatore Bonaccorso wrote:

>I uploaded 6.11.5-1 now to unstable. As we were not identifying the
>upstream change fixing the issue, I have manually marked the bug as
>fixed with 6.11.5-1, so once ftp-master accepts it through NEW and
>packages build you should be able to get the controller back working.

Thank you. A quick test of the 6.11.5 Unstable package shows that it fixes
the problem, as expected.

[toc] | [prev] | [next] | [standalone]

#84347

[Multipart message — attachments visible in raw view] — view raw

Hi,

I can confirm this bug, i.e. not pairing, for my external bluetooth keyboard.
This happened immediately after installing linux-6.11.4-amd64.
When booting with linux-6.11.2-amd64 then everything works perfectly!

It would be great to have this fixed!

Cheers,
Nick

[toc] | [prev] | [next] | [standalone]

#84355 — Processed: Re: Bug#1085850: regression: bluetooth game controller no longer connects

Processing control commands:

> tags -1 - moreinfo
Bug #1085850 [src:linux] regression: bluetooth game controller no longer connects
Removed tag(s) moreinfo.

-- 
1085850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085850
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web