"cu: Got hangup signal" on sio0 probe

[Jeremy Chadwick]

On Thu, May 10, 2007 at 12:19:27AM +0200, Jeremie Le Hen wrote:
> % obiwan:root# cat /boot.config 
> % -D
> % obiwan:root# grep ttyd0 /etc/ttys  
> % ttyd0   "/usr/libexec/getty std.9600"   dialup  on secure
> 
> This works correctly but on startup, when the kernel probes sio0,
> I get "Got hangup signal".  Is it expected?

I wonder if that's some sort of reference to carrier detect being
wired wrong on whatever device or adapter you have connected to
your serial port.

However, I can't find this string referenced anywhere in the kernel
source code for RELENG_6.  An (admittedly bad) egrep shows:

$ egrep -r "Got .+ signal" /usr/src
/usr/src/contrib/amd/amd/nfs_start.c:    /* Got a signal */
/usr/src/usr.bin/make/job.c: *  Got a signal. Set global variables and hope that someone will
/usr/src/usr.sbin/bluetooth/bthidd/bthidd.c:    syslog(LOG_NOTICE, "Got signal %d, total number of signals %d",
/usr/src/usr.sbin/bluetooth/hcsecd/hcsecd.c:    syslog(LOG_DEBUG, "Got signal %d, total number of signals %d",
/usr/src/usr.sbin/bluetooth/sdpd/main.c:        log_notice("Got signal %d. Total number of signals received %d",

What version of FreeBSD are you referring to?

> I think I can understand
> this, but is there any way to workaround this?

Consider using uart(4) as a possible alternative, but depending upon
the answer to the above question, this might not be applicable.

I wrote some directions on how to get uart(4) to work, and one caveat I
found when attempting to use it.  Those docs are here:

http://jdc.parodius.com/freebsd_uart.txt

-- 
| Jeremy Chadwick                                    jdc at parodius.com |
| Parodius Networking                           http://www.parodius.com/ |
| UNIX Systems Administrator                      Mountain View, CA, USA |
| Making life hard for others since 1977.                  PGP: 4BD6C0CB |