Date: Mon, 11 Feb 2002 20:13:28 -0600 From: Stephen <sdk@shell.yuck.net> To: "Crist J. Clark" <cjc@FreeBSD.ORG> Cc: Stephen <sdk@shell.yuck.net>, freebsd-questions@FreeBSD.ORG Subject: Re: 4.4-R cuaa Device busy Message-ID: <20020212021328.GA2941@visi.com> In-Reply-To: <20020211172804.D24535@blossom.cjclark.org> References: <20020211234033.GA2588@visi.com> <20020211172804.D24535@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the response. No luck with what you suggested. I'm not running ppp, tip, or cu, and no hung processes. I use ttya for x10/firecracker, and use a program called bottlerocket to access the firecracker module. It's been working for years. A reboot will correct the problem for a day or so. Is it possible this is failing hardware? Stephen On Mon, Feb 11, 2002 at 05:28:04PM -0800, Crist J. Clark wrote: > On Mon, Feb 11, 2002 at 05:40:33PM -0600, Stephen wrote: > > Running: FreeBSD 4.4-RELEASE, and I can't find out what's using my serial > > a port. Nothings changed in /etc/ttys (ie, no console on serial a). > > No hanging processes. Ideas? Please cc to my email address. > > > > root# tip com1 > > tip: /dev/cuaa0: Device busy > > > > root# fstat /dev/cuaa0 > > USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME > > root# > > You can also try, > > /dev/cuaia0 > /dev/cuala0 > > /dev/ttyd0 > /dev/ttyid0 > /dev/ttyld0 > > But it is also possible for the device to be busy, but not open. Usual > culprits are getty(8), other tip(1) or cu(1) processes, and ppp(8). 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?20020212021328.GA2941>