Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17022 - GUI freezing every fiew minutes.
Attached to Project:
Arch Linux
Opened by Viacheslav Chumushuk (voice) - Thursday, 05 November 2009, 18:14 GMT
Last edited by Ionut Biru (wonder) - Saturday, 07 November 2009, 16:49 GMT
Opened by Viacheslav Chumushuk (voice) - Thursday, 05 November 2009, 18:14 GMT
Last edited by Ionut Biru (wonder) - Saturday, 07 November 2009, 16:49 GMT
|
DetailsDescription:
Now I have fresh updated system, and after update (I think 2 days ago) I have next bug: * every fiew minutes my GUI interface stops, and mouse and keyboard freeze, and after fiew (near 5) seconds it backs to normal work. * all text at widgets, firefox (but not in terminal, urxvt) damaged. I don't really know how to describe it... I think it is problem in video drivers or kernel. I was trying radeonhd and radeon drivers and result the same. Here is my video card (HP 6820s laptop): 01:00.0 VGA compatible controller: ATI Technologies Inc RV516 [Mobility Radeon X1350] Kernel: Linux laptop 2.6.31-ARCH #1 SMP PREEMPT Fri Oct 23 11:12:58 CEST 2009 i686 Intel(R) Pentium(R) Dual CPU T2410 @ 2.00GHz GenuineIntel GNU/Linux Here is what I have in my /var/log/errors.log: Nov 5 19:46:30 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f68b23c0:0x00006C8C) 523ms timeout Nov 5 19:46:30 laptop kernel: [drm:radeon_fence_wait] *ERROR* last signaled fence(0x00006C8C) Nov 5 19:51:13 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f68b2f00:0x0000759A) 506ms timeout going to reset GPU Nov 5 19:51:13 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f68b2f00:0x0000759A) 516ms timeout Nov 5 19:51:13 laptop kernel: [drm:radeon_fence_wait] *ERROR* last signaled fence(0x0000759A) Nov 5 19:51:13 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f68b25a0:0x0000759B) 516ms timeout going to reset GPU Nov 5 19:51:13 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f68b25a0:0x0000759B) 526ms timeout Nov 5 19:51:13 laptop kernel: [drm:radeon_fence_wait] *ERROR* last signaled fence(0x0000759B) Nov 5 19:54:58 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6ab9760:0x00007EA9) 1053ms timeout going to reset GPU Nov 5 19:54:58 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6ab9760:0x00007EA9) 1066ms timeout Nov 5 19:54:58 laptop kernel: [drm:radeon_fence_wait] *ERROR* last signaled fence(0x00007EA9) Nov 5 19:54:58 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6ab9000:0x00007EAA) 926ms timeout going to reset GPU Nov 5 19:54:58 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6ab9000:0x00007EAA) 940ms timeout Nov 5 19:54:58 laptop kernel: [drm:radeon_fence_wait] *ERROR* last signaled fence(0x00007EAA) Nov 5 20:01:05 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6813b20:0x000087B8) 10726ms timeout going to reset GPU Nov 5 20:01:05 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6813b20:0x000087B8) 10736ms timeout Nov 5 20:01:05 laptop kernel: [drm:radeon_fence_wait] *ERROR* last signaled fence(0x000087B8) Nov 5 20:01:05 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6813e20:0x000087B9) 10623ms timeout going to reset GPU Nov 5 20:01:05 laptop kernel: [drm:radeon_fence_wait] *ERROR* fence(f6813e20:0x000087B9) 10633ms timeout Nov 5 20:01:05 laptop kernel: [drm:radeon_fence_wait] *ERROR* last signaled fence(0x000087B9) |
This task depends upon
[2009-11-07 14:45] upgraded xorg-server (1.7.1-1 -> 1.7.1.901-1)
Sorry, but after rebooting I lost my xorg log, but when I had this bug I haven't nothing interesting in xorg log,
only in errors.log, which I posted above.
So I think the problem is solved. Strange that only I had this bug...
Thanks for you replies, guys.