Xorg crash in FlushClient() on login after resume from suspend

[Connor Imes]

Binary package hint: xorg

This crash appeared while I was backtracing for a different problem. I was able to reproduce this, I will attach both backtraces.
Oddly, the X session was able to continue after I stopped gdb.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xorg 1:7.4~5ubuntu16
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-8-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu1) ) #28-Ubuntu SMP Thu Mar 5 21:49:36 UTC 2009
SourcePackage: xorg
Uname: Linux 2.6.28-8-generic i686
XorgConf:

#0 0xb8078430 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7d121fc in writev () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x0813c0de in _XSERVTransSocketWritev (ciptr=0xa314b38, buf=0xbf994fb4,
    size=1) at /usr/include/X11/Xtrans/Xtranssock.c:2184
No locals.
#3 0x0813b11f in _XSERVTransWritev (ciptr=0xa314b38, buf=0xbf994fb4, size=1)
    at /usr/include/X11/Xtrans/Xtrans.c:912
No locals.
#4 0x081370c2 in FlushClient (who=0xa310a50, oc=0xa3172e0, __extraBuf=0x0,
    extraCount=0) at ../../os/io.c:899
 before = <value optimized out>
 remain = <value optimized out>
 i = -1080471628
 len = <value optimized out>
 oco = (ConnectionOutputPtr) 0xa317b18
 connection = 15
 trans_conn = (XtransConnInfo) 0xa314b38
 iov = {{iov_base = 0xa24c058, iov_len = 64}, {iov_base = 0x0,
    iov_len = 0}, {iov_base = 0x81e5ff4, iov_len = 3214495720}}
 written = 0
 padsize = 0
 notWritten = 64
 todo = 64
 padBuffer = "\000\000"
#5 0x08135957 in CloseDownConnection (client=0xa310a50)
    at ../../os/connection.c:1047
 oc = (OsCommPtr) 0xa3172e0
#6 0x080876dd in CloseDownClient (client=0xa310a50)
    at ../../dix/dispatch.c:3404
 really_close_down = 1
#7 0x0808d448 in Dispatch () at ../../dix/dispatch.c:448
 result = 136277312
 client = (ClientPtr) 0xa310a50
 nready = 0
 start_tick = 300

[Connor Imes (ckimes)]

By the way, I believe the crash appeared after I typed in my password and clicked Enter (that's when it froze anyway). Here is the reproduced backtrace.

[Connor Imes (ckimes)]

I just confirmed that it is showing the crash at the moment I press Enter at the password prompt screen. However, I am able to continue with the X session by either quitting gdb or running "cont".

[Nikos Efthimiou (nikos-efthimiou)]

I am having a slightly different problem.

On resume the cursor appears as well as a red strip on the upper right part of the screen and the system froze.

I have a toshiba A200 with ATI video card.

[Connor Imes (ckimes)]

Nikos,
This sounds like a different problem, with different hardware - you should file a new bug report for your problem.
Thanks and good luck.

[Bryce Harrington (bryce)]

Looking at the backtrace, I sense this is failing somewhere deeper down than X. I'm refiling to the kernel; if nothing else they're a bit more skillful at analyzing resume failures so hopefully can recommend better debugging techniques than I.

[Leann Ogasawara (leannogasawara)]

Hi Connor,

Care to do a quick round of testing with the latest Karmic Alpha release? ISO CD images can be found at http://cdimage.ubuntu.com/releases/karmic/ . I'd like to just verify this issue remains with the 2.6.31 based kernel in Karmic. You should be able to test Suspend using a LiveCD. Please let us know your results. Thanks.

[Connor Imes (ckimes)]

Hi Leann, it seems that this is still a problem - I just captured another backtrace for you in a fully up-to-date Karmic, which I fresh installed with alpha 3 a couple of weeks ago. The trace appears to be the same.

This doesn't seem to prevent X from functioning properly, as I can "cont" afterward, or simply "handle SIGPIPE nostop" beforehand, and the system proceeds normally.

If you're not running Xorg through gdb, you would never know about this problem.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]