[arch-general] xf86-video-intel-2.20.5
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
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. -- Andre Goree andre@drenet.info
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. For whatever reason, it was causing "X BadWindow" and "Fatal IO" errors, e.g.: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x30000ee X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x30000ee X Error: BadWindow (invalid Window parameter) 3 Major opcode: 18 (X_ChangeProperty) Resource id: 0x30000ee plasma-desktop(3002)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: MNG error 11: Function is invalid at this point; chunk IHDR; subcode 0:0 kopete(3110): No language dictionaries for the language : "en_US" plasma-desktop(3002)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application enigmail.js: Registered components caught error TypeError: Cc['@mozilla.org/mime/pgp-mime-decrypt;1'] is undefinedmimeDecrypt.jsm: MimeDecryptor registration doneplasma-desktop(3002)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 2 (X_ChangeWindowAttributes) Resource id: 0x1e020c7 krdc(3272)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kwin: Fatal IO error: client killed kdeinit4: Fatal IO error: client killed -- Andre Goree andre@drenet.info
On Tue, Aug 28, 2012 at 12:37 PM, Andre Goree <andre@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
I opened a bug report. https://bugs.archlinux.org/task/31317
It seems to be SNA causing the problem. I have swapped over to UXA for the time being, been stable for the like 3 hours. Neil
On Tue, 28 Aug 2012 17:55:46 +0100 Neil Perry <nperry@gmail.com> wrote:
It seems to be SNA causing the problem. I have swapped over to UXA for the time being, been stable for the like 3 hours.
Is the default still UXA mode? --- Joakim
On Tue, Aug 28, 2012 at 12:55 PM, Neil Perry <nperry@gmail.com> wrote:
It seems to be SNA causing the problem. I have swapped over to UXA for the time being, been stable for the like 3 hours.
Yep. UXA is working fine for me, also. =-Jameson
On 08/28/2012 02:43 PM, Jameson wrote:
On Tue, Aug 28, 2012 at 12:55 PM, Neil Perry <nperry@gmail.com> wrote:
It seems to be SNA causing the problem. I have swapped over to UXA for the time being, been stable for the like 3 hours.
Yep. UXA is working fine for me, also.
For what its worth - i still have crashes with UXA just very much less frequent. I logged it here: https://bugs.archlinux.org/task/30921 gene/
On Tue, Aug 28, 2012 at 8:46 PM, Genes MailLists <lists@sapience.com> wrote:
On Tue, Aug 28, 2012 at 12:55 PM, Neil Perry <nperry@gmail.com> wrote:
It seems to be SNA causing the problem. I have swapped over to UXA for
On 08/28/2012 02:43 PM, Jameson wrote: the
time being, been stable for the like 3 hours.
Yep. UXA is working fine for me, also.
For what its worth - i still have crashes with UXA just very much less frequent.
I logged it here: https://bugs.archlinux.org/task/30921
gene/
Works excellent here with intel ironlake and sna
Le lundi 27 août 2012 13:03:16 Jameson a écrit :
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
It's better to open a bug report, with: * dmesg output * Xorg log output * lspci output * list of enabled repos And of course, have you properly upgrade ? (pacman -Syu) ++
participants (7)
-
Andre Goree
-
Brandon Watkins
-
Genes MailLists
-
Jameson
-
Joakim Hernberg
-
Laurent Carlier
-
Neil Perry