From owner-freebsd-current  Thu Oct  8 08:16:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA14086
          for freebsd-current-outgoing; Thu, 8 Oct 1998 08:16:48 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14077
          for <freebsd-current@FreeBSD.ORG>; Thu, 8 Oct 1998 08:16:42 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA25214;
	Fri, 9 Oct 1998 01:16:34 +1000
Date: Fri, 9 Oct 1998 01:16:34 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199810081516.BAA25214@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.ORG, ghelmer@scl.ameslab.gov
Subject: Re: Kernel backtrace for recurring page fault panic
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>I finally have a backtrace for a page fault panic that has been bothering
>me under -current for months (it only happens when I use cvsup); this
>kernel was built from current sources on October 2.  It appears that there
>are two page faults, the first occuring in tulip_txput and the second in
>tsleep.  Is this of value to the kernel gurus? 

I think this panic was reported by someone else.  tulip_txput() calls
vtophys() on an invalid address for some unknown reason.  The pagefault in
tsleep() is not interesting (sync() can not be called from an interrupt
handler).

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message