Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2059568

Summary: thunderbolt usb hub not connecting
Product: Red Hat Enterprise Linux 9 Reporter: Peter Kopec <pekopec>
Component: boltAssignee: Kate Hsuan <hpa>
Status: CLOSED NEXTRELEASE QA Contact: Fendy Tjahjadi <ftjahjad>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: jkoten, pekopec, rvr, tpelka
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-18 08:58:32 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:
Attachments:
Description Flags
dmesg none

Description Peter Kopec 2022-03-01 10:57:55 UTC
Created attachment 1863687 [details]
dmesg

Description of problem:
I am using Monitor with build in USB hub and KVM switch and is connected to laptop via thunderbolt 3 cable. 
After 2 or 3 kvm switches usb devices connected via monitor stop working but image output is still working. 

After disconnecting cable from laptop  "boltclt list" will show monitor still as connected, after connecting  it will show as disconnected and after another disconnect and connect everything works till next KVM switches.


Version-Release number of selected component (if applicable): bolt-0.9.1-4.el9.x86_64


How reproducible: 100%


Additional info:
Laptop: Lenovo T14s gen 1 
Monitor: Benq PD2720U

Comment 1 Peter Kopec 2022-03-01 11:00:44 UTC
Created attachment 1863688 [details]
bolt journal

Comment 4 Kate Hsuan 2023-07-07 09:32:04 UTC
Hi,

Thank you for reporting it.

Could you please try to update the firmware of the monitor and laptop, boltd, and RHEL kernel to see if the issue still appears?

Thank you

Comment 5 Peter Kopec 2023-07-17 14:33:01 UTC
Hi, 
currently this problem is not happening anymore for me.
I dont know at which point it started working but only think i have done since then is OS update.

Comment 6 Kate Hsuan 2023-07-18 07:19:22 UTC
Hi,

Great to hear that. The usci issues of kernel, such as NULL pointer, race condition, and canceling a queued command were got fixed. I believe the issues you reported were fixed through those patches.
Now, the system works properly and this bug could be closed. Would you mind me closing the issue or do you want to close it yourself?

Thank you

Comment 7 Peter Kopec 2023-07-18 08:58:32 UTC
Closing this issue as it is not happening anymore and most likely was fixed in previous updates, see comments above.