| Summary: | [IVB/HSW Regression] X server crash when Lightsmark v2008 run 10~15 times | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | liulei <lei.a.liu> | ||||||||||||
| Component: | Driver/intel | Assignee: | Chris Wilson <chris> | ||||||||||||
| Status: | VERIFIED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||
| Severity: | major | ||||||||||||||
| Priority: | high | CC: | eero.t.tamminen, intel-gfx-bugs, Mark.Rodehorst, mengmeng.meng | ||||||||||||
| Version: | git | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux (All) | ||||||||||||||
| Whiteboard: | |||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
liulei
2014-06-24 03:08:55 UTC
Created attachment 101623 [details]
Xorg.log
I'll be impressed if you can bisect this to a kernel commit... (In reply to comment #2) > I'll be impressed if you can bisect this to a kernel commit... It's hard to reproduce this issue. Game may crash after ten or even fifteen times running. I find it's not kernel after I increase my attempts to fifteen. *** This bug has been marked as a duplicate of bug 80157 *** If you plan on reopening a bug, make sure you include the up-to-date information, i.e. treat it as a fresh bug report to at least convince us that is the same bug. = Environment= -------------------------- Platform:IVB/HSW Libdrm: (master)libdrm-2.4.54-19-gc0b34dca2632a774249cfa3b969c3f7ce9df33e1 Mesa: (master)48deb4dbf278c03ea49aeaa7f9d9eda231def817 Xserver: (master)xorg-server-1.15.99.902-121-g2f5cf9ff9a0f713b7e038636484c77f113a5f10a Xf86_video_intel: (master)2.99.912-233-gf33d44f41ef0f287375b7a6b1c117abff5a23b19 Cairo: (master)f4dbba26d4fc571e0621f3c7a98196c501f8bcc5 Libva: (master)c61d8c6ce9ffc27320e9e177c1e1123d5f1b5014 Libva_intel_driver: (master)c5cb17ea86f0065a939d3636dd26651c93d497c8 kernel: drm-intel-nightly 8734408c113bb38234ed03ec51c723b3deff579b drm-intel-nightly: 2014y-07m-18d-15h-21m-24s integration manifest I found this issue still exists.
(EE) Backtrace:
(EE) 0: X (xorg_backtrace+0x48) [0x469fd8]
(EE) 1: X (0x400000+0x6fd69) [0x46fd69]
(EE) 2: /usr/lib64/libpthread.so.0 (0x3f7a200000+0xefa0) [0x3f7a20efa0]
(EE) 3: /usr/lib64/libc.so.6 (0x3f79e00000+0x148593) [0x3f79f48593]
(EE) 4: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0x61f3b) [0x7f1ee4a3af3b]
(EE) 5: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0x62c81) [0x7f1ee4a3bc81]
(EE) 6: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0x41a4c) [0x7f1ee4a1aa4c]
(EE) 7: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0x52cb2) [0x7f1ee4a2bcb2]
(EE) 8: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0x324b4) [0x7f1ee4a0b4b4]
(EE) 9: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0x327ab) [0x7f1ee4a0b7ab]
(EE) 10: X (0x400000+0x128aba) [0x528aba]
(EE) 11: X (0x400000+0x120a5c) [0x520a5c]
(EE) 12: X (0x400000+0x121592) [0x521592]
(EE) 13: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0xf7f71) [0x7f1ee4ad0f71]
(EE) 14: /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so (0x7f1ee49d9000+0x6c12f) [0x7f1ee4a4512f]
(EE) 15: X (WakeupHandler+0x9c) [0x43da6c]
(EE) 16: X (WaitForSomething+0x1bf) [0x4738cf]
(EE) 17: X (0x400000+0x38e71) [0x438e71]
(EE) 18: X (0x400000+0x3cf4a) [0x43cf4a]
(EE) 19: /usr/lib64/libc.so.6 (__libc_start_main+0xf5) [0x3f79e21b75]
(EE) 20: X (0x400000+0x286c1) [0x4286c1]
(EE)
(EE) Segmentation fault at address 0x7f1ee2fb6000
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/opt/X11R7/var/log/Xorg.0.log" for additional information.
(EE)
(II) AIGLX: Suspending AIGLX clients for VT switch
Created attachment 103167 [details]
reopen-xorg.log
(In reply to comment #7) > I found this issue still exists. > (EE) Backtrace: [snip] > Fatal server error: > (EE) Caught signal 11 (Segmentation fault). Server aborting Which doesn't look a lot like the original. Either capture the bt in gdb or run it through addr2line. Created attachment 103169 [details]
reopen-dmesg.log
(In reply to comment #9) > (In reply to comment #7) > > I found this issue still exists. > > (EE) Backtrace: > [snip] > > Fatal server error: > > (EE) Caught signal 11 (Segmentation fault). Server aborting > > Which doesn't look a lot like the original. Either capture the bt in gdb or > run it through addr2line. Are they the same issue with below bug? https://bugs.freedesktop.org/show_bug.cgi?id=81215 That's what I suspect, but I don't have enough information to be sure. > Which doesn't look a lot like the original. Either capture the bt in gdb or
> run it through addr2line.
Excuse me, I haven't done this before. Would you please offer me steps to run it through addr2line?
You have to specify the object to read the debug information from and the relative addresses: addr2line -e /opt/X11R7/lib/xorg/modules/drivers/intel_drv.so -i 0x61f3b 0x62c81 0x41a4c 0x52cb2 0x324b4 0x327ab 0xf7f71 0x6c12f It is not as good as using gdb and inspecting the fault in place, but it is better than nothing. Created attachment 103245 [details]
gdb.log
(In reply to comment #15) > Created attachment 103245 [details] > gdb.log Oh, if you want to print the locals at each frame, just use "bt full". That stack is bug 81215 so I don't think we have a re-occurrence of the DRI2 bug here. *** Bug 83176 has been marked as a duplicate of this bug. *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.