Nouveau - Jan 2016 - [Bug 93932] New: Xorg/Nouveau crashes with Segmentation fault when setting i7-Skylake iGPU as primary grapics device in BIOS

https://bugs.freedesktop.org/show_bug.cgi?id=93932

            Bug ID: 93932
           Summary: Xorg/Nouveau crashes with Segmentation fault when
                    setting i7-Skylake iGPU as primary grapics device in
                    BIOS
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: m.prechtl97 at googlemail.com
        QA Contact: xorg-team at lists.x.org

Created attachment 121404
  --> https://bugs.freedesktop.org/attachment.cgi?id=121404&action=edit
Apport crash dump

Xorg/Nouveau crashes with Segmentation fault when setting i7-Skylake iGPU as
primary grapics device in BIOS

Hardware:
CPU: i7-6700k (Intel HD Graphics 530)
MB: Asus H110M2 D3
GPU: NVIDIA GeForce GTX 750ti

How to reproduce:
- Install fresh Ubuntu Gnome 15.10 (Side note, graphic issues with standard
drivers, goes away with NVIDIA drivers so no big problem there)
- Install Kernel 4.3.4
- Install Intel drivers / compile and install latest Intel drivers
- Reboot
- iGPU isn't recognized as VGA compatible card
- Reboot and set primary graphics device to 'CPU Graphics' in BIOS
--> iGPU now is recognized
--> Xorg lives for approx. 1-2 seconds and then crashes

Xorg Version: X.Org X Server 1.17.2

Excerpt from error log:

[     9.322] (EE) 
[     9.322] (EE) Backtrace:
[     9.322] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x56165770c68e]
[     9.322] (EE) 1: /usr/bin/X (0x561657558000+0x1b89f9) [0x5616577109f9]
[     9.323] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f40fc83e000+0x352f0)
[0x7f40fc8732f0]
[     9.323] (EE) 3: /usr/lib/xorg/modules/drivers/nouveau_drv.so
(0x7f40f87bd000+0xd74f) [0x7f40f87ca74f]
[     9.323] (EE) 4: /usr/bin/X (PixmapShareToSlave+0x8e) [0x5616575cc94e]
[     9.323] (EE) 5: /usr/bin/X (RRCrtcSet+0x670) [0x561657671870]
[     9.323] (EE) 6: /usr/bin/X (ProcRRSetCrtcConfig+0x38b) [0x56165767289b]
[     9.323] (EE) 7: /usr/bin/X (0x561657558000+0x5818f) [0x5616575b018f]
[     9.323] (EE) 8: /usr/bin/X (0x561657558000+0x5c34b) [0x5616575b434b]
[     9.323] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
[0x7f40fc85ea40]
[     9.323] (EE) 10: /usr/bin/X (_start+0x29) [0x56165759e6c9]
[     9.323] (EE) 
[     9.323] (EE) Segmentation fault at address 0x8
[     9.323] (EE) 
Fatal server error:
[     9.323] (EE) Caught signal 11 (Segmentation fault). Server aborting
[     9.323] (EE) 
[     9.323] (EE)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20160130/0c329587/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=93932

Christopher M. Penalver <christopher.m.penalver at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Christopher M. Penalver <christopher.m.penalver at
gmail.com> ---
Matthias, thank you for reporting this and helping make Ubuntu better. However,
your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your
crash that can be dealt with by the automatic retracer. First, execute at a
terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get
-y
dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in
/etc/default/apport and restart. Now reproduce the crash, then open a terminal,
navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default,
this sends the crash to the Ubuntu Error Tracker infrastructure, which is
different than Launchpad. For more on this, please see
https://wiki.ubuntu.com/ErrorTracker .  

However, if after doing this you would still like to have a crash report posted
to Launchpad, for example to ease triage and add others to your report, one
would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above will deal
with this issue more efficiently.

Also, please do not attach your crash report manually to this report and reopen
it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160224/938cb184/attachment.html>