I have a custom application running on an embedded x86 setup (built using buildroot and uClibc). The application has been running fine but this morning when I returned to work I discovered my process had been killed and the following output on my terminal
SAK: killed process 1008 (CX_SC3): fd#4 opened to the tty
SAK: killed process 1009 (CX_SC3): fd#4 opened to the tty
SAK: killed process 1011 (CX_SC3): fd#4 opened to the tty
SAK: killed process 1012 (CX_SC3): fd#4 opened to the tty
Now CX_SC3
is my process – it has multiple threads, one of which opens /dev/ttyS0
to send messages over a radio modem. The fd number is 4 for the serial port. What I don't understand is
- What the SAK means
- The PID listed above must refer to a process that was killed by my application as there is only ever one instance of my application running at a time. Is it possible that these PIDs are actually my thread IDs (as my application does run 4 threads always).
- If my application killed other processes, why was my application also killed?
- What does the
opened to the tty
part mean? From some research this suggests that this has something to do with a interrupt character sent to the tty that I used to start the program.
What events could have lead to the following output? My embedded setup is very small, uses busybox
and runs vsftpd
and very little else other than my custom application. It is vital that my application is robust.
EDIT: In response to the comment below, if this is due to a SAK being detected, is there anything that can accidentally trigger this? Is it possible that anything being read on the serial port has triggered this? Also, how can I find the SAK combination for my system – I do not have a rc.sysinit
or rc.local
file anywhere in my root file system.
UPDATE: I have managed to pin this event down to the point at which my host machine shuts down. I have a serial cable between my host machine and my target device which I use to send serial data to the embedded target. When I leave the target running, but shutdown the host, my application is killed as described above. When I disconnect the serial cable prior to shutting down my host machine then my application does not get killed and runs as normal. This behaviour happens even after I have performed
echo 0 > /proc/sys/kernel/sysrq
as advised.
Best Answer
SAK in this case really means Secure Attention Key. The message you are seeing is a kernel message defined in drivers/tty/tty_io.c. SAK is a key combination which ensures secure login for a user on console. On Linux SAK ensures this by killing all processes attached to the terminal SAK is invoked on. It is expected that
init
will then restart the trusted login process likegetty
followed bylogin
or X server with display manager.The listed PIDs are indeed PIDs of threads of your application
CX_SC3
which were killed by SAK.fd#n opened to the tty
means that the process/thread which was killed had the file descriptorn
opened to the terminal on which the SAK was invoked.In Linux there are two ways of invoking SAK:
Through the magic SysRq key - typically Alt+SysRq+K (virtual terminal) or BreakK (serial console). This is not your case as you already tried to disable the magic SysRq by
echo 0 > /proc/sys/kernel/sysrq
and sending the BreakK sequence by accident is improbable.Through a defined key sequence (virtual terminal) or the break signal (serial console). SAK availability on a serial console is controlled by
setserial
.Break signal on a serial line is continuous sending of spacing values over a time longer than the character sending time (including start, stop and parity bits). In you case it is highly probable that the condition of the Break signal appears during shutting your host machine down. Please try to turn the SAK off on your serial port on the target device by
setserial
:You can check the SAK functionality status on the serial port by
setserial -g /dev/ttyS0
. When turned on it will showSAK
afterFlags:
. For automatic setting of the option after boot see the startup scripts which on BusyBox systems are usually/etc/init.d/rcS
and/etc/rc.d/S*
or check/etc/inittab
for other possibilities.