Date: Sun, 24 Jun 2001 07:22:26 -0400 From: "Otter" <otterr@telocity.com> To: <cjclark@alum.mit.edu>, <freebsd-stable@freebsd.org> Subject: RE: /dev/console and Serial Device Problems Message-ID: <PCEGINJJIOIMLAAHJLIPGEKFCDAA.otterr@telocity.com> In-Reply-To: <20010624004514.A10875@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Crist,
This is something I've noticed recently also. I have a -stable machine
with source from June 9th, 2001. I tried using both cu AND kermit to
hook up to my Sun Sparcstation 5 to do a console install on it and my
FreeBSD box locks up tighter than a drum with both applications.
Because I had a few transfers going at the time and the FreeBSD
machine in question is my gateway, I scrapped the idea just to get the
thing back up and online by cycling power to the computer. I didn't
have time then to troubleshoot the problem, but I'm open to ideas and
can provide the time if anyone has any ideas.
-Otter
> -----Original Message-----
> From: owner-freebsd-stable@FreeBSD.ORG
> [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Crist J. Clark
> Sent: Sunday, June 24, 2001 3:45 AM
> To: freebsd-stable@freebsd.org
> Subject: /dev/console and Serial Device Problems
>
>
> I just started having some really odd problems with a
> -STABLE I built
> this afternoon. /dev/console seems to be blocking when I use the
> serial port. I noticed since syslogd(8) did not seem to be
> working. I
> brought it up in debug and it would get caught on the first
> entry with
> /dev/console and just stick there,
>
> # syslogd -ds -vv
> sending on inet and/or inet6 socket
> off & running....
> init
> cfline("*.err;kern.debug;auth.notice;mail.crit
> /dev/console", f, "*", "*")
> syslogd: /dev/console: Interrupted system call
> logmsg: pri 53, flags 4, from blossom, msg syslogd:
> /dev/console: Interrupted system call
>
> I removed all of the /dev/console lines one by one. Each time I ran
> syslogd(8) it would get caught at the next. It's now
> running fine with
> all /dev/console lines commented out.
>
> Just to see if it wasn't syslogd(8) I just did,
>
> # echo "hello" > /dev/console
>
> And it looked like I've hung that shell up hard.
>
> Then... I quit the tip(1) sesssion I had going in another window and
> the echo finished. I killed syslogd(8) and started it again with all
> of the console lines in place and it is fine...
>
> But now, if I try to start tip(1) again,
>
> # tip -9600 cuaa0c
> tip: /dev/cuaa0: Device busy
> link down
>
> Something seems broken. Note,
>
> # ls /var/spool/lock
> LCK..cuaa1
>
> That's the lock on the modem, not the line to the other
> machine which
> is on cuaa0. Also,
>
> # ls -ali /dev/cua*0 /dev/console /dev/tty*d0
> 6334 crw------- 1 root wheel 0, 0 Jun 24 00:38
> /dev/console
> 6814 crw-rw---- 1 uucp dialer 28, 128 Jun 24 00:28 /dev/cuaa0
> 6815 crw-rw---- 1 uucp dialer 28, 160 Jun 23 15:06 /dev/cuaia0
> 6816 crw-rw---- 1 uucp dialer 28, 192 Jun 23 15:06 /dev/cuala0
> 7374 crw------- 1 root wheel 28, 0 Jun 23 23:20 /dev/ttyd0
> 7375 crw------- 1 root wheel 28, 32 Jun 23 15:06 /dev/ttyid0
> 7376 crw------- 1 root wheel 28, 64 Jun 23 15:06 /dev/ttyld0
> # fstat | egrep '(cua.*|tty.*d)0'
> #
>
> Any ideas? Not being able to use tip(1) to access other machines via
> serial console is annoying.
> --
> Crist J. Clark cjclark@alum.mit.edu
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PCEGINJJIOIMLAAHJLIPGEKFCDAA.otterr>