----- Forwarded message from Mattia Dongili <[EMAIL PROTECTED]> -----
Subject: Re: xserver-xorg-input-evtouch: Changes to 'refs/tags/0.8.5' From: Mattia Dongili <[EMAIL PROTECTED]> Date: Wed, 13 Jun 2007 22:54:31 +0900 To: Jeremy Powell <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> X-Operating-System: Linux 2.6.22-rc4-mm2-1 i686 User-Agent: Mutt/1.5.13 (2006-08-11) X-Disclaimer: Buh! On Wed, Jun 13, 2007 at 12:23:27PM +0100, Jeremy Powell wrote: > Mattia Dongili wrote: ... > >hmmm, so a race condition basically... this may well be in the x server > >as well. > > > The thought had crossed my mind, but I'm still a bit of a noob with Linux > I attached gdb to xinit like so: > /# gdb xinit 6102 ... > Program received signal SIGPIPE, Broken pipe. > 0x401b7d50 in write () from /lib/libc.so.6 > (gdb) bt > #0 0x401b7d50 in write () from /lib/libc.so.6 > #1 0x4005988c in _X11TransWrite () from /usr/lib/libX11.so.6 > #2 0x4005ea90 in _XSend () from /usr/lib/libX11.so.6 > #3 0x000130a8 in ?? () hummm, you should attach to the X process (after it started, it's easier), so fire up X (startx or whaterver) and $ gdb -p $(pidof X) see also http://wiki.debian.org/XStrikeForce/XserverDebugging > >>Anyway, if you have the time to take a look, the problem is best > >>reproduced by tapping the screen and setting the date via the console > >>simultaneously (pressing enter to change the date ever so slightly after > >>tapping the screen). With some experimenting you should be able to > >>reproduce the crash nearly every time. > >> > > > >will surely try, I need the latop alive currently, but later I may have > >some more time ;) > > > >BTW: if you think the I pointed out is related, do you mind if I forward > >the discussion to the bug tracking system? it's easier this way to ask > >for some insight to xorg developers as well. > > > I dont know enough to say yet, I'm always concerned by the use of > 'freeze', I take it that its actually a crash and not a hang? By all hmmm, in the bug I pointed out the visual effect is that X is freezed, doesn't respond to anything, no mouse, no touchscreen, no keyboard. And it doesn't return to the console. Does it die in your case instead? ... > EVTouch: DoBtnAction btn_count=5 > EVTouch: setting (x/y)=(501/1100) > EVTouch: ReadInput type:03 code: 0x0001 value:1098 > EVTouch: setting (x/y)=(501/1098) > EVTouch: ReadInput type:00 code: 0x0000 value:0 > EVTouch: ConvertProc > FIRST: v0=501 v1=1098 > cx[0]=0.525370 cy[0]=0.100327 > cx[1]=0.474630 cy[1]=0.899673 > cx[2]=0.000000 cy[2]=0.000000 > ViewPort_X0=0 ViewPort_Y0=0 > dx=0.000000 dy=0.000000 > FINAL: v0=189 v1=264 > EVTouch: DoBtnAction btn_count=5 > EVTouch: setting (x/y)=(501/1098) > > Backtrace: > > Fatal server error: > Caught signal 11. Server aborting Hmmmm, I fear we're seeing different problems... argh. I don't even get to the server getting the signal... -- mattia :wq! ----- End forwarded message ----- -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
