Hi all,
I've got a server console connected to my FreeBSD desktop via serial cable and run a command like
to get to the console - all good. However, every few months or so, the serial port seems to get screwed up and no data is transmitted anymore. When I kill "cu" and start it again, I get a local echo, nothing else. It's a local problem, though, because it works again after rebooting the desktop.
Every time this has happened so far, I haven't had the time to debug properly because I needed the console working ASAP so I rebooted my desktop. Things I've checked so far:
Thanks,
--Christina
I've got a server console connected to my FreeBSD desktop via serial cable and run a command like
Code:
cu -l /dev/cuau0 -s 115200
to get to the console - all good. However, every few months or so, the serial port seems to get screwed up and no data is transmitted anymore. When I kill "cu" and start it again, I get a local echo, nothing else. It's a local problem, though, because it works again after rebooting the desktop.
Every time this has happened so far, I haven't had the time to debug properly because I needed the console working ASAP so I rebooted my desktop. Things I've checked so far:
- There's no other process on /dev/cuau0 or /dev/ttyu0 that would lock the port.
- The server doesn't use hardware flow control, only XON/XOFF, and I've had no indications that hardware flow control had been turned on somehow when this happened.
Thanks,
--Christina