Your message dated Sun, 13 Jul 2014 15:10:47 +0200 with message-id <20140713131047.GA1400@betterave.cristau.org> and subject line Re: Bug#683167: linux-image-3.4-trunk-amd64: Attempting to start X with intel driver hangs system has caused the Debian Bug report #683167, regarding libdrm-intel1: X dies hard on Ivy Bridge GT2 Server graphics to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 683167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683167 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libdrm-intel1: X dies hard on Ivy Bridge GT2 Server graphics
- From: Maik Zumstrull <maik@zumstrull.net>
- Date: Sun, 12 Aug 2012 15:25:14 +0200
- Message-id: <20120812132514.4449.3013.reportbug@antares.zumstrull.net>
Package: libdrm-intel1 Version: 2.4.33-3 Severity: important If X is started with this libdrm on a machine with "Ivy Bridge GT2 Server" Intel graphics, it crashes and leaves the machine in an almost unusable state (network/ssh might remain up). X is certainly completely unusable, as it won't start. Please package a version >= 2.4.34 or backport the patches mentioned in this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=53222 Other related reports: https://bugzilla.redhat.com/show_bug.cgi?id=840180 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683167 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdrm-intel1 depends on: ii libc6 2.13-33 ii libdrm2 2.4.33-3 ii libpciaccess0 0.13.1-2 ii multiarch-support 2.13-33 libdrm-intel1 recommends no packages. libdrm-intel1 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Maik Zumstrull <maik@zumstrull.net>, 683167-done@bugs.debian.org
- Subject: Re: Bug#683167: linux-image-3.4-trunk-amd64: Attempting to start X with intel driver hangs system
- From: Julien Cristau <jcristau@debian.org>
- Date: Sun, 13 Jul 2014 15:10:47 +0200
- Message-id: <20140713131047.GA1400@betterave.cristau.org>
- In-reply-to: <20120729113605.5102.7805.reportbug@antares.zumstrull.net>
- References: <20120729113605.5102.7805.reportbug@antares.zumstrull.net>
Version: 2.4.40-1 On Sun, Jul 29, 2012 at 13:36:05 +0200, Maik Zumstrull wrote: > Package: src > Version: 3.4.4-1~experimental.1 > Severity: important > > This is on an Ivy Bridge Xeon E3 with GPU. I thought it was the X > driver, because i915 KMS works fine for the console, it only crashes > when trying to bring up X. But I pulled in the 2.20.2 driver today and > it still happens. So I now think the problem is in the kernel. > > It's entirely possible this is fixed in 3.5, which I will test as soon > as it hits experimental. > > 3.2 crashes as well, but not as hard as 3.4. With 3.2, X doesn't come > up, but you can switch to a console and reboot. 3.4 needs the reset > button. > Per https://bugs.freedesktop.org/show_bug.cgi?id=53222, marking as fixed in libdrm 2.4.34. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---