Bug#805974: xserver-xorg-core: X server crash after corruption seen in rxvt-unicode under kde4
On 24.11.2015 21:41, Zoran Dželajlija wrote:
> Package: xserver-xorg-core
> Version: 2:1.16.4-1
> Severity: important
>
> Hi,
>
> X server with a KDE4 session running on a Radeon HD 7450, single DP screen
> connected, just crashed. Last few actions done before the crash was
> maximizing a urxvt (rxvt-unicode 9.20-1+b1) window that started to show
> corruption at that point, refreshing just the last line (~16 pixels
> vertical) instead of the whole window. X crashed a second or two after
> that.
>
> This is a recently upgraded and migrated hardware system with an ivy bridge
> board and cpu. Kernel and xserver-org-video-intel are from
> jessie-backports, but there's also a discrete ati card which I've been using
> just to see how it works. X has been running for a couple weeks without
> issues, apart from my own accidental zap with Ctrl-Alt-Backspace.
>
> Not sure whether to file against video-radeon or X server itself. The
> stack trace (see below for Xorg.0.log.old) does not look like anything
> radeon specific, so xserver-xorg-core it is.
[...]
> [2836461.796] failed to map pixmap: -12
This means that radeon_bo_map() returned -12 (-ENOMEM) in
EVERGREENDownloadFromScreen().
> [2836461.798] (EE)
> [2836461.798] (EE) Backtrace:
> [2836461.808] (EE) 0: /usr/bin/X (xorg_backtrace+0x52) [0x56785552]
> [2836461.808] (EE) 1: /usr/bin/X (0x565df000+0x1aa7f2) [0x567897f2]
> [2836461.808] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xf779db50]
> [2836461.808] (EE) 3: /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xf733a000+0x12ff40) [0xf7469f40]
> [2836461.808] (EE) 4: /usr/lib/xorg/modules/libexa.so (0xf53c4000+0x48de) [0xf53c88de]
> [2836461.808] (EE) 5: /usr/lib/xorg/modules/libexa.so (0xf53c4000+0x4e27) [0xf53c8e27]
> [2836461.808] (EE) 6: /usr/lib/xorg/modules/libexa.so (0xf53c4000+0x5043) [0xf53c9043]
> [2836461.808] (EE) 7: /usr/lib/xorg/modules/libexa.so (0xf53c4000+0x748b) [0xf53cb48b]
> [2836461.808] (EE) 8: /usr/lib/xorg/modules/libexa.so (0xf53c4000+0x3d83) [0xf53c7d83]
> [2836461.808] (EE) 9: /usr/lib/xorg/modules/libexa.so (0xf53c4000+0x10013) [0xf53d4013]
> [2836461.808] (EE) 10: /usr/lib/xorg/modules/libexa.so (0xf53c4000+0x7707) [0xf53cb707]
> [2836461.808] (EE) 11: /usr/bin/X (0x565df000+0x12ab24) [0x56709b24]
> [2836461.808] (EE) 12: /usr/bin/X (0x565df000+0x39346) [0x56618346]
> [2836461.808] (EE) 13: /usr/bin/X (0x565df000+0x3d086) [0x5661c086]
> [2836461.808] (EE) 14: /usr/bin/X (0x565df000+0x4126a) [0x5662026a]
> [2836461.808] (EE) 15: /usr/bin/X (0x565df000+0x2af2a) [0x56609f2a]
> [2836461.808] (EE) 16: /lib/i386-linux-gnu/i686/cmov/libc.so.6 (__libc_start_main+0xf3) [0xf7353a63]
> [2836461.808] (EE) 17: /usr/bin/X (0x565df000+0x2af68) [0x56609f68]
> [2836461.808] (EE)
> [2836461.808] (EE) Segmentation fault at address 0x0
> [2836461.808] (EE)
> Fatal server error:
> [2836461.808] (EE) Caught signal 11 (Segmentation fault). Server aborting
This immediate crash is an EXA bug. glamor might handle this more
gracefully.
However, since there seems to be some kind of out of memory situation,
even if a crash can be avoided, correct rendering probably cannot be
maintained. Maybe you can try running Xorg in valgrind --leak-check=full
to see if there's a memory leak somewhere. When you do so, please make
sure the xserver-xorg-core-dbg and xserver-xorg-video-radeon-dbg
packages are installed.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
Reply to: