From owner-freebsd-current Sun Mar 4 1:19:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E849937B718; Sun, 4 Mar 2001 01:19:44 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA13671; Sun, 4 Mar 2001 20:19:42 +1100 Date: Sun, 4 Mar 2001 20:19:31 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: RE: Problem with sio in -current ... possible cause of hangs? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Mar 2001, John Baldwin wrote: > On 03-Mar-01 The Hermit Hacker wrote: > > If I plug my cable from /dev/ttyd0 -> /dev/ttyd1 on the same > > machine, run getty on /dev/ttyd1 and use kermit to connect to /dev/cuaa0, > > I get no response back, which is why I'm wondering about sio ... > > Try turning clocal off on the host and port you are running kermit on. Even Or just use /dev/cuaa*. > then, I still have yet to get getty to work at all, it's always stuck in > 'siodcd'. I've noticed via debugging output that the DCD change bit does raise > for a read, but that teh DCD status bit stays at zero the entire time. The This seems to indicate a cabling problem. DCD and DCD change shouldn't change for a read; they should only change when "carrier" changes. > sio driver seems to ignore the change bit and only read the status bit, so it > thinks DCD is never raised and hangs forever on open. Note that I can get a Very short transients in DCD would be missed by the driver. The DCD change bit is for not missing transients, but in normal modem applications missing transients is probably a feature. Anyway, it's not clear what state change should occur in the driver if the DCD state hasn't changed when the driver looks at it. > getty fine on a serial console, just not on a /dev/ttydX that's not also the > serial console. :( I've had this problem since before PRE_SMPNG however. Certainly a hardware problem :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message