Bug 1630414

Summary: OS freeze after connecting thunderbolt3 dock
Product: [Fedora] Fedora Reporter: Martin Hoyer <mhoyer>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, 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: 2019-02-21 21:09:46 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 Martin Hoyer 2018-09-18 14:44:48 UTC
Created attachment 1484402 [details]
dmesg

Description of problem:
After a re-connect of Lenovo thunderbolt dock, OS freezes, can't switch tty's, can't reboot.

Tried switching to x.org and managed to get a dmesg from tty2, but gnome was frozen

Version-Release number of selected component (if applicable):
4.18.7-200.fc28.x86_64
bolt-0.4-1.fc28.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Start F28
2.Connect Lenovo thunderbolt3 dock
 - in my case I have 2x displayport, ethernet, keyboard+mouse

Actual results:
Frozen OS

Expected results:
dock connected without issues

Additional info:
Using Carbon x1 gen6

Comment 1 Justin M. Forbes 2019-01-29 16:23:58 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Comment 2 Justin M. Forbes 2019-02-21 21:09:46 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.