From owner-freebsd-stable Tue May 12 21:01:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03245 for freebsd-stable-outgoing; Tue, 12 May 1998 21:01:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03180; Tue, 12 May 1998 21:00:47 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA14458; Wed, 13 May 1998 00:38:37 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805122338.AAA14458@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: "Forrest W. Christian" cc: Brian Somers , stable@FreeBSD.ORG, brian@FreeBSD.ORG Subject: Re: PPP hard lock in 2.2.6 In-reply-to: Your message of "Tue, 12 May 1998 17:01:47 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 May 1998 00:38:37 +0100 From: Brian Somers 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? At the ppp prompt: set log local async carrier ccp chat command connect debug hdlc id0 ipcp lcp link lqm phase tcp/ip > 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? This is tricky if the machine's just hanging.... See if it mis-behaves with a GENERIC kernel. If it does, help will be easier :-) Apart from that, it's a matter of trying to cause the crash with the minimum effort, then maybe sprinkling printf()s into the kernel in likely places 'till you hit something interesting... I'm not expert though. > - 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 > ---------------------------------------------------------------------- -- 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