Dualshock4 controller doesn't stay connected

[Goran Josic]

Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all.

Once the pairing is completed, if I try to connect it it doesn't stay connected.

I have checked the dmesg and apparently there is a buffer overflow somewhere.

I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

Dmesg output:

[ 4.099796] Bluetooth: Core ver 2.22
[ 4.099833] Bluetooth: HCI device and connection manager initialized
[ 4.099837] Bluetooth: HCI socket layer initialized
[ 4.099839] Bluetooth: L2CAP socket layer initialized
[ 4.099842] Bluetooth: SCO socket layer initialized
[ 4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
[ 6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.855413] Bluetooth: BNEP filters: protocol multicast
[ 6.855416] Bluetooth: BNEP socket layer initialized
[ 14.234706] Bluetooth: RFCOMM TTY layer initialized
[ 14.234711] Bluetooth: RFCOMM socket layer initialized
[ 14.234715] Bluetooth: RFCOMM ver 1.11
[ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow

Release:
Description: Ubuntu 19.10
Release: 19.10

Package Info:
bluez:
  Installed: 5.50-0ubuntu4
  Candidate: 5.50-0ubuntu4
  Version table:
 *** 5.50-0ubuntu4 500
        500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluez 5.50-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 28 14:11:19 2020
InstallationDate: Installed on 2019-11-26 (62 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20FCS33A00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
dmi.bios.date: 03/13/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET68W (1.42 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FCS33A00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 4th
dmi.product.name: 20FCS33A00
dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6
  UP RUNNING PSCAN
  RX bytes:8289 acl:41 sco:0 events:268 errors:0
  TX bytes:9494 acl:44 sco:0 commands:163 errors:0
syslog:

[Goran Josic (arael78)]

If I try to connect the controller with the usb cable it gets recognized as pulse audio source.

The controller model is: CUH-ZCT2U

This is the output of the dmesg:

[ 1882.762621] usb 1-1: new full-speed USB device number 6 using xhci_hcd
[ 1882.913951] usb 1-1: New USB device found, idVendor=054c, idProduct=09cc, bcdDevice= 1.00
[ 1882.913956] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1882.913960] usb 1-1: Product: Wireless Controller
[ 1882.913962] usb 1-1: Manufacturer: Sony Interactive Entertainment
[ 1882.951627] usbcore: registered new interface driver snd-usb-audio
[ 1882.952799] sony 0003:054C:09CC.0004: failed to retrieve feature report 0x81 with the DualShock 4 MAC address
[ 1882.952943] sony 0003:054C:09CC.0004: hidraw1: USB HID v81.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:00:14.0-1/input3
[ 1882.952945] sony 0003:054C:09CC.0004: failed to claim input
[ 1883.072399] retire_capture_urb: 28 callbacks suppressed
~ ❯❯❯

[Daniel van Vugt (vanvugt)]

It sounds like this might be the problem:

  Bluetooth: Dropping L2CAP data: receive buffer overflow

in which case that would be a kernel bug. So this has been assigned to the kernel.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Goran Josic (arael78)]

I have just tried with kernel 5.5.0-050500-generic I got from here:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/

Same issue.

[Kai-Heng Feng (kaihengfeng)]

Please try latest daily iso:
http://cdimages.ubuntu.com/daily-live/current/

[Goran Josic (arael78)]

I am waiting for the daily-iso to be downloaded but I suspect it will not solve the issue because I have already tried with the current kernel (5.5+) without success. Same issue. So unless this doesn't only involve the kernel I don't think that the daily iso will make any difference.

Is there any way I can provide more info about this bug?

[Goran Josic (arael78)]

I have tried the daily iso and the same things happens. Same error message as well.

If anybody else is reading this bug report and has the dualshock4 model CUH-ZCTU2 please try to pair it and post here the result.

[Kai-Heng Feng (kaihengfeng)]

Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Bluetooth

[Goran Josic (arael78)]

Done: https://bugzilla.kernel.org/show_bug.cgi?id=206457

[Bastian Bittorf (bbittorf)]

Same issue for me with fresh mainline kernel 5.5.2 on debian.
The controller model (the same) is: CUH-ZCT2U

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Goran Josic (arael78)]

Bastian, may I ask you to weight your controller? I suspect mine could be not a genuine one. I checked online and dualshock4 controllers weight around 220 grams. Mine weights 200 grams. The only way to understand if it is really copy is to examine the inner parts but I cannot open it because it would invalidate the warranty.

[Bastian Bittorf (bbittorf)]

@Goran:
both of mine controllers have a weight of 202 grams...
question: they where working on your machine earlier?

I have an onboard Intel Wireless-AC 9260 (rev 29) with recent firmware.

[Goran Josic (arael78)]

@Bastian: I have gotten mine on Amazon. It never worked on my Ubuntu machine and it does not pair with my sony smartphone. It pairs with my wife's thinkpad running windows 10 and it pairs with my old samsung tablet. Since I had mixed results and since the weight does not correspond I am starting to think that this controller might not be a genuine one. I got it on January 17 and I think I will return it.

I have Intel Corporation Wireless 8260 (rev 3a) with latest updates. fwupdmgr does not report any new update.

[Bastian Bittorf (bbittorf)]

Official specs say about den 2nd generation, that the weight is 209-210 grams.
https://en.wikipedia.org/wiki/DualShock

The Internet is full of people having problem to pair these,
but it worked with older kernels.

[Goran Josic (arael78)]

Thank you for the info Bastian. Now all we can do is wait for the bugfix.

[Bastian Bittorf (bbittorf)]

Same error during connect with kernel 5.6.0-rc2

When i press the "playstation"-button in the middle,
the connect works for a very short time (gets "blue")
and gets off with this message in kernel-log:

"Dropping L2CAP data: receive buffer overflow"

root@ryzen:/home/bastian# dmesg | grep Bluetooth
[ 8.589275] Bluetooth: Core ver 2.22
[ 8.589293] Bluetooth: HCI device and connection manager initialized
[ 8.589296] Bluetooth: HCI socket layer initialized
[ 8.589298] Bluetooth: L2CAP socket layer initialized
[ 8.589300] Bluetooth: SCO socket layer initialized
[ 8.738524] Bluetooth: hci0: Firmware revision 0.1 build 216 week 27 2019
[ 8.846171] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.846173] Bluetooth: BNEP filters: protocol multicast
[ 8.846179] Bluetooth: BNEP socket layer initialized
[ 11.148265] Bluetooth: RFCOMM TTY layer initialized
[ 11.148271] Bluetooth: RFCOMM socket layer initialized
[ 11.148276] Bluetooth: RFCOMM ver 1.11
[...]
[ 76.444821] Bluetooth: Dropping L2CAP data: receive buffer overflow

I can apply kernel-patches and debug on advise.

[Bastian Bittorf (bbittorf)]

attached is a hcidump during connect.

[Goran Josic (arael78)]

Same issue with kernel 5.6.10.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.