Created attachment 33065 [details] [review]
I'm on Debian testing with graphic stack from sid, this is:
01:00.0 VGA compatible controller : ATI Technologies Inc Mobility Radeon HD 3600 Series [1002:9598]
I was on KDE 4.3.4 with desktop effects on. I added a lot of downloads to kget and the plasma notifier opened a lot of notifications. As I have the notifier in the left side of screen, in this case the notifications would have overflown the screen height, so they couldn't have been seen. Anyways, I couldn't see them becuase xserver crashed with this backtrace:
#0 0x00007f4ef3322f55 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00007f4ef3325d90 in *__GI_abort () at abort.c:88
#2 0x00000000004712c3 in ddxGiveUp () at ../../../../hw/xfree86/common/xf86Init.c:1214
#3 0x000000000046a2dd in AbortServer () at ../../os/log.c:404
#4 0x000000000046a97e in FatalError (f=0x573ae8 "Caught signal %d (%s). Server aborting\n") at ../../os/log.c:529
#5 0x000000000046421e in OsSigHandler (signo=11, sip=0x10, unused=<value optimized out>) at ../../os/osinit.c:156
#6 <signal handler called>
#7 r600SetTexOffset (pDRICtx=<value optimized out>, texname=<value optimized out>, offset=3735386112, depth=32, pitch=1792) at r600_texstate.c:862
#8 0x00007f4ef1fd61ec in __glXDRIleaveServer (rendering=<value optimized out>) at ../../glx/glxdri.c:152
#9 0x00007f4ef1fcd048 in __glXleaveServer (rendering=48 '0') at ../../glx/glxext.c:534
#10 0x00007f4ef1fcd66e in __glXDispatch (client=0x26a1400) at ../../glx/glxext.c:580
#11 0x0000000000431524 in Dispatch () at ../../dix/dispatch.c:439
#12 0x0000000000425bca in main (argc=8, argv=0x7d48e8, envp=<value optimized out>) at ../../dix/main.c:285
I guess it's related to trying to draw something out of the screen bounds.
Find attached the xorg log.
Just for your information. Today, I got the same crash with xserver 1.7.5.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/95.