SIGQUIT from tty layer
bgamari.foss at gmail.com
Sat Jul 11 07:54:42 PDT 2009
On Fri, Jul 10, 2009 at 08:33:46PM +0200, Samuel Thibault wrote:
> Not writing to the tty, but producing input for the tty. Are you
> using evdev or the legacy kbd driver?
> 0x1c is the keycode of the enter key, maybe your workload happens to
> restart the keyboard driver, which temporarily re-enables signal keys.
What syscall would one use to do this? Perhaps I could systemtap this.
> Or maybe it's on another tty, do you have anything beyond /dev/mem,
> /dev/null, /dev/tty7, /dev/agpgart and /dev/dri/card* in
> lsof -p $(pidof Xorg) | grep CHR
[1038 ben at ben-laptop ~] $ sudo lsof -p $(pidof X) | grep CHR
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/ben/.gvfs
Output information may be incomplete.
X 2787 root mem CHR 226,0 1191 /dev/dri/card0
X 2787 root 5w CHR 4,7 0t0 1150 /dev/tty7
X 2787 root 8u CHR 226,0 0t0 1191 /dev/dri/card0
X 2787 root 10u CHR 13,66 0t0 1464 /dev/input/event2
X 2787 root 11u CHR 13,67 0t0 1505 /dev/input/event3
X 2787 root 12u CHR 13,65 0t0 1450 /dev/input/event1
X 2787 root 13u CHR 13,68 0t0 1478 /dev/input/event4
X 2787 root 14u CHR 13,69 0t0 1471 /dev/input/event5
X 2787 root 15u CHR 13,72 0t0 4938 /dev/input/event8
X 2787 root 16u CHR 13,71 0t0 4905 /dev/input/event7
So other than a bunch of event devices, not too much. Thanks for your
More information about the xorg