Bug 1305797

Summary:	Deadlock when running minecraft with DRI_PRIME=1 on an optimus laptop
Product:	[Fedora] Fedora	Reporter:	Andrew Cook <ariscop>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	gansalmon, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-06 18:00:12 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:

Description Andrew Cook 2016-02-09 09:37:54 UTC

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):
4.5.0-0.rc2.git3.1.fc24.x86_64

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 18:00:12 UTC

Doing some pruning, this bug looks to be years old. Please test on a newer kernel and reopen if the problem still exists.