public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 204877] [Regression] Linux 5.3 breaks connecting a DualShock 4 controller via bluetooth
Date: Mon, 16 Sep 2019 13:34:42 +0000	[thread overview]
Message-ID: <bug-204877-62941-ITM7lesNWR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204877-62941@https.bugzilla.kernel.org/>

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

George Gibbs (Vash63@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Vash63@gmail.com

--- Comment #1 from George Gibbs (Vash63@gmail.com) ---
I can duplicate this issue on both a DS4 v1 (model CUH-ZTC1U) and a v2 (model
CUH-ZCT2U), though the crc check numbers are slightly different.

CUH-ZTC1U:
kernel: sony 0005:054C:05C4.0017: unknown main item tag 0x0
kernel: sony 0005:054C:05C4.0017: DualShock 4 calibration report's CRC check
failed, received crc 0x1cffff8c != 0xdfe3b226
kernel: sony 0005:054C:05C4.0017: Retrying DualShock 4 get calibration report
request
kernel: sony 0005:054C:05C4.0017: DualShock 4 calibration report's CRC check
failed, received crc 0x1cffff8c != 0xdfe3b226
kernel: sony 0005:054C:05C4.0017: Retrying DualShock 4 get calibration report
request
kernel: sony 0005:054C:05C4.0017: DualShock 4 calibration report's CRC check
failed, received crc 0x1cffff8c != 0xdfe3b226
kernel: sony 0005:054C:05C4.0017: Failed to get calibration data from Dualshock
4
kernel: sony 0005:054C:05C4.0017: hidraw18: BLUETOOTH HID v81.00 Gamepad
[Wireless Controller] on a0:c5:89:b5:44:e1
kernel: sony 0005:054C:05C4.0017: failed to claim input

CUH-ZCT2U:
kernel: sony 0005:054C:09CC.0019: unknown main item tag 0x0
kernel: sony 0005:054C:09CC.0019: DualShock 4 calibration report's CRC check
failed, received crc 0x1cffff8c != 0x48b66901
kernel: sony 0005:054C:09CC.0019: Retrying DualShock 4 get calibration report
request
kernel: sony 0005:054C:09CC.0019: DualShock 4 calibration report's CRC check
failed, received crc 0x1cffff8c != 0x48b66901
kernel: sony 0005:054C:09CC.0019: Retrying DualShock 4 get calibration report
request
kernel: sony 0005:054C:09CC.0019: DualShock 4 calibration report's CRC check
failed, received crc 0x1cffff8c != 0x48b66901
kernel: sony 0005:054C:09CC.0019: Failed to get calibration data from Dualshock
4
kernel: sony 0005:054C:09CC.0019: hidraw19: BLUETOOTH HID v80.01 Gamepad
[Wireless Controller] on a0:c5:89:b5:44:e1
kernel: sony 0005:054C:09CC.0019: failed to claim input

-- 
You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2019-09-16 13:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 11:11 [Bug 204877] New: [Regression] Linux 5.3 break connecting a DualShock 4 controller via bluetooth bugzilla-daemon
2019-09-16 13:34 ` bugzilla-daemon [this message]
2019-09-20 20:20 ` [Bug 204877] [Regression] Linux 5.3 breaks " bugzilla-daemon
2019-09-21  8:18 ` bugzilla-daemon
2019-09-21 23:18 ` bugzilla-daemon
2019-09-22  0:43 ` 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-204877-62941-ITM7lesNWR@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