From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 206457] New: Gamepad Dualshock4 CUH-ZCT2U doesn't pair or connect
Date: Fri, 07 Feb 2020 13:35:12 +0000 [thread overview]
Message-ID: <bug-206457-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206457
Bug ID: 206457
Summary: Gamepad Dualshock4 CUH-ZCT2U doesn't pair or connect
Product: Drivers
Version: 2.5
Kernel Version: 5.5+
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: arael78@gmail.com
Regression: No
Pairing the Dualshock4 controller does not complete correctly, even after
several attempts.
Once the pairing is apparently completed (I have to switch off the controller
to interrupt the pairing process), when I try to connect it it doesn't stay
connected.
I have checked the dmesg and apparently there is a buffer overflow.
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 kernel 5.5 and current 5.5+ it doesn't work. I tried other
kernels from 5.0 up. None worked.
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
If I try to use USB cable I get this error:
[ 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
My distro is Ubuntu 19.04 and I have already filed a bug there. I was asked to
submit a report here too. On that report there are other logs which might be
useful here. Let me know if it is enough or if you need more info.
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063
Thank you very much for your help.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-02-07 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 13:35 bugzilla-daemon [this message]
2020-08-04 23:31 ` [Bug 206457] Gamepad Dualshock4 CUH-ZCT2U doesn't pair or connect bugzilla-daemon
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=bug-206457-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/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).