Hide Forgot
Created attachment 504216 [details] The image that causes the crash Description of problem: Open the attached image in EOG. X server will crash. (Furthermore, abrt is not able to recover trace information for this crash, and I had to go figure out how to get it myself out of /var/spool/abrt, which is not very helpful for automated reporting of bugs like this.) Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.15.0-3.fc15.x86_64 xorg-x11-server-Xorg-1.10.2-1.fc15.x86_64 kernel: Linux localhost.localdomain 2.6.38.7-30.fc15.x86_64 #1 SMP Fri May 27 05:15:53 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux eog-3.0.1-1.fc15.x86_64 gtk3-3.0.10-1.fc15.x86_64 How reproducible: Every time Steps to Reproduce: 1. Double-click on attached JPEG file Backtrace: #7 <signal handler called> #8 0x0000003cc092d7b1 in __memcpy_ssse3 () from /lib64/libc.so.6 #9 0x00007f67a5b6ba46 in intel_uxa_pixmap_put_image (pixmap=<optimized out>, src=<optimized out>, src_pitch=29528, x=<optimized out>, y=<optimized out>, w=<optimized out>, h=8) at /usr/include/bits/string3.h:52 #10 0x00007f67a5b6d3a6 in intel_uxa_put_image (pixmap=0x3e234b0, x=0, y=0, w=7382, h=<optimized out>, src=0x3ec0d78 "\377\377\377", src_pitch=29528) at intel_uxa.c:806 #11 0x00007f67a5b8161d in uxa_do_put_image (src_stride=29528, bits=0x3ec0d78 "\377\377\377", format=2, h=8, w=7382, y=<optimized out>, x=<optimized out>, depth=<optimized out>, pGC=0x3f0c660, pDrawable=0x3e234b0) at uxa-accel.c:336 #12 uxa_put_image (pDrawable=0x3e234b0, pGC=0x3f0c660, depth=<optimized out>, x=<optimized out>, y=0, w=7382, h=8, leftPad=0, format=2, bits=0x3ec0d78 "\377\377\377") at uxa-accel.c:374 #13 0x00000000004dc199 in ?? ()
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 add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I have no xorg.conf file, but the rest are attached.
Created attachment 504256 [details] Xorg.0.log
Created attachment 504257 [details] dmesg output with drm.debug=0x04
Created attachment 504258 [details] /var/log/messages
hmm... I don't see any crash in the xorg log file. can you please reproduce the crash with the drm.debug=0x04, restart xorg, and attach Xorg.0.log.old or any other recent log file that ends with the crash? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
OK, but how to I prevent gdm from restarting Xorg after a crash on Fedora 15?
You don't need to. After it restarts, simply grab /var/log/Xorg.0.log.old and attach it here. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 504263 [details] /var/log/Xorg.0.log.old I installed debuginfo for the intel driver and it still doesn't show up in the backtrace -- how do I get Xorg to give the debuginfo in the backtrace? This is a Heisenbug -- since installing the debuginfo, the bug has suddenly become quite hard to trigger. I have to restart the X server several times before I can trigger the bug by opening the image.
(In reply to comment #9) > Created attachment 504263 [details] > /var/log/Xorg.0.log.old > > I installed debuginfo for the intel driver and it still doesn't show up in the > backtrace -- how do I get Xorg to give the debuginfo in the backtrace? Xorg catches backtraces on its own and abrt doesn't get involved at all. So here we have nice backtrace in Xorg.0.log: Backtrace: [ 161.129] 0: /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a142f] [ 161.129] 1: /usr/bin/Xorg (0x400000+0x62316) [0x462316] [ 161.129] 2: /lib64/libpthread.so.0 (0x3aad000000+0xeeb0) [0x3aad00eeb0] [ 161.129] 3: /lib64/libc.so.6 (0x3aac800000+0x12dff1) [0x3aac92dff1] [ 161.129] 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5d96fdf000+0x11a46) [0x7f5d96ff0a46] [ 161.129] 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5d96fdf000+0x133a6) [0x7f5d96ff23a6] [ 161.129] 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5d96fdf000+0x2761d) [0x7f5d9700661d] [ 161.129] 7: /usr/bin/Xorg (0x400000+0xdc199) [0x4dc199] [ 161.129] 8: /usr/bin/Xorg (0x400000+0x2b91d) [0x42b91d] [ 161.129] 9: /usr/bin/Xorg (0x400000+0x2ec11) [0x42ec11] [ 161.129] 10: /usr/bin/Xorg (0x400000+0x22e1a) [0x422e1a] [ 161.129] 11: /lib64/libc.so.6 (__libc_start_main+0xed) [0x3aac82139d] [ 161.129] 12: /usr/bin/Xorg (0x400000+0x23101) [0x423101] [ 161.129] Bus error at address 0x7f5d8451d010 [ 161.129] Fatal server error: [ 161.129] Caught signal 7 (Bus error). Server aborting [ 161.129] [ 161.129] Please consult the Fedora Project support at http://wiki.x.org for help.
No, I saw that, but there is no symbol information in that backtrace. I was asking how to get Xorg to add symbol information. Is that not possible?
(In reply to comment #11) > No, I saw that, but there is no symbol information in that backtrace. I was > asking how to get Xorg to add symbol information. Is that not possible? Unfortunately, there is no easy way ... working on some automagical (or at least semi-automagical) way, but not done yet.
--------------------------------- In function intel_uxa_pixmap_put_image: (from frame 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5d96fdf000+0x11a46) [0x7f5d96ff0a46]) 742: char *dst = priv->bo->virtual; 743: int row_length = w * cpp; 744: int num_rows = h; 745: if (row_length == src_pitch && src_pitch == stride) 746: num_rows = 1, row_length *= h; 747: dst += y * stride + x * cpp; 748: do { 749: memcpy (dst, src, row_length); 750: src += src_pitch; 751: dst += stride; 752: >>>>>>> } while (--num_rows); 753: drm_intel_gem_bo_unmap_gtt(priv->bo); 754: ret = TRUE; 755: } 756: 757: return ret; 758: } 759: 760: static Bool intel_uxa_put_image(PixmapPtr pixmap, 761: int x, int y, 762: int w, int h, Frame 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5d96fdf000+0x133a6) [0x7f5d96ff23a6] Souce file: /usr/src/debug/xf86-video-intel-2.15.0/src/intel_uxa.c In function intel_uxa_put_image, line no. 806 Frame 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5d96fdf000+0x2761d) [0x7f5d9700661d] Souce file: /usr/src/debug/xf86-video-intel-2.15.0/uxa/uxa-accel.c In function uxa_do_put_image, line no. 342 Frame 7: /usr/bin/Xorg (0x400000+0xdc199) [0x4dc199] Souce file: /usr/src/debug/xorg-server-1.10.2/miext/damage/damage.c In function damagePutImage, line no. 880 Frame 8: /usr/bin/Xorg (0x400000+0x2b91d) [0x42b91d] Souce file: /usr/src/debug/xorg-server-1.10.2/dix/dispatch.c In function ProcPutImage, line no. 1990 Frame 9: /usr/bin/Xorg (0x400000+0x2ec11) [0x42ec11] Souce file: /usr/src/debug/xorg-server-1.10.2/dix/dispatch.c In function Dispatch, line no. 431 Frame 10: /usr/bin/Xorg (0x400000+0x22e1a) [0x422e1a] Souce file: /usr/src/debug/xorg-server-1.10.2/dix/main.c In function main, line no. 296 bradford:xorg-backtrace-analyze (master) $
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping