[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#622653: Fatal server error: Caught signal 11 (Segmentation fault). Server aborting



On So, 2011-04-17 at 19:48 +0300, Modestas Vainius wrote:
> Hello,
> 
> On sekmadienis 17 Balandis 2011 19:39:34 Julian Andres Klode wrote:
> > On So, 2011-04-17 at 19:32 +0300, Modestas Vainius wrote:
> > > forwarded 622653 https://bugs.freedesktop.org/show_bug.cgi?id=36319
> > > tags 622653 upstream fixed-upstream patch
> > > thanks
> > > 
> > > Hello,
> > > 
> > > On trečiadienis 13 Balandis 2011 19:58:06 Julian Andres Klode wrote:
> > > > Package: xserver-xorg-video-intel
> > > > Version: 2:2.14.902-1
> > > > Severity: grave
> > > > 
> > > > X crashed about 4 times today. It did not crash directly after the
> > > > upgrade or yesterday, as far as I can remember, but now it seems
> > > > to crash. I am running GNOME 3 with gnome-shell, and thus use
> > > > compositing.
> > > > 
> > > > 
> > > > I attached upgrade logs of the past days, as well as
> > > > a X log showing the bug.  The relevant part is:
> > > > 
> > > > Backtrace:
> > > > [  5306.687] 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x4aacc8]
> > > > [  5306.687] 1: /usr/bin/Xorg (0x400000+0x61e59) [0x461e59]
> > > > [  5306.687] 2: /lib/libpthread.so.0 (0x7f52090f9000+0xef60)
> > > > [0x7f5209107f60] [  5306.687] 3: /usr/lib/libdrm_intel.so.1
> > > > (drm_intel_bo_emit_reloc+0x0) [0x7f5205c2adb0] [  5306.687] 4:
> > > > /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5205e34000+0x227a0)
> > > > [0x7f5205e567a0] [  5306.687] 5:
> > > > /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5205e34000+0x2797f)
> > > > [0x7f5205e5b97f] [  5306.687] 6:
> > > > /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5205e34000+0x29d5f)
> > > > [0x7f5205e5dd5f] [  5306.687] 7:
> > > > /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5205e34000+0x27473)
> > > > [0x7f5205e5b473] [  5306.687] 8: /usr/bin/Xorg (miPolyRectangle+0xd8)
> > > > [0x550228]
> > > > [  5306.687] 9: /usr/bin/Xorg (0x400000+0xdf142) [0x4df142]
> > > > [  5306.687] 10: /usr/bin/Xorg (0x400000+0x46082) [0x446082]
> > > > [  5306.687] 11: /usr/bin/Xorg (0x400000+0x48909) [0x448909]
> > > > [  5306.687] 12: /usr/bin/Xorg (0x400000+0x257ab) [0x4257ab]
> > > > [  5306.687] 13: /lib/libc.so.6 (__libc_start_main+0xfd)
> > > > [0x7f5207e55c4d] [  5306.687] 14: /usr/bin/Xorg (0x400000+0x25339)
> > > > [0x425339]
> > > > [  5306.687] Segmentation fault at address (nil)
> > > > [  5306.687]
> > > > Fatal server error:
> > > > [  5306.687] Caught signal 11 (Segmentation fault). Server aborting
> > > > [  5306.687]
> > > > [  5306.687]
> > > 
> > > The bug is i965 specific. Upstream has just fixed it hence the fix is NOT
> > > included in the latest 2.15.0 release. It would great if you could add
> > > the attached patch (which is a backport from upstream) to the 2.15.0
> > > package.
> > 
> > This specific bug or its symptoms have been fixed in 2.14.903 already. I
> > am running a self-compiled 2.14.903 since days without any X crash. So
> > either those are different problems or something changed in the driver
> > that worked around my specific problem while still keeping the
> > underlying bug.
> 
> I tested unpatched 2.15.0 and I could reproduce the crash reliably. Your and 
> my backtraces are the same. Anyways, I don't see any reason not to include the 
> patch.
Yes, we both had a buffer overrun via the same path. What changed for me
in 2.14.903 is that something which required more buffer now seems to
require less buffer, so I do not experience it anymore. But yes,
including it certainly makes sense.


-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.





Reply to: