Skip site navigation (1)Skip section navigation (2) 
Date:      Tue, 17 Dec 1996 00:27:25 -0800
From:      Steven Wallace <swallace@ece.uci.edu>
To:        bugs@freebsd.org
Cc:        dawes@xfree86.org
Subject:   unexpected signal 2?
Message-ID:  <199612170827.AAA15424@newport.ece.uci.edu>
next in thread | raw e-mail | index | archive | help 

I just had an interesting experience with my new 3.2 XFree86 X server.

I ran this little FWF test program called AnsiTermT.
When I typed ^C in the xterm where I ran AnsiTermT, it shuts down my
X server saying:
xinit:  unexpected signal 2
xinit:  connection to X server lost.

Here is the last bit of a kdump

   743 AnsiTermT CALL  write(0x3,0x17000,0x14)
   743 AnsiTermT GIO   fd 3 wrote 20 bytes
       "L\^A\^E\0\v\0\M^@\^C\b\0\M^@\^C.\^BP\0 \0\^D\0"
   743 AnsiTermT RET   write 20/0x14
   743 AnsiTermT CALL  ioctl(0x3,FIONREAD,0xefbfcb98)
   743 AnsiTermT RET   ioctl 0
   743 AnsiTermT CALL  gettimeofday(0xefbfd368,0)
   743 AnsiTermT RET   gettimeofday 0
   743 AnsiTermT CALL  select(0x5,0xefbfd304,0xefbfd324,0xefbfd344,0xefbfd378)
   743 AnsiTermT PSIG  SIGINT caught handler=0x4600 mask=0x0 code=0x0
   743 AnsiTermT RET   select -1 errno 4 Interrupted system call
   743 AnsiTermT CALL  kill(0xffffffff,0x2)
   743 AnsiTermT PSIG  SIGHUP caught handler=0x4600 mask=0x2 code=0x0
   743 AnsiTermT RET   kill 0
   743 AnsiTermT CALL  kill(0xffffffff,0x1)
   743 AnsiTermT PSIG  SIGCHLD caught handler=0x45dc mask=0x3 code=0x0
   743 AnsiTermT RET   kill 0
   743 AnsiTermT CALL  fstat(0x1,0xefbfce00)
   743 AnsiTermT RET   fstat -1 errno 9 Bad file descriptor
   743 AnsiTermT CALL  wait4(0xffffffff,0xefbfd150,0,0)
   743 AnsiTermT RET   wait4 744/0x2e8
   743 AnsiTermT CALL  write(0x1,0x22800,0x14)
   743 AnsiTermT RET   write -1 errno 5 Input/output error
   743 AnsiTermT CALL  exit(0)


I don't know why this simple user-level program is causing
my X server to die.  I've u/ld the binary to freefall.


Also, I've always had this annonying problem using a PS/2 mouse,
which is why I end up using a serial one.  When I use device
/dev/psm0 and protocol PS/2, sometimes the keyboard state gets messed
up so that the X server thinks a modifier key (control, alt) will 
remain in the depressed state when the key is not pressed.  I
have to press and release the key again to correct the state.
This does not happen when I use a serial mouse.

I was having some other wierd problems with 3.1.2 and my ps/2 mouse.
I just upgraded to 3.2 and those problems went away, but this
keystate problem persists.

Steven

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612170827.AAA15424>