I am not sure if it is still the same issue, but the last comments in
this bug are very similar to what is reported in bug 55821.
A reproducible test case I could not find. It just happens during normal
use, though a heavy load (suspend/resume) may trigger it quicker. It is
hard to be really sure
A couple of weeks ago I experienced a similar bug once or twice (at
least a similar backtrace as in comment 16), but I also did not have
symbols installed.
However, it may be noteworthy that I did not trigger it by a resume, but
by putting very heavy load on the machine. I have not done so since,
My eeepc running mint has suddenly (after an update) also started to
exhibit this bug. It is starting to get annoying! I will try the patch
mentioned in the coming days (but confirmation can take some time, I
only hit this once a week or less).
--
You received this bug notification because you ar
Hmm, Peter, can you confirm that patch is already in Fedora 18. It seems to
have been merged as part of:
* Tue Oct 30 2012 Peter Hutterer 1.13.0-6
- Add touchscreen fixes (including pointer emulation) #871064
So unless it was reverted by a later patch (at 1.13.2-1 now), this is
not it (unless th
just compiled 2.21.13 as it is supposed to fix some mem corruption, but
it still crashes...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203273
Title:
Xorg crashed with SIGABRT in has_offload_slav
with O0 -g3 it was not so easy to trigger, but:
Program received signal SIGSEGV, Segmentation fault.
0x7f1472b8b88c in has_offload_slaves (sna=0x7f1471868000)
at sna_accel.c:14747
14747 ScreenPtr screen = sna->scrn->pScreen;
(gdb) bt full
#0 0x7f1472b8b88c in has_offload_slaves (sna
I did recompile with full debug but unfortunately, I do not manage to
crash it with the same procedure. Everything is a lot slower however, so
maybe timing is important.
I suspected memory corruption as well as triggering the crash seems to
rely there being consideral memory load on the system.
W
Created attachment 83493
gdb output
Work is keeping my too busy, so it took some time. Anyway, finally did
manage to get the gdb output at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203273
You're quicker than I had time to recompile with debug. As far as i can
tell, this has fixed the issue. Should it change, i will let you know.
Thanks!
d.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
