Date: Mon, 11 Feb 2002 21:49:59 -0800 From: "Crist J. Clark" <crist.clark@attbi.com> To: Stephen <sdk@shell.yuck.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 4.4-R cuaa Device busy Message-ID: <20020211214959.F24535@blossom.cjclark.org> In-Reply-To: <20020212021328.GA2941@visi.com>; from sdk@shell.yuck.net on Mon, Feb 11, 2002 at 08:13:28PM -0600 References: <20020211234033.GA2588@visi.com> <20020211172804.D24535@blossom.cjclark.org> <20020212021328.GA2941@visi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 11, 2002 at 08:13:28PM -0600, Stephen wrote:
> 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?
Just to be thorough first, you _did_ check for locks left behind by a
previous tip(1) run in /var/spool/lock/?
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
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?20020211214959.F24535>