From owner-freebsd-mobile Mon Oct 6 10:32:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13522 for mobile-outgoing; Mon, 6 Oct 1997 10:32:35 -0700 (PDT) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA13516 for ; Mon, 6 Oct 1997 10:32:30 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id LAA14817; Mon, 6 Oct 1997 11:32:20 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA00767; Mon, 6 Oct 1997 11:32:19 -0600 (MDT) Date: Mon, 6 Oct 1997 11:32:19 -0600 (MDT) Message-Id: <199710061732.LAA00767@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John-Mark Gurney Cc: Nate Williams , mobile@freebsd.org Subject: Re: current on notebook (as of Oct 3) In-Reply-To: <19971006092448.15900@hydrogen.nike.efn.org> References: <19971006044227.01139@hydrogen.nike.efn.org> <199710061520.JAA00240@rocky.mt.sri.com> <19971006092448.15900@hydrogen.nike.efn.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > [ Moved to -mobile ] > > > > > well.. I'm running into some interesting problems... every other reboot > > > just before it prints the type of pcic chip it does (the PC-Card Intel line): > > > > > > Fatal trap 12: page fault while in kernel mode > > > fault virtual address = 0x80000008 > > > > I was seeing these last night until I updated *all* of my code. I'm not > > sure what caused it, but it happenned all the time with my new code > > changes. I suspect something in the interrupt code, but I never got a > > chance to verify it since the box is now solid with everything updated. > > ok... well.. the wierd part is this is from a tree of Oct 3rd... so > it's before your changes that you did yesterday... I was also having > problems with nfs hanging... but I completed the install by hand... This is typical of the types of problems I was seeing as well. Even after I backed out my pccard changes I still had problems, but I thought it may have had something to do with the changes I made in kern_intr to the printing (whY???), so I updated /sys/kern. Unfortunately, it made lots of changes I hadn't expected, so I updated my entire sys tree and re-built everything, which made all of the problems go away. I brought back my changes and things were still OK, so I'm calling it some sort of brokeness in the tree that is now fixed. Nate