From owner-freebsd-questions  Mon Feb 11 18:13:32 2002
Delivered-To: freebsd-questions@freebsd.org
Received: from conn.mc.mpls.visi.com (conn.mc.mpls.visi.com [208.42.156.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id F0C1237B400; Mon, 11 Feb 2002 18:13:29 -0800 (PST)
Received: from bambi.visi.com (bambi.visi.com [209.98.98.24])
	by conn.mc.mpls.visi.com (Postfix) with ESMTP
	id 58F298199; Mon, 11 Feb 2002 20:13:29 -0600 (CST)
Received: by bambi.visi.com (Postfix, from userid 3058)
	id CAC635DC5C; Mon, 11 Feb 2002 20:13:28 -0600 (CST)
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>
References: <20020211234033.GA2588@visi.com> <20020211172804.D24535@blossom.cjclark.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020211172804.D24535@blossom.cjclark.org>
User-Agent: Mutt/1.3.27i
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

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