Re: serial ttys broken?

On Tue, 2005-09-20 at 20:26 +0300, Ruslan Ermilov wrote:
> On Tue, Sep 20, 2005 at 04:39:53PM +0100, Gavin Atkinson wrote:
> > On Tue, 2005-09-20 at 18:30 +0300, Ruslan Ermilov wrote:
> > > On Tue, Sep 20, 2005 at 07:27:13AM -0700, othermark wrote:
> > > > Poul-Henning Kamp wrote:
> > > > > In message <20050920110023.GA468_at_ip.net.ua>, Ruslan Ermilov writes:
> > > > > 
> > > > >>I have the following issues with serial on today's -CURRENT:
> > > > > 
> > > > > Hmm, my box runs just as fine as always with serial console.
> > > > > 
> > > > >>2) If booted with -h, as most people are doing, but without
> > > > >>   the recently added -S option to boot2, serial console
> > > > >>   works in 9600 bps as advertised, but despite std.9600 in
> > > > >>   /etc/ttys, the speed is set to 115200.
> > > > >>
> > > > >>My configuration is pretty much GENERIC.  Rumors are that these
> > > > >>issues aren't new.
> > > > > 
> > > > > This is the first I hear about them...
> > > > > 
> > > > > I won't have time to look at it for the next several weeks
> > > > > (unless it happens on my machine and forces me to handle it).
> > > > > 
> > > > 
> > > > I probably should have piped up on -current, but yes, serial console is
> > > > 'different' after the recent changes went into the boot loader.
> > > > 
> > > > -P  in /boot.config and the following in /etc/make.conf
> > > > 
> > > > BOOT_COMCONSOLE_PORT=0x3F8
> > > > BOOT_COMCONSOLE_SPEED=115200
> > > > 
> > > > used to be enough for my boxes to work, but now (of course, only after a
> > > > installworld for the bootloader) the following in /boot/loader.conf
> > > > 
> > > > console=comconsole
> > > > comconsole_speed=115200
> > > > 
> > > > seems to be required for serial console to work.
> > > > 
> > > Serial console aside, can you PLEASE verify that you can get
> > > getty(8) working on the first serial port if it is NOT set up as
> > > a serial console?  That is, with an empty /boot.config and
> > > default syscons console, can you get a login: prompt on a
> > > serial port?  I cannot, on neither of my -current machines,
> > > nor i386 nor amd64.  People I asked around report the same.
> > 
> > In my experience, you need to use:
> > 
> > cuad0   "/usr/libexec/getty std.9600"   dialup  on secure
> > and not
> > ttyd0   "/usr/libexec/getty std.9600"   dialup  on secure
> > 
> > in /etc/ttys to get a console on the serial port if you are not using -h
> > in /boot.config.  I'm pretty sure it's been like this for a long time.
> > 
> > What line have you got in /etc/ttys?
> > 
> I've come to the same conclusion after also trying uart(4) instead
> of sio(4).  Odd, but I can confirm that getty works on cua* devices
> while tty* do not.  Also, if at the getty prompt I press <Enter>
> quickly, I consistently get the garbage.  Do you also see it?

FreeBSD/i386 (buffy.york.ac.uk) (ttyd0)

login:
FreeBSD/i386 (buffy.york.ac.uk) (ttyd0)

login: HWV*Q)kB
               BJjHVKCCeeBSD/i386 (buffy.york.ac.uk) (ttyd0)

login:
FreeBSD/i386 (buffy.york.ac.uk) (ttyd0)

login: CCreeBSD/i386 (buffy.york.ac.uk) (ttyd0)

login:
FreeBSD/i386 (buffy.york.ac.uk) (ttyd0)

login: CCeeBSD/i386 (buffy.york.ac.uk) (ttyd0)

login:


Yes.

And that's with ttyd0, not cuaa0, and a Windows machine at the far end
of a 9600 baud link.  A configuration which I'm pretty sure should
perform better.  No matter how hard I try, I can't manage to reproduce
the corruption once logged in, unless I explicitly
run /usr/libexec/getty from the shell, in which case the corruption is
even worse:

loi:cCreeBSDi36(ff.or.c.(tt0

loi:
reeBSDi36(ff.or.c.(tt0

loi:
reeBSDi36(ff.or.c.(tt0

loi:
reeBSDi36(ff.or.c.(tt0loi:
reeBSDi36(ff.or.c.(tt0

loi:cCeeBSDi36(ff.or.c.(tt0


Guess there may be some issue with getty?

Gavin