Bug 680415

Created attachment 480994 [details]
dmesg

Created attachment 480995 [details]
Xorg.0.log

Created attachment 480996 [details]
detailed backtrace

(In reply to comment #0)
> it happened after several hours of desktop usage

I should amend this. The log clearly shows the freeze happened after less than an hour of uptime. I forgot that I had rebooted not so long ago, but the reboot was not induced by any troubles.

Backtrace:
[  2207.459] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a120f]
[  2207.459] 1: /usr/bin/Xorg (mieqEnqueue+0x1e9) [0x4a0729]
[  2207.459] 2: /usr/bin/Xorg (xf86PostMotionEventM+0x93) [0x47d9b3]
[  2207.459] 3: /usr/bin/Xorg (xf86PostMotionEventP+0x52) [0x47dad2]
[  2207.459] 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f0d5c1de000+0x499e) [0x7f0d5c1e299e]
[  2207.459] 5: /usr/bin/Xorg (0x400000+0x6b1a8) [0x46b1a8]
[  2207.459] 6: /usr/bin/Xorg (0x400000+0x117ab0) [0x517ab0]
[  2207.459] 7: /lib64/libc.so.6 (0x300ee00000+0x36300) [0x300ee36300]
[  2207.459] 8: /lib64/libc.so.6 (ioctl+0x7) [0x300eed8b17]
[  2207.459] 9: /usr/lib64/libdrm.so.2 (drmIoctl+0x28) [0x3026603338]
[  2207.459] 10: /usr/lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x30266054ab]
[  2207.459] 11: /usr/lib64/libdrm_nouveau.so.1 (0x7f0d5ed20000+0x2ede) [0x7f0d5ed22ede]
[  2207.459] 12: /usr/lib64/libdrm_nouveau.so.1 (nouveau_bo_map_range+0x111) [0x7f0d5ed234d1]
[  2207.459] 13: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7f0d5ef43000+0x5dde) [0x7f0d5ef48dde]
[  2207.459] 14: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x621e) [0x7f0d5e2dd21e]
[  2207.459] 15: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x89fe) [0x7f0d5e2df9fe]
[  2207.459] 16: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0xf92a) [0x7f0d5e2e692a]
[  2207.459] 17: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x104dc) [0x7f0d5e2e74dc]
[  2207.459] 18: /usr/bin/Xorg (0x400000+0xd73f2) [0x4d73f2]
[  2207.459] 19: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0xd847) [0x7f0d5e2e4847]
[  2207.460] 20: /usr/bin/Xorg (0x400000+0xd75c8) [0x4d75c8]
[  2207.460] 21: /usr/bin/Xorg (0x400000+0xd3b2b) [0x4d3b2b]
[  2207.460] 22: /usr/bin/Xorg (0x400000+0x2e6a1) [0x42e6a1]
[  2207.460] 23: /usr/bin/Xorg (0x400000+0x2292a) [0x42292a]
[  2207.460] 24: /lib64/libc.so.6 (__libc_start_main+0xed) [0x300ee212fd]
[  2207.460] 25: /usr/bin/Xorg (0x400000+0x22c11) [0x422c11]

*** Bug 704434 has been marked as a duplicate of this bug. ***

Backtrace in bug 679576 looks kind of similar to this one, but not completely, moreover that other one is quite incomplete.

This bug not appear a the 1024x768  resolution diplay.I propose to solve this bug
a the 1280x1024 display resolution.

Created attachment 499028 [details]
Propose for close Bug 680415

path of this file /usr/share/gnome-shell/shaders and make backup first.

Created attachment 499084 [details]
For testing

Created attachment 499090 [details]
This work more better

This it.

Created attachment 499155 [details]
May be the last

I am unable to reproduce the bug. I haven't had a crash for weeks.

I tried using the dim-window.glsl from marian. FWIW, gnome-shell worked just as well as before.

I don't know much about GLSL.
marian, could you please explain how your proposed dim-window.glsl is supposed to solve the bug?

For more informations http://en.wikipedia.org/wiki/GLSL and study GLSL Language
Specification ,Version 1.20  and more.

Trust me man original configuration don't work to me.

Especial try to run gnome-terminal on full screen  and acces Help->About for
two tree times and tel us hapen.

The modal dialog always appears fine, there's no crash. But I noticed this line is printed to .xsession-errors:
      JS LOG: Error invoking Clutter.compile: GLSL shaders not supported

If I understand the GLSL code correctly, when a modal dialog pops up, the main window is supposed to darken a little bit. This does not happen here.
As long as there's no crash, I'm happy with that.

Maybe bug 704434 is not a duplicate after all (it's a different NV HW).

kernel-2.6.38.6-26.rc1.fc15.x86_64
xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64

At me dialog pops produce crash on xorg.log because supose to overloading the buffer.
Add support for GLSL shaders and continue testing.With new configurations dialog pops run roundly and not produce overloading on xserver because run optimized.
Sintax use on configuration is open gl 2.0 version.
xorg-x11-drv-nouveau-1:0.0.16-24.20110324git8378443.fc15(x86_64) on my xserver.
Installed Packages
Name        : xorg-x11-drv-nouveau
Arch        : x86_64
Epoch       : 1
Version     : 0.0.16
Release     : 24.20110324git8378443.fc15
Size        : 255 k
Repo        : installed
From repo   : koji-override-0
Summary     : Xorg X11 nouveau video driver for NVIDIA graphics chipsets
URL         : http://www.x.org
License     : MIT
Description : X.Org X11 nouveau video driver.

(In reply to comment #17)
> The modal dialog always appears fine, there's no crash. But I noticed this line
> is printed to .xsession-errors:
>       JS LOG: Error invoking Clutter.compile: GLSL shaders not supported

I found why GLSL is not working on my system. It's a bug in the mesa nv50 driver.

With mesa-dri-drivers-7.11-0.9.20110509.0.fc15.x86_64:

$ glxinfo |grep -e OpenGL -e shad
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV96
OpenGL version string: 1.3 Mesa 7.11-devel
OpenGL extensions:
    GL_ARB_fragment_program, GL_ARB_fragment_shader, GL_ARB_shader_objects, 
    GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ATI_draw_buffers, 
    GL_ARB_occlusion_query2, GL_ARB_point_sprite, GL_ARB_shading_language_100, 
    GL_EXT_separate_shader_objects, GL_EXT_vertex_array_bgra,

The "1.3" OpenGL version struck me as odd. I found this upstream fix:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=d6b248652a7b2c9c3e83a5f2188ce0ac77176bf0

After applying it to the mesa SRPM and a rebuild, I am now getting more features:

OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV96
OpenGL version string: 2.1 Mesa 7.11-devel
OpenGL shading language version string: 1.20
OpenGL extensions:
    GL_ARB_shadow, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
    GL_ARB_draw_buffers, GL_ARB_fragment_program, GL_ARB_fragment_shader, 
    GL_ARB_shader_objects, GL_ARB_vertex_program, GL_ARB_vertex_shader, 
    GL_ATI_draw_buffers, GL_ATI_texture_env_combine3, GL_EXT_shadow_funcs, 
    GL_ARB_depth_clamp, GL_ARB_fragment_program_shadow, 
    GL_ARB_shading_language_100, GL_ARB_sync, GL_ARB_texture_non_power_of_two, 
    GL_ARB_vertex_array_bgra, GL_EXT_separate_shader_objects, 

I am now getting the dimming effect when popping up a modal dialog.
Still no crash observed.

On my glxinfo |grep -e OpenGL -e shad
nvfx_screen_get_param:88 -  Warning: unknown PIPE_CAP 36
nvfx_screen_get_param:88 -  Warning: unknown PIPE_CAP 45
nvfx_screen_get_param:88 -  Warning: unknown PIPE_CAP 43
nvfx_screen_get_param:88 -  Warning: unknown PIPE_CAP 44
nvfx_screen_get_param:88 -  Warning: unknown PIPE_CAP 48
nvfx_screen_get_param:88 -  Warning: unknown PIPE_CAP 47
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV46
OpenGL version string: 2.1 Mesa 7.11-devel
OpenGL shading language version string: 1.20
OpenGL extensions:
    GL_ARB_shadow, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
    GL_ARB_fragment_program, GL_ARB_fragment_shader, GL_ARB_shader_objects, 
    GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ATI_draw_buffers, 
    GL_ATI_texture_env_combine3, GL_EXT_shadow_funcs, GL_EXT_stencil_wrap, 
    GL_MESA_pack_invert, GL_ARB_fragment_program_shadow, 
    GL_ARB_shading_language_100, GL_ARB_sync, GL_ARB_texture_non_power_of_two, 
    GL_EXT_separate_shader_objects, GL_EXT_texture_swizzle, 
May be new bug must be created.

(In reply to comment #2)
> Created attachment 480995 [details]
> Xorg.0.log

[  2207.459] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a120f]
[  2207.459] 1: /usr/bin/Xorg (mieqEnqueue+0x1e9) [0x4a0729]
[  2207.459] 2: /usr/bin/Xorg (xf86PostMotionEventM+0x93) [0x47d9b3]
[  2207.459] 3: /usr/bin/Xorg (xf86PostMotionEventP+0x52) [0x47dad2]
[  2207.459] 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f0d5c1de000+0x499e) [0x7f0d5c1e299e]
[  2207.459] 5: /usr/bin/Xorg (0x400000+0x6b1a8) [0x46b1a8]
[  2207.459] 6: /usr/bin/Xorg (0x400000+0x117ab0) [0x517ab0]
[  2207.459] 7: /lib64/libc.so.6 (0x300ee00000+0x36300) [0x300ee36300]
[  2207.459] 8: /lib64/libc.so.6 (ioctl+0x7) [0x300eed8b17]
[  2207.459] 9: /usr/lib64/libdrm.so.2 (drmIoctl+0x28) [0x3026603338]
[  2207.459] 10: /usr/lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x30266054ab]
[  2207.459] 11: /usr/lib64/libdrm_nouveau.so.1 (0x7f0d5ed20000+0x2ede) [0x7f0d5ed22ede]
[  2207.459] 12: /usr/lib64/libdrm_nouveau.so.1 (nouveau_bo_map_range+0x111) [0x7f0d5ed234d1]
[  2207.459] 13: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7f0d5ef43000+0x5dde) [0x7f0d5ef48dde]
[  2207.459] 14: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x621e) [0x7f0d5e2dd21e]
[  2207.459] 15: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x89fe) [0x7f0d5e2df9fe]
[  2207.459] 16: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0xf92a) [0x7f0d5e2e692a]
[  2207.459] 17: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x104dc) [0x7f0d5e2e74dc]
[  2207.459] 18: /usr/bin/Xorg (0x400000+0xd73f2) [0x4d73f2]
[  2207.459] 19: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0xd847) [0x7f0d5e2e4847]
[  2207.460] 20: /usr/bin/Xorg (0x400000+0xd75c8) [0x4d75c8]
[  2207.460] 21: /usr/bin/Xorg (0x400000+0xd3b2b) [0x4d3b2b]
[  2207.460] 22: /usr/bin/Xorg (0x400000+0x2e6a1) [0x42e6a1]
[  2207.460] 23: /usr/bin/Xorg (0x400000+0x2292a) [0x42292a]
[  2207.460] 24: /lib64/libc.so.6 (__libc_start_main+0xed) [0x300ee212fd]
[  2207.460] 25: /usr/bin/Xorg (0x400000+0x22c11) [0x422c11]

which is

Frame 2: /usr/bin/Xorg (xf86PostMotionEventM+0x93) [0x47d9b3]
/usr/src/debug/xorg-server-20101201/hw/xfree86/common/xf86Xinput.c:1049
xf86PostMotionEventM
Frame 3: /usr/bin/Xorg (xf86PostMotionEventP+0x52) [0x47dad2]
/usr/src/debug/xorg-server-20101201/hw/xfree86/common/xf86Xinput.c:1001
xf86PostMotionEventP
Frame 5: /usr/bin/Xorg (0x400000+0x6b1a8) [0x46b1a8]
/usr/src/debug/xorg-server-20101201/hw/xfree86/common/xf86Events.c:300
xf86SigioReadInput
Frame 6: /usr/bin/Xorg (0x400000+0x117ab0) [0x517ab0]
/usr/src/debug/xorg-server-20101201/hw/xfree86/os-support/linux/../shared/sigio.c:106
xf86SIGIO
Frame 14: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x621e) [0x7f0d5e2dd21e]
/usr/src/debug/xorg-server-20101201/exa/exa_migration_classic.c:220
exaCopyDirty
Frame 15: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x89fe) [0x7f0d5e2df9fe]
/usr/src/debug/xorg-server-20101201/exa/exa_migration_mixed.c:115
exaDoMigration_mixed
Frame 16: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0xf92a) [0x7f0d5e2e692a]
/usr/src/debug/xorg-server-20101201/exa/exa_render.c:737
exaTryDriverComposite
Frame 17: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0x104dc) [0x7f0d5e2e74dc]
/usr/src/debug/xorg-server-20101201/exa/exa_render.c:1035
exaComposite
Frame 18: /usr/bin/Xorg (0x400000+0xd73f2) [0x4d73f2]
/usr/src/debug/xorg-server-20101201/miext/damage/damage.c:625
damageComposite
Frame 19: /usr/lib64/xorg/modules/libexa.so (0x7f0d5e2d7000+0xd847) [0x7f0d5e2e4847]
/usr/src/debug/xorg-server-20101201/exa/exa_glyphs.c:860
exaGlyphs
Frame 20: /usr/bin/Xorg (0x400000+0xd75c8) [0x4d75c8]
/usr/src/debug/xorg-server-20101201/miext/damage/damage.c:692
damageGlyphs
Frame 21: /usr/bin/Xorg (0x400000+0xd3b2b) [0x4d3b2b]
/usr/src/debug/xorg-server-20101201/render/render.c:1445
ProcRenderCompositeGlyphs
Frame 22: /usr/bin/Xorg (0x400000+0x2e6a1) [0x42e6a1]
/usr/src/debug/xorg-server-20101201/dix/dispatch.c:431
Dispatch
Frame 23: /usr/bin/Xorg (0x400000+0x2292a) [0x42292a]
/usr/src/debug/xorg-server-20101201/dix/main.c:289
main

I am still seing the X server hang with this hardware in Fedora 17.
Clicking on a www link in Thunderbird seems to be a good reproducer. Maybe the graphical effect that Firefox shows when adding a new tab as a response to the click triggers it.

kernel-3.3.7-1.fc17.x86_64
xorg-x11-drv-nouveau-0.0.16-35.20120306gitf5d1cd2.fc17.x86_64

[michich@dhcp-29-224 ~]$ sudo gstack 1074
#0  0x0000003b9b4ea617 in ioctl () from /lib64/libc.so.6
#1  0x0000003ba1c03548 in drmIoctl () from /lib64/libdrm.so.2
#2  0x0000003ba1c0577b in drmCommandWrite () from /lib64/libdrm.so.2
#3  0x00007f87157e1085 in ?? () from /lib64/libdrm_nouveau.so.1
#4  0x00007f87157e16b3 in nouveau_bo_map_range () from /lib64/libdrm_nouveau.so.1
#5  0x00007f8715a0ccc3 in nouveau_dri2_finish_swap (draw=0x15031e0, frame=0, tv_sec=0, tv_usec=0, s=0x17a47d0) at nouveau_dri2.c:311
#6  0x00007f8715a0d279 in nouveau_dri2_schedule_swap (client=0x1254fe0, draw=0x15031e0, dst=0x1afbdd0, src=0x1559dd0, target_msc=0x7fff153c6df8, divisor=0, remainder=0, func=0x7f8715c3b700 <DRI2SwapEvent>, data=0x15031e0) at nouveau_dri2.c:479
#7  0x00007f8715c3ac37 in DRI2SwapBuffers (client=client@entry=0x1254fe0, pDraw=0x15031e0, target_msc=0, divisor=0, remainder=<optimized out>, swap_target=swap_target@entry=0x7fff153c6df8, func=func@entry=0x7f8715c3b700 <DRI2SwapEvent>, data=0x15031e0) at dri2.c:930
#8  0x00007f8715c3bf42 in ProcDRI2SwapBuffers (client=0x1254fe0) at dri2ext.c:403
#9  ProcDRI2Dispatch (client=0x1254fe0) at dri2ext.c:569
#10 0x000000000043439a in Dispatch () at dispatch.c:439
#11 0x00000000004233e5 in main (argc=13, argv=0x7fff153c6ff8, envp=<optimized out>) at main.c:287


[michich@dhcp-29-224 ~]$ sudo cat /proc/1074/stack
[<ffffffffa00922e6>] __nouveau_fence_wait+0xb6/0x110 [nouveau]
[<ffffffffa006104a>] ttm_bo_wait+0xaa/0x1b0 [ttm]
[<ffffffffa0094bc6>] nouveau_gem_ioctl_cpu_prep+0x66/0xc0 [nouveau]
[<ffffffffa0015494>] drm_ioctl+0x424/0x520 [drm]
[<ffffffff81190109>] do_vfs_ioctl+0x99/0x580
[<ffffffff81190689>] sys_ioctl+0x99/0xa0
[<ffffffff815f3f29>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.