Bug 1298885

Summary: kernel 4.3.3 crashing when using Xorg
Product: [Fedora] Fedora Reporter: Erwan GEORGET <egeorget>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 23CC: bigant, christof, egeorget, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-15 18:59:08 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:
Attachments:
Description Flags
Xorg log
none
Screenshot after crash none

Description Erwan GEORGET 2016-01-15 11:10:34 UTC
Created attachment 1115101 [details]
Xorg log

Description of problem:

After updating to latest kernel, I'm unable to log in using the the Gnome default session (using Xorg). Wayland work fine. 

When using "startx", system seem to go into a kernel panic, seemly caused by Nouveau.

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

4.3.3-300.fc23

How reproducible:

100%


Steps to Reproduce:

1. Boot with said kernel
2. Log using any Xorg based session

Actual results:

System will hang (with something looking like a kernel panic when using command-line).

Expected results:

Gnome desktop show.

Additional info:

I'm on an Optimus enabled laptop (Core i7-4500U + nVidia GTX 820M)

Comment 1 Josh Boyer 2016-01-15 14:28:58 UTC
Please provide the contents of dmesg and/or a picture of the backtrace on the screen when this happens.

Comment 2 Roman Spirgi 2016-01-15 18:36:27 UTC
Created attachment 1115239 [details]
Screenshot after crash

Same on a Samsung laptop, model 700Z3C, i5 3210M, GT 630M.
Don't know if attachment is of use, screen after sysrq -e

Comment 3 Josh Boyer 2016-01-15 18:59:08 UTC
This is most likely a duplicate of bug 1296820

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

Comment 4 Erwan GEORGET 2016-01-20 22:10:02 UTC
Same error as Roman Spirgi.