[arch-general] xf86-video-intel-2.20.5
Jameson
imntreal at gmail.com
Tue Aug 28 12:44:12 EDT 2012
On Tue, Aug 28, 2012 at 12:37 PM, Andre Goree <andre at drenet.info> wrote:
> On 08/27/2012 01:20 PM, Andre Goree wrote:
>> On 08/27/2012 01:03 PM, Jameson wrote:
>>> Updating xf86-video-intel to 2.20.5 today results in my DRM driver
>>> hanging when I try to use compiz. Has anyone else seen this, or am I
>>> just lucky with my hardware configuration? Does anyone know of
>>> something new that got turned on by default in this version that could
>>> result in this:
>>>
>>> Aug 27 12:39:09 localhost kernel: [ 4.733046] [drm] Initialized
>>> i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
>>> Aug 27 12:42:27 localhost kernel: [ 219.129987]
>>> [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed...
>>> render ring idle
>>> Aug 27 12:42:37 localhost kernel: [ 220.723319]
>>> [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed...
>>> render ring idle
>>> Aug 27 12:42:37 localhost kernel: [ 222.229987]
>>> [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed...
>>> render ring idle
>>> Aug 27 12:42:37 localhost kernel: [ 222.230044]
>>> [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
>>> Aug 27 12:42:37 localhost kernel: [ 222.230087] [drm] capturing error
>>> event; look for more information in /debug/dri/0/i915_error_state
>>>
>>> I'll be happy to post more information, and/or a bug later if that
>>> will be helpful. For now, I need to get caught back up at work.
>>>
>>> Thanks,
>>> =-Jameson
>>>
>>
>>
>> Interesting (glad I didn't proceed with the update). Given that I'm at
>> work right now, I'll hold off on my update/reboot until later this
>> evening, and let you know if I get the same error.
>>
>> I'm not actually using Compiz, but rather Kwin...though since it's a
>> kernel-level issue, I guess we'll see how much that matters.
>>
>>
>
> I indeed ended up having an issue with Kwin that actually was causing
> KDE to crash. After downgrading to
> xf86-video-intel-2.20.4-1-x86_64.pkg.tar.xz, the issue ceased.
I opened a bug report. https://bugs.archlinux.org/task/31317
More information about the arch-general
mailing list