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 - please disable CONFIG_DEBUG_VM_PGFLAGS as it cause crash in X with nvida driver
Summary: please disable CONFIG_DEBUG_VM_PGFLAGS as it cause crash in X with nvida driver
Keywords:
Status: CLOSED DUPLICATE of bug 1335173
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-14 06:00 UTC by Knut J BJuland
Modified: 2016-05-16 12:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-16 12:43:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.