From owner-freebsd-questions Wed Nov 19 15:20:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA11470 for questions-outgoing; Wed, 19 Nov 1997 15:20:57 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA11451 for ; Wed, 19 Nov 1997 15:20:50 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA25154; Wed, 19 Nov 1997 15:14:41 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd025150; Wed Nov 19 15:14:35 1997 Message-ID: <3473725E.237C228A@whistle.com> Date: Wed, 19 Nov 1997 15:12:30 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Doug White CC: Brian Somers , Jonathan Chen , freebsd-questions@FreeBSD.ORG Subject: Re: Kernel panic in 2.2.2R with ppp References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I fixed a bug in the routing socket code that had this set of symptoms. it is fixed in 2.2.5 the symptom is a fault at the beginning of a page (e.g.0xf057a000) with a networking program that sets the default route (e.g. ppp). 2.2.2 had this problem. Doug White wrote: > > On Wed, 19 Nov 1997, Brian Somers wrote: > > > Seriously, as you already suspect, it can't really be ppp that's > > causing the problem. I'd suspect a memory problem. Is the > > instruction pointer the same each time ? If so, the only way to > > diagnose this is to rebuild your kernel with symbols (-g), wait for > > it to crash again, and try to find out where the instruction pointer > > is pointing. > > Whihc of these should I be looking at? Using `nm /kernel | grep xxx', the > fault virtual addr doesn't point to anything but the instruction pointer > is in the middle of the msdosfs code. > > > > > Fatal trap 12: page fault while in kernel mode > > > > fault virtual address = 0xf057a000 > > > > fault code = supervisor read, page not present > > > > instruction pointer = 0x8:0xf013d087 > > > > stack pointer = 0x10:0xefbffd80 > > > > frame pointer = 0x10:0xefbffd9c > > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > > = DPL 0, pres 1, def32 1, gran 1 > > > > processor eflags = interrupt enabled, resume, IOPL = 0 > > > > current process = 24356 (ppp) > > > > interrupt mask = > > > > panic: page fault > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major