From owner-freebsd-questions Wed Nov 19 17:33:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22935 for questions-outgoing; Wed, 19 Nov 1997 17:33:43 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22922 for ; Wed, 19 Nov 1997 17:33:38 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id XAA12010; Wed, 19 Nov 1997 23:31:17 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711192331.XAA12010@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Doug White cc: Brian Somers , Jonathan Chen , freebsd-questions@freebsd.org Subject: Re: Kernel panic in 2.2.2R with ppp In-reply-to: Your message of "Wed, 19 Nov 1997 10:12:04 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Nov 1997 23:31:17 +0000 From: Brian Somers Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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. So it sounds like that's the problem. As fs access is asyncronous, the ``current process'' is irrelevent - it's random, but weighted towards whatever's being scheduled the most (maybe someone was doing a transfer to/from an MSDOS partition over the ppp link). Perhaps using mtools for a while instead of mounting any DOS partitions and seeing if the problem goes away may be in order. > > > > 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 > > -- Brian , , Don't _EVER_ lose your sense of humour....