Bug 1630414 - OS freeze after connecting thunderbolt3 dock
Summary: OS freeze after connecting thunderbolt3 dock
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-18 14:44 UTC by Martin Hoyer
Modified: 2019-02-21 21:09 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-21 21:09:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (119.17 KB, text/plain)
2018-09-18 14:44 UTC, Martin Hoyer
no flags Details

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.


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