I'm cloning off my incident since it's on a different RHEL release. +++ This bug was initially created as a clone of Bug #210584 +++ Description of problem: I've hit the same symptoms several times. Another co-worker has hit the same problem and I was able to grab the following data from his workstation. strace output: --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = 28144 --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = 28144 --- SIGALRM (Alarm clock) @ 0 (0) --- gdb backtrace: (gdb) bt #0 0x00002aaaac047c49 in NVSync () from /usr/lib64/xorg/modules/drivers/nv_drv.so #1 0x00002aaaae140bb6 in XAAGetFallbackOps () from /usr/lib64/xorg/modules/libxaa.so #2 0x0000000000512b04 in miInitializeCompositeWrapper () #3 0x000000000050e683 in DamageDamageRegion () #4 0x00000000004480ae in ProcCopyArea () #5 0x0000000000449c9a in Dispatch () #6 0x00000000004325d5 in main () xorg.conf: # Xorg configuration created by system-config-display Section "ServerLayout" Identifier "single head configuration" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "Device" Identifier "Videocard0" Driver "nv" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection -- Additional comment from nstraz on 2007-07-10 16:47 EST -- I should also add that we've hit this running on RHEL 5.0. xorg-x11-server-Xorg-1.1.1-48.2.el5 xorg-x11-drv-nv-1.2.0-4.fc6
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach all X server log files (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 159350 [details] /var/log/Xorg.0.log.old from affected host. Here is the log from the X server which I had to kill off this morning.
Did you try to run the server without any configuration log? Could you send us log files when it crashes?
No, I haven't had a chance to do that yet. We haven't found a reliable trigger for the bug and this is affecting our primary workstations.
Oh well. Please, try to reproduce and send us the required information. Unless you will provide this information in a month, I will close it as hard to reproduce and INSUFFICIENT_DATA or something.
What information are you looking for? I attached the logs from an incident of this bug. The logs don't provide anything useful. I included strace output and a stack trace from gdb. Is there a debugging option I can turn on so the Xorg logs are more useful? Should I run strace or ltrace on the X server until the bug is triggered? I don't see how running X w/o a config file and supplying the logs which don't report anything is more useful information.
(In reply to comment #3) > Did you try to run the server without any configuration log? Could you send us > log files when it crashes? The server does not crash. It gets stuck in a SIGALRM loop and I have to ssh into the box and kill it.
Here is another backtrace from a system stuck in the SIGALRM loop. #0 0x00002aaaac0474fc in NVDmaWait () from /usr/lib64/xorg/modules/drivers/nv_drv.so #1 0x00002aaaac04856a in NVSync () from /usr/lib64/xorg/modules/drivers/nv_drv.so #2 0x00002aaaae167275 in XAAWriteBitmapScanlineColorExpandLSBFirst () from /usr/lib64/xorg/modules/libxaa.so #3 0x00002aaaae146987 in XAANonTEGlyphRenderer () from /usr/lib64/xorg/modules/libxaa.so #4 0x00002aaaae147692 in XAAImageText8NonTEColorExpansion () from /usr/lib64/xorg/modules/libxaa.so #5 0x000000000051194b in miInitializeCompositeWrapper () #6 0x000000000050f9a2 in DamageDamageRegion () #7 0x000000000044d5d3 in doImageText () #8 0x000000000044d76b in ImageText () #9 0x00000000004471f7 in ProcImageText8 () #10 0x0000000000449c9a in Dispatch () #11 0x00000000004325d5 in main ()
Yes, sure, I understand that the server didn't crash, but still the log file could contain a wealth of information which could be helpful for us to resolve this problem (like for example exact details of your configuration), so if you could please send us the /var/log/Xorg.*.log files attached to this bug as separated uncompressed attachments, it would be very helpful, regardless of how Xorg was quited/killed/whatever.
Please see the original comment and the already attached log file.
Sorry, silly me -- yes, sure, this is correct.
*** This bug has been marked as a duplicate of 219377 ***