From owner-freebsd-current Sat Dec 13 17:44:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA09133 for current-outgoing; Sat, 13 Dec 1997 17:44:19 -0800 (PST) (envelope-from owner-freebsd-current) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA09093 for ; Sat, 13 Dec 1997 17:44:08 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.1/nospam) with UUCP id CAA28064; Sun, 14 Dec 1997 02:43:26 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id CAA02108; Sun, 14 Dec 1997 02:41:35 +0100 (CET) Message-ID: <19971214024134.PL39369@@> Date: Sun, 14 Dec 1997 02:41:34 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: tlambert@primenet.com (Terry Lambert) Cc: totii@est.is (?or?ur Ivarsson), pb@fasterix.freenix.org, freebsd-current@FreeBSD.ORG Subject: Re: panics when stopping pppd References: <3492A8DE.27B270DB@est.is> <199712132150.OAA03369@usr06.primenet.com> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <199712132150.OAA03369@usr06.primenet.com>; from Terry Lambert on Dec 13, 1997 21:50:21 +0000 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: [ crash when disconnecting PPP ] > If you have a local ethernet, look at the variables that exist on your > stack to see if your local ethernet MAC address is there somewhere; > this looks remarkably similar to a crash I saw, but have not yet been > able to reproduce. I have a local ethernet, but apparently no MAC address on the stack (I might have missed it though). On the other hand, I can reproduce the crash almost at will. It happens only when I have dynamic routes _and_ they are removed when PPP is down; if I stop gated before I stop PPP, there is no crash at all even when gated routes are removed. If I spray a few printf in the rtrequest code for RTM_DELETE to figure out what happens, it doesn't crash anymore. There might be a race condition somewhere. rtrequest() appears to at least sometimes return with an error before crashing, because in_ifadownkill managed to log the following once (from strings vmcore | tail -100): <4>in_ifadownkill: error 3 The instruction pointer is 0x6e655000 every time I've been able to see it: instruction pointer = 0x8:0x6e655000 stack pointer = 0x10:0xf4d4cd74 frame pointer = 0x10:0xf4d4cdb0 -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org