From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-ieee1394 i686) Description of problem: Setting clocal off on a serial port makes the port inaccessible and eventually panics the kernel How reproducible: Always Steps to Reproduce: 1.stty -a </dev/ttyS0 2.stty -clocal </dev/ttyS0 3.stty -a </dev/ttyS0 Actual Results: The second stty -a produced no output. User software which repeatedly tried to open() this port eventually caused kernel panic Expected Results: Second stty-a gives same results as second one except -clocal is reported Additional info: This bug was noticed whilst debugging Ricardo Fachetti's libmodem library. Software under development would crash prematurely leaving clocal off on the port. There are 2 ways to free the port - reboot or run minicom and killall it after it has opened the port.
unsetting clocal makes the open block until the attached device asserts the DCD signal. Could you supply details of the panic, and a method that causes it please? Thanks.
No reply in over a year, closing