Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1336093

Summary:	please disable CONFIG_DEBUG_VM_PGFLAGS as it cause crash in X with nvida driver
Product:	[Fedora] Fedora	Reporter:	Knut J BJuland <knutjbj>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	23	CC:	gansalmon, itamar, jonathan, kernel-maint, 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:	2016-05-16 12:43:52 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 Knut J BJuland 2016-05-14 06:00:46 UTC

Description of problem:
page dumped because: VM_BUG_ON_PAGE(1 && PageCompound(page))
Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. launch system with kernel 4.5
2.
3.

Actual results:
page dumped because: VM_BUG_ON_PAGE(1 && PageCompound(page))
and 
Expected results:
I am recompiling witouth please disable CONFIG_DEBUG_VM_PGFLAGS
Additional info

https://devtalk.nvidia.com/default/topic/928352/crash-with-kernel-4-5-and-4-6/

Comment 1 Knut J BJuland 2016-05-14 11:26:21 UTC

I have now recompiled without  CONFIG_DEBUG_VM_PGFLAGS and I now able to launch X with nvida driver .I am also able to use D-Link Corp. DWA-160 802.11abgn Xtreme N Dual Band Adapter(rev.B2) [Ralink RT5572].

Comment 2 Josh Boyer 2016-05-16 12:43:52 UTC


*** This bug has been marked as a duplicate of bug 1335173 ***