From owner-freebsd-stable Fri Apr 21 18:25:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id CE23A37BABA for ; Fri, 21 Apr 2000 18:25:45 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA00367; Sat, 22 Apr 2000 02:24:20 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA46234; Sat, 22 Apr 2000 02:24:33 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004220124.CAA46234@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: William Denton Cc: Brian Somers , stable@FreeBSD.org, brian@hak.lan.awfulhak.org Subject: Re: Serial port problems with 4.0 In-Reply-To: Message from William Denton of "Fri, 21 Apr 2000 16:53:14 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Apr 2000 02:24:31 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 21 April 2000, Brian Somers wrote: > > : Well, there's nothing responding at the other end.... I've no idea > : why not. Did you say you've got access to the other end ? What does > : physical logging say there ? > > I do work for the ISP I use, but they don't log anything before a login > happens. > > A friend suggested I see what happens with cu, in case the problem wasn't > with ppp but lower, and it turns out cu freezes after connecting, too. It > dials up, handshakes, connects, then just sits there. I tried cu on the > working system and got the the login prompt as usual. > > So neither ppp nor cu is able to see any data coming down from the other > end. Could this be a problem with the serial port drivers in 4.0? I've done a bit of testing here with a 4.0-stable and 5.0-current box and everything seems to be sane. Perhaps there's a problem between your modem and the ISP.... I think the only thing to do at this point is to swap bits in & out 'till you find the culprit. You could try booting an older kernel on your 4.0 box, and maybe even try another modem there. > Bill > -- > William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message