From owner-freebsd-stable Tue May 12 16:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21120 for freebsd-stable-outgoing; Tue, 12 May 1998 16:19:16 -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 QAA21100; Tue, 12 May 1998 16:19:03 -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 RAA23271; Tue, 12 May 1998 17:01:47 -0600 (MDT) Date: Tue, 12 May 1998 17:01:47 -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: <199805122214.XAA06336@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Ok, I've played some more and even compiled and installed the ppp from -current. This is definately a case of PPP doing something the kernel doesn't like. I haven't had this machine (yet) do anything else I'd define as wierd. In fact, it feels more stable than any other box I've installed recently. Let me ask these two questions: 1) What EXACTLY is the best way to get MAXIMUM verbosity out of PPP, preferably to the console, so we can tell where this thing is locking? 2) Do you have a quick and dirty answer to the question of how to best do a debuging session which will likely get us near what this thing is doing which is locking this box? - 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