Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TB3 controller not waking up after sleep causes panic #3

Closed
osy opened this issue Jun 27, 2019 · 1 comment
Closed

TB3 controller not waking up after sleep causes panic #3

osy opened this issue Jun 27, 2019 · 1 comment
Labels
hardware Hardware issues kernel KEXT and kernel issues thunderbolt Thunderbolt issues

Comments

@osy
Copy link
Owner

osy commented Jun 27, 2019

Related to #2

If the TB3 port is started successfully through force power or from a device plugged in during boot. If no device is plugged in when the computer sleeps and wakes up again, the kernel will panic with the message thunderbolt power on failed.

Limited success from calling TBFP () from the SSDT _PS0 function for RP05. However it does not solve the problem 100% of the time.

Workaround: Make sure at least one TB3 device is plugged in when computer goes to sleep if TB3 is enabled.
@osy osy added hardware Hardware issues kernel KEXT and kernel issues labels Jun 27, 2019
@osy osy closed this as completed in 3968cb4 Jun 28, 2019
@osy
Copy link
Owner Author

osy commented Jul 10, 2019

Re-opening this issue because the force-power UEFI driver + TBFP solution does not always work.

@osy osy reopened this Jul 10, 2019
@osy osy closed this as completed in c42767e Sep 16, 2019
@osy osy added the thunderbolt Thunderbolt issues label Dec 21, 2019
@deftdawg deftdawg mentioned this issue Jun 16, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
hardware Hardware issues kernel KEXT and kernel issues thunderbolt Thunderbolt issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@osy