Bug 21476

Created attachment 25258 [details]
Xorg.0.log

Xorg.0.log from a run outside of gdb

Created attachment 25259 [details]
Xorg.0.log

wrong mimetype :(

also, this is the dmesg of a zombie X, it happen but not all the times, and never in a gdb run.


[ 8071.706720] [drm] DAC-6: set mode 1152x864 18
[ 8092.659194] INFO: RCU detected CPU 0 stall (t=4297305094/3000 jiffies)
[ 8092.659200] Pid: 12542, comm: X Not tainted 2.6.30-rc4-debug #7
[ 8092.659200] Call Trace:
[ 8092.659200]  <IRQ>  [<ffffffff802c1891>] __rcu_pending+0x1b1/0x300
[ 8092.659200]  [<ffffffff8020c296>] ? ftrace_call+0x5/0x2b
[ 8092.659200]  [<ffffffff802c1a1b>] rcu_pending+0x3b/0x90
[ 8092.659200]  [<ffffffff802676b0>] ? run_local_timers+0x30/0x50
[ 8092.659200]  [<ffffffff80267722>] update_process_times+0x52/0xa0
[ 8092.659200]  [<ffffffff8028985d>] ? tick_do_update_jiffies64+0x8d/0xf0
[ 8092.659200]  [<ffffffff8028995a>] tick_nohz_handler+0x9a/0x140
[ 8092.659200]  [<ffffffff80761cc0>] smp_apic_timer_interrupt+0x80/0xc6
[ 8092.659200]  [<ffffffff8020d193>] apic_timer_interrupt+0x13/0x20
[ 8092.659200]  <EOI>  [<ffffffff807595e3>] ? __mutex_lock_common+0x343/0x450
[ 8092.659200]  [<ffffffffa00c2b75>] ? drm_vm_shm_close+0xc5/0x2a0 [drm]
[ 8092.659200]  [<ffffffffa00c2b37>] ? drm_vm_shm_close+0x87/0x2a0 [drm]
[ 8092.659200]  [<ffffffff8030fc56>] ? remove_vma+0x56/0xc0
[ 8092.659200]  [<ffffffff8030fdf0>] ? exit_mmap+0x130/0x180
[ 8092.659200]  [<ffffffff8036da92>] ? exit_aio+0x12/0x100
[ 8092.659200]  [<ffffffff80256737>] ? mmput+0x87/0x100
[ 8092.659200]  [<ffffffff8025bec5>] ? exit_mm+0x125/0x180
[ 8092.659200]  [<ffffffff8025ddf5>] ? do_exit+0x135/0x820
[ 8092.659200]  [<ffffffff8025e53c>] ? do_group_exit+0x5c/0xe0
[ 8092.659200]  [<ffffffff8026d2fa>] ? get_signal_to_deliver+0x2fa/0x460
[ 8092.659200]  [<ffffffff8075b892>] ? _spin_unlock_irqrestore+0x52/0x90
[ 8092.659200]  [<ffffffff8020c296>] ? ftrace_call+0x5/0x2b
[ 8092.659200]  [<ffffffff8020b80a>] ? do_notify_resume+0xea/0x840
[ 8092.659200]  [<ffffffff8075b81f>] ? _spin_unlock_irq+0x3f/0x60
[ 8092.659200]  [<ffffffff8020c5cc>] ? sysret_check+0x27/0x62
[ 8092.659200]  [<ffffffff8028fc52>] ? trace_hardirqs_on_caller+0x32/0x200
[ 8092.659200]  [<ffffffff8020c296>] ? ftrace_call+0x5/0x2b
[ 8092.659200]  [<ffffffff8028fc52>] ? trace_hardirqs_on_caller+0x32/0x200
[ 8092.659200]  [<ffffffff8020c698>] ? sysret_signal+0x7c/0xcb

kernel, and all x11 parts except xorg-server have been updated to the lastest git version.

Created attachment 25379 [details]
intel_reg_dumper-dumps.zip

today trying with xorg-server from git, the attached file contain the dump of intel_reg_dumper tool in various point in time.

(gdb) bt
#0  drm_intel_bo_alloc (bufmgr=0x0, name=0x7f71fdb126c1 "HW cursors", size=40960, alignment=1048576) at intel_bufmgr.c:51
#1  0x00007f71fdad1ee0 in i830_allocate_memory_bo () from /usr/lib64/xorg/modules/drivers/intel_drv.so
#2  0x00007f71fdad23f9 in i830_allocate_memory () from /usr/lib64/xorg/modules/drivers/intel_drv.so
#3  0x00007f71fdad3448 in i830_allocate_cursor_buffers () from /usr/lib64/xorg/modules/drivers/intel_drv.so
#4  0x00007f71fdad3876 in i830_allocate_2d_memory () from /usr/lib64/xorg/modules/drivers/intel_drv.so
#5  0x00007f71fdac81ef in i830_try_memory_allocation () from /usr/lib64/xorg/modules/drivers/intel_drv.so
#6  0x00007f71fdac83da in i830_memory_init () from /usr/lib64/xorg/modules/drivers/intel_drv.so
#7  0x00007f71fdac8f60 in I830ScreenInit () from /usr/lib64/xorg/modules/drivers/intel_drv.so
#8  0x0000000000430f5b in AddScreen (pfnInit=0x7f71fdac8b2a <I830ScreenInit>, argc=1, argv=0x7fff0a1a5d18) at dispatch.c:4032
#9  0x0000000000463874 in InitOutput (pScreenInfo=0x7b1820, argc=1, argv=0x7fff0a1a5d18) at xf86Init.c:1233
#10 0x00000000004291b2 in main (argc=1, argv=0x7fff0a1a5d18, envp=<value optimized out>) at main.c:202
(gdb) list
46
47      drm_intel_bo *
48      drm_intel_bo_alloc(drm_intel_bufmgr *bufmgr, const char *name,
49                         unsigned long size, unsigned int alignment)
50      {
51         return bufmgr->bo_alloc(bufmgr, name, size, alignment);
52      }
53
54      drm_intel_bo *
55      drm_intel_bo_alloc_for_render(drm_intel_bufmgr *bufmgr, const char *name,
(gdb)

Nothing GL related here, you're just triggering the nasty path of trying to deinitialize the driver and reinitialize it after the last client closes.  You could do it with any X app and a bare X server.

I'm working on getting this fixed, but as always our init/close paths are rather tricky.

If you're just trying to do testing, then I'd recommend keeping another application open when running glxgears or test applications.

you have my simpathy awfull stuff to debug, just in case ...

I do own 5 pc with the configuration show in this same bug, and some nightly time to spare, if some debug/testing is needed feel free to contact me francesco<>pnpitalia<>it

Adjusting severity: crashes & hangs should be marked critical.

*** This bug has been marked as a duplicate of bug 20516 ***