[Bug 98690] New: [i915] System freeze when starting X using kernel 4.9-rc4

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 98690
           Summary: [i915] System freeze when starting X using kernel
                    4.9-rc4
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: freedesktop-bugs at PaulSD.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 127923
  --> https://bugs.freedesktop.org/attachment.cgi?id=127923&action=edit
Xorg.0.log

Dell 7510 laptop with Intel Xeon E3-1545Mv5 (Iris Pro 580), running Ubuntu
16.04 (stock except for kernel and linux-firmware package - using
linux-firmware 1.161 from Ubuntu 16.10).

The stock Ubuntu 16.04 kernel (4.8.0-22-generic) works fine.

Updating to kernel 4.9-rc4 or drm-next or drm-intel-next or drm-intel-nightly
from http://kernel.ubuntu.com/~kernel-ppa/mainline/ reliably causes Xorg to
hang at start-up, with the following message being printed to Xorg.0.log:
systemd-logind: failed to take device /dev/dri/card0: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.

If I boot to a console then run startx, Xorg prints a few standard messages,
then the console freezes - the screen does not turn black or change video
modes.  CTRL-C, CTRL-ALT-DELETE, and CTRL-ALT-F2 do not respond.  However, ACPI
hot-keys do seem to respond - hitting the power button causes Ubuntu to attempt
to shut down, and the console prints shutdown messages when this happens. 
However, the shutdown process hangs again before it finishes shutting down - it
typically gets stuck when shutting down either the network or rng-tools.

The attached dmesg was produced by running the following script ... the
produced error.bz2 file was empty:
#!/bin/bash
startx &
sleep 10
dmesg > dmesg
cat /sys/class/drm/card0/error | bz2 > error.bz2

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161111/d1750186/attachment.html>