Timeline for My process was killed but I cannot understand the kernel notice
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 3, 2013 at 13:21 | history | bounty awarded | mathematician1975 | ||
| Jul 2, 2013 at 11:19 | comment | added | mathematician1975 | On a run of strace I see no ioctl() calls inbetween my calls of open and ioctl using TIOCGSERIAL . It really does appear that either the open call is setting the SAK, or that the busybox implementation of setserial does not work properly. When I open /dev/ttyS0 the ASYNC_SAK bit is certainly set. | |
| Jul 2, 2013 at 8:49 | comment | added | pabouk - Ukraine stay strong | @mathematician1975 I forgot to address you in the comment above. | |
| Jul 1, 2013 at 20:57 | comment | added | pabouk - Ukraine stay strong | You are welcome! Unfortunately I cannot add comments anywhere except my reply. Please did you check by ioctl(fd, TIOCGSERIAL, &s_serial) immediately after open() that open() really enables SAK? For me it seems like a bug. Could you please run your application with strace to see if there is not hidden/overlooked ioctl() call somewhere? Useful is also to run catch syscall ioctl in gdb. This causes the program to stop on all ioct() syscalls. You can examine the arguments by printing the registers and stack even without symbols. en.wikipedia.org/wiki/X86_calling_conventions | |
| Jul 1, 2013 at 13:41 | vote | accept | mathematician1975 | ||
| Jul 1, 2013 at 10:01 | vote | accept | mathematician1975 | ||
| Jul 1, 2013 at 13:41 | |||||
| Jul 1, 2013 at 9:56 | comment | added | mathematician1975 | I finally managed to find a code based solution and I posted it on stackoverflow. I will add this answer here but I will accept your answer as this enabled me to identify the how and why of it all. Many thanks | |
| Jul 1, 2013 at 9:17 | comment | added | mathematician1975 | Thankyou for your answer - it is very helpful. Unfortunately, when my application is opening the serial port, the sak that I just disabled gets re-enabled. I must be setting a particular flag combination that is re-enabling the SAK on /dev/ttyS0 | |
| Jul 1, 2013 at 2:21 | history | edited | pabouk - Ukraine stay strong | CC BY-SA 3.0 | adding links and completing the answer by information about startup scripts |
| Jul 1, 2013 at 1:48 | history | edited | pabouk - Ukraine stay strong | CC BY-SA 3.0 | adding third link to test the ability |
| Jul 1, 2013 at 0:56 | history | edited | user26112 | CC BY-SA 3.0 | Add keyboard formatting. |
| Jul 1, 2013 at 0:53 | review | First posts | |||
| Jul 1, 2013 at 0:57 | |||||
| Jul 1, 2013 at 0:46 | history | edited | pabouk - Ukraine stay strong | CC BY-SA 3.0 | adding links - unfortunately invsible as I do not have enough reputation for more than two links |
| Jul 1, 2013 at 0:34 | history | answered | pabouk - Ukraine stay strong | CC BY-SA 3.0 |