From owner-freebsd-stable Tue May 12 22:45:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16142 for freebsd-stable-outgoing; Tue, 12 May 1998 22:45:38 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from workhorse.iMach.com (forrestc@workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16087; Tue, 12 May 1998 22:45:11 -0700 (PDT) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.8.8/8.8.8) with SMTP id XAA24458; Tue, 12 May 1998 23:27:51 -0600 (MDT) Date: Tue, 12 May 1998 23:27:51 -0600 (MDT) From: "Forrest W. Christian" To: Brian Somers cc: stable@FreeBSD.ORG, brian@FreeBSD.ORG Subject: Re: PPP hard lock in 2.2.6 In-Reply-To: <199805122338.AAA14458@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Some more information.... After spewing the very long debug line into the ppp config ppp locks even more reliably. It seems to always lock at the following point: Chat: Sending: ATE1Q0 Chat: Expecting: OK Chat: Wait for (5): OK If I run ppp inside of ktrace, I get one more line, usually: Connect: The unusual thing is that previously it would lock at somewhat random points - sometimes it would connect and then die, sometimes it would die before I could type DIAL. For everyone's information, here's what I have here: Pentium 133 32MB SDRAM TX Chipset Motherboard (epox) PCI Ethernet Card (NE2000 clone) PCI Trident Video Card Internal USR 56K Sporster on /dev/cuaa1 Built in com1 on /dev/cuaa0 Built in com2 disabled 2G WD Hard drive (IDE) And probably something else which is really important to mention. Things I've tried: Latest PPP from -current crashes Generic 2.2.6 kernel crashes This is basically an out-of-the-box setup. When it crashes it hard locks the machine. No alt-keys, no lock light toggling, no pings to the ethernet card, etc. etc. Basically a hard reset or power cycle is required to bring the machine back to life. - Forrest W. Christian (forrestc@imach.com) ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message