[Bug 76514] New: [Xeon E3-1200 v2/3rd Gen] [3.13.6-1-ARCH x86_64] xf86-video-intel 2.99.911 freezes or very slow on startup

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 76514
          Assignee: chris at chris-wilson.co.uk
           Summary: [Xeon E3-1200 v2/3rd Gen] [3.13.6-1-ARCH x86_64]
                    xf86-video-intel 2.99.911 freezes or very slow on
                    startup
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: colinnkeenan at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: Driver/intel
           Product: xorg

Bug description: using xf86-video-intel 2.99.911, X is 10 to 100 times slower
than normal to start, or never starts and displays a black or garbled screen.

Switching to a virtual console is still possible, but sometimes garbled until X
is closed. Even when displaying a black screen, all the components of the
desktop are running as are auto-started applications such as Google Chrome.

If X starts, after taking close to 100 times longer than normal, and it's not
displaying a garbled screen, everything works normally for that session. 

Downgrading to xf86-video-intel 2.99.910 solves all issues.

System environment:
-- chipset: Core i5-3570K / Intel Xeon E3-1200 v2/3rd Gen Core processor
Graphics Controller
-- system architecture: 64-bit
-- xf86-video-intel: 2.99.911
-- xserver: X.Org 1.15.0
-- mesa: 10.1.0_devel.60267-1 (package intel-dri-git in AUR flagged out of date
back on 2013-10-16)
-- libdrm: 2.4.50-1 (package libdrm-git in AUR last updated 2013-04-23)
-- kernel: 3.13.6
-- Linux distribution: Arch
-- Machine or mobo model: GIGABYTE GA-Z77N-WIFI
-- Display connector: HDMI

Reproducing steps:
I tried starting both Xfce and DWM. I tried DWM just because it's minimal. Xfce
was auto-starting a lot of stuff. DWM wasn't auto-starting anything. DWM didn't
work either.

Additional info:
The errors generated are not listed in journalctl because I get the following
journalctl error: 

systemd-journald[131]: Failed to write entry (26 items, 81589132 bytes) despite
vacuuming, ignoring: Argument list too long

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140323/cea165da/attachment.html>