Date: Fri, 11 May 2001 10:39:30 +0100 From: Nick Barnes <Nick.Barnes@pobox.com> To: freebsd-questions@freebsd.org Subject: Cyclades serial devices busy Message-ID: <2890.989573970@thrush.ravenbrook.com>
next in thread | raw e-mail | index | archive | help
I am running 3.3-RELEASE on a machine acting as a RAS, with a 16-port Cyclades serial box and a bunch of modems. Sometimes after a power-cycle, one or more of the serial devices appears as "busy". I can't cu to them or run comcontrol on them, and coming in through the modem I don't get a login prompt even though the getty is running. Something somewhere in the system has got the device and won't relinquish it. There doesn't seem to be any way of reclaiming it apart from rebooting. Today I had an example of this on ttyc01/cuac01. Trying to track down the culprit I turned off the getty (in /etc/ttys, then kill -1 1). So in theory at that point nothing in the system is interested in that serial port. But I was still getting this kind of thing: > # comcontrol /dev/cuac01 > comcontrol: couldn't open file /dev/cuac01: Device busy > # cu -l /dev/cuac01 -s 57600 > cu: open (/dev/cuac01): Permission denied > cu: /dev/cuac01: Line in use Any ideas? I've had this before on regular serial lines as well, but the Cyclades lines seem more prone to it. Nick B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2890.989573970>