Bug#507916: xorg: Xorg segfault on swsusp resume
Andy Isaacson wrote:
> Package: xorg
> Version: 1:7.3+18
> Severity: important
>
> I trigger swsusp on my Thinkpad X40 using a script which does
>
> sudo sh -c 'echo 300000000 > /sys/power/image_size;
> echo shutdown > /sys/power/disk;
> echo disk > /sys/power/state'
>
> This generally works (I've probably suspended 500 times in the last
> three years, running various -mm and mainline kernels, and most of the
> time it works), but this morning the X server crashed while resuming in
> a most interesting manner:
>
>
>> (II) Open ACPI successful (/var/run/acpid.socket)
>> (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007df000 (pgoffset 2015)
>> (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x007e0000 (pgoffset 2016)
>> (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x007e4000 (pgoffset 2020)
>> (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x007e5000 (pgoffset 2021)
>> (II) intel(0): xf86BindGARTMemory: bind key 4 at 0x007e9000 (pgoffset 2025)
>> (II) intel(0): xf86BindGARTMemory: bind key 5 at 0x007f0000 (pgoffset 2032)
>>
>> Backtrace:
>> 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8631]
>> 1: [0xffffe400]
>> 2: /usr/bin/X11/X(xf86_reload_cursors+0x70) [0x80f9f80]
>> 3: /usr/lib/xorg/modules/drivers//i810_drv.so [0xb7ba5f62]
>> 4: /usr/bin/X11/X(xf86CrtcSetMode+0x279) [0x80f9169]
>> 5: /usr/bin/X11/X(xf86SetDesiredModes+0x139) [0x80f9519]
>> 6: /usr/lib/xorg/modules/drivers//i810_drv.so [0xb7ba98c9]
>> 7: /usr/lib/xorg/modules//libxaa.so [0xb7a643f2]
>> 8: /usr/bin/X11/X [0x80d08fc]
>> 9: /usr/bin/X11/X [0x80ddcd8]
>> 10: /usr/bin/X11/X(xf86Wakeup+0x3bd) [0x80c9d4d]
>> 11: /usr/bin/X11/X(WakeupHandler+0x59) [0x80929e9]
>> 12: /usr/bin/X11/X(WaitForSomething+0x1ae) [0x81b88ee]
>> 13: /usr/bin/X11/X(Dispatch+0x82) [0x808ec22]
>> 14: /usr/bin/X11/X(main+0x495) [0x8076e85]
>> 15: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d74450]
>> 16: /usr/bin/X11/X(FontFileCompleteXLFD+0x1ed) [0x80761c1]
>>
>> Fatal server error:
>> Caught signal 11. Server aborting
>>
>> (II) intel(0): xf86UnbindGARTMemory: unbind key 0
>> (II) intel(0): xf86UnbindGARTMemory: unbind key 1
>> (II) intel(0): xf86UnbindGARTMemory: unbind key 2
>> (II) intel(0): xf86UnbindGARTMemory: unbind key 3
>> (II) intel(0): xf86UnbindGARTMemory: unbind key 4
>> (II) intel(0): xf86UnbindGARTMemory: unbind key 5
>>
>
> It looks to me like the SIGIO from the mouse filedescriptor came in
> while the driver was reinitializing and caught a function pointer with
> its pants down.
>
> I've never seen this before, though I have had some untriaged X
> crashes-on-resume in the past.
>
Can you reproduce this bug? If so, could you upgrade to experimental and
see if the bug is gone?
> Complete system information (including xorg.conf, .config, and complete
> Xorg.0.log.old) is at
> http://web.hexapodia.org/~adi/bobble/bobble_2.6.27_20081205113626/
> http://web.hexapodia.org/~adi/bobble/bobble_2.6.27_20081205113626.tar.gz
> SHA1 (bobble_2.6.27_20081205113626.tar.gz) = 2123c9633053f1423b04ebff2d8cc71f72774ae0
>
Please send you xorg.conf and Xorg.0.log to the bug report so that we
are always able to download it, even when your personal webpage will be
down.
Brice
Reply to: