Bug 1747755 - Sony DualShock 4 fails to claim input
Summary: Sony DualShock 4 fails to claim input
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-01 09:22 UTC by Antoine Saroufim
Modified: 2019-09-22 07:21 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-22 07:21:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Logs (72.62 KB, text/plain)
2019-09-01 09:22 UTC, Antoine Saroufim
no flags Details

Description Antoine Saroufim 2019-09-01 09:22:16 UTC
Created attachment 1610473 [details]
Logs

1. Please describe the problem:
After a kernel update, the DaulShock 4 controller no longer provides any input. It connects but its led color does not change and it does not provide any input events whatsoever. 

The only relevant logs are:
sony 0005:054C:09CC.0006: Failed to get calibration data from Dualshock 4
sony 0005:054C:09CC.0006: failed to claim input
kernel device:+hid:0005:054C:09CC.0006

2. What is the Version-Release number of the kernel:

kernel-5.3.0-0.rc6.git0.1.fc31.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
Yes, it worked previously and it started appearing with kernel-5.3.0-0.rc6.git0.1.fc31.x86_64


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Simply pairing the device and connecting it produces this problem

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
I haven't tried the rawhide kernel.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No, I have a stock Fedora Silverblue system 

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Attached


Additional info: My phone can still pair with Fedora just fine. The controller can pair with my phone just fine. It's when the controller tries to pair with Fedora that I experience the issue so I'm assuming that there is no fault with the hardware of either one. I have also tried resetting the controller and pairing it again multiple times with no luck.

Comment 1 Dan Elkouby 2019-09-06 10:20:22 UTC
I've run into the same issue on Arch Linux while running mainline kernels.
5.3-rc5 was fine, rc6 and rc7 are broken. The controller still works fine when connected with a USB cable.

I've bisected the regression and submitted a fix upstream [1].

[1] https://lore.kernel.org/patchwork/patch/1125039/

Comment 2 Antoine Saroufim 2019-09-06 11:57:16 UTC
Thank you very much for your efforts. Once the fix is accepted, I will test again and update the bug report accordingly.

Comment 3 Dan Elkouby 2019-09-06 12:04:55 UTC
If you're going to monitor this, you should probably watch the second version of the patch [1].
If I remember, I will post here once it gets merged.

[1] https://lore.kernel.org/patchwork/patch/1125068/

Comment 4 Antoine Saroufim 2019-09-22 07:21:20 UTC
Fixed upstream as per https://bugzilla.kernel.org/show_bug.cgi?id=204877


Note You need to log in before you can comment on or make changes to this bug.