lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Tue, 18 Jun 2024 09:44:14 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Edward Wawrzynski <ewawrzynski16@...il.com>,
 Linux regressions mailing list <regressions@...ts.linux.dev>,
 "open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: Xinput Controllers No Longer Working

Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
for once, to make this easily accessible to everyone.

Dmitry, Edward seems to have some regression with Xinput Controllers no
Longer Working since v6.8..v6.9 and still not working with mainline. The
thread starts here:
https://lore.kernel.org/all/CABRw72orHLEqpAS%3DcW1ThGkVUW0juqc7Y_-N2%3Do-k0rSqgpLxA@mail.gmail.com/

Dmesg files are attached to the parent of this mail. I briefly looked
into them but no obvious problem jumped out to me untrained eyes.

Edward, with a bit of luck Dmitry might have an idea what's wrong here.
But if not you might need to perform a git bisection to find the change
that broke things:
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html

That process would also rule out that some config change on the Fedora
side causes this.

Ciao, Thorsten

On 18.06.24 02:03, Edward Wawrzynski wrote:
> Hi Thorsten - I've removed the stable mailing list.
> 
> Sorry I took so long to respond. I just got the information you
> requested. To add onto the previous report, the kernel I booted into
> this time is 6.8.12, and the Xinput controllers still work perfectly.
> 
> I've attached two separate files I've generated, one on 6.9.4 (the
> broken one) and one on 6.8.12 (the working one). Please let me know if
> I can be of any further assistance.
> 
> On Mon, Jun 17, 2024 at 12:14 PM Linux regression tracking (Thorsten
> Leemhuis) <regressions@...mhuis.info> wrote:
>>
>> [to anyone that replies to this: please drop the stable mailing list
>> from CC, as this sounds like a mainline regressin]
>>
>> Hi Edward! Thx for your report
>>
>> On 17.06.24 17:37, Edward Wawrzynski wrote:
>>>
>>> I was reaching out to report that there's been a regression in the
>>> latest stable 6.9.4 kernel. I'm using Fedora 40 and 6.9.4 just got
>>> pushed to the repos recently. Upon updating, my wired USB Xinput
>>> controllers no longer get detected.
>>>
>>> I've tried two 8BitDo controllers, the one being the 8BitDo Pro 2
>>> Bluetooth (with a USB cable) and the other being the 8BitDo Pro 2
>>> Wired Controller for Xbox. Neither of them are being detected on
>>> Kernel 6.9.4, despite previously working throughout the lifetime of
>>> Fedora 40's 6.8.x kernel versions, the latest being 6.8.11. I've also
>>> tried the vanilla kernel, as well as the latest vanilla mainline
>>> kernel from Fedora's COPR: 6.10.0-0.rc4.337.vanilla.fc40.x86_64.
>>>
>>> To reproduce, simply load Kernel 6.9.4+
>>
>> That sounds a lot like it is a mainline regression that was introduced
>> between 6.8.y and 6.9;
>>
>>> and plug a USB controller in
>>> with XInput (either an Xbox controller or something else that emulates
>>> one). It won't be detected. I plugged in a PS5 controller and it
>>> worked, but when I plugged in an Xbox Series S controller, it didn't
>>> work. The 8BitDo Pro 2 Bluetooth controller has four different
>>> settings (Switch, Android, DirectInput, Xinput), and it was detected
>>> and worked on every setting except for the Xinput setting. Reverting
>>> to version 6.8.11 fixes the issues immediately.
>>
>> Could you please share the output of "journalctl --dmesg --output=short"
>> for both a working and a broken kernel?

--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

P.S.: let me add this to the tracking:

#regzbot report /
#regzbot introduced v6.8..v6.9
#regzbot title input: Xinput Controllers No Longer Working
#regzbot ignore-activity

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ