From owner-freebsd-hackers Wed Apr 30 08:41:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA02260 for hackers-outgoing; Wed, 30 Apr 1997 08:41:19 -0700 (PDT) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA02252 for ; Wed, 30 Apr 1997 08:41:13 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.6.12/8.6.5) with ESMTP id LAA01584 for ; Wed, 30 Apr 1997 11:35:29 -0400 Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id LAA00303 for ; Wed, 30 Apr 1997 11:40:32 -0400 (EDT) Message-Id: <199704301540.LAA00303@bmcgover-pc.cisco.com> To: hackers@freebsd.org Subject: PPPd oddity when changing baud rate Date: Wed, 30 Apr 1997 11:40:32 -0400 From: Brian McGovern Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok. Heres a weird one for you. I'm hoping someone can shed some light on my rapidly diminishing sanity. I'm working on a serial driver, and things are looking good in character mode via kermit, and PPP at the default baud rate (9600). What I'm seeing, however, is that if I change the baud rate for the link, pppd doesn't get around to setting the new baud rate until just after it gets an LCP:timout sending Config-Requests (or so says debugging with GDB), and it breaks down the call. I'm also seeing numerous reads and writes to the device before the baud-rate call is made, so I'm fairly confident that its not just the timing of the debugger tripping the LCP timeout. My code for ioctl is copied virtually from the SIO driver, so I'm fairly confident that I'm linking in at all the right places. In any event, I've run out of ideas. It appears to work ok with the SIO driver, so I suspect I'm just doing something stupid. Anyone care to comment? -Brian