Bug 1305797 - Deadlock when running minecraft with DRI_PRIME=1 on an optimus laptop
Deadlock when running minecraft with DRI_PRIME=1 on an optimus laptop
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-02-09 04:37 EST by Andrew Cook
Modified: 2018-04-06 14:00 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-06 14:00:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Cook 2016-02-09 04:37:54 EST
Description of problem:
Lock debugging reports a possible deadlock in dmesg before killing minecraft
Using i915 + nouveau in an optimus laptop

Version-Release number of selected component (if applicable):

How reproducible:
seems to be triggered reliably on my machine by setting DRI_PRIME=1 when running a modded instance of minecraft, specifically FTB Infinity from their launcher

Actual results:
Minecraft is killed
I had previously encountered this in 4.4.0, where it completely froze the screen, forcing a reboot

Expected results:
Minecraft runs and is rendered on the nvidia card

Additional info:
Kernel log: http://ur1.ca/ohw9p
Comment 1 Laura Abbott 2018-04-06 14:00:12 EDT
Doing some pruning, this bug looks to be years old. Please test on a newer kernel and reopen if the problem still exists.

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