Bug 2242189

Summary:	kernel module hid_logitech_dj causes crash and broken USB in case receiver is connected on USB switch and toggled
Product:	[Fedora] Fedora	Reporter:	Peter Bieringer <pb>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	39	CC:	acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarod, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-10-05 18:31:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Bieringer 2023-10-04 20:32:37 UTC

1. Please describe the problem:
having Logitech receiver connected on a KVM switch the system went unusable after KVM switch action since some time.

Similar to reported
https://bugzilla.kernel.org/show_bug.cgi?id=217412#c58

BTW: crash is that bad that on ASRock J4125-ITX a power dis/reconnect is required , a power cycle is not solving the issue proper, resulting in strange USB timeouts during boot.

2. What is the Version-Release number of the kernel:
kernel-6.5.5-300.fc39.x86_64

2. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

It worked some time ago in F38 without any issue, since a while it was detected and looks like sporadic hangs turning worse from 6.4 to 6.5.

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


Temporary workaround:
cat <<END /etc/modprobe.d/logitech-blacklist.conf
blacklist hid_logitech_dj
END

Comment 1 Hans de Goede 2023-10-05 18:31:13 UTC

Peter thank you for this bug report.

I'm going to mark this as a duplicate of bug 2227221 since this as been reported several times already and all other identical bug reports have been marked as duplicates of bug 2227221 already so that everyone can track this in a single place.

However your bug report was not in vane. Reporting this has made me notice it and since I'm familiar with the driver I have spend pretty much my entire day looking into this and trying to reproduce it and I believe I have figured out the root cause + written a fix. Lets discuss this further in bug 2227221 where I'll add more details for everyone to see.

*** This bug has been marked as a duplicate of bug 2227221 ***