From owner-freebsd-current  Thu Jun  5 02:41:03 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA05464
          for current-outgoing; Thu, 5 Jun 1997 02:41:03 -0700 (PDT)
Received: from shadows.aeon.net (bsdcur@[194.100.41.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05458
          for <current@freebsd.org>; Thu, 5 Jun 1997 02:41:00 -0700 (PDT)
Received: (from bsdcur@localhost)
          by shadows.aeon.net (8.8.5/8.8.3) id MAA27014
          for current@freebsd.org; Thu, 5 Jun 1997 12:40:14 +0300 (EET DST)
From: mika ruohotie <bsdcur@shadows.aeon.net>
Message-Id: <199706050940.MAA27014@shadows.aeon.net>
Subject: Re: page fault
In-Reply-To: <19970604174918.CS56609@uriah.heep.sax.de> from J Wunsch at "Jun 4, 97 05:49:18 pm"
To: current@freebsd.org
Date: Thu, 5 Jun 1997 12:40:12 +0300 (EET DST)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > yes, but i failed to get kernel -g:ed. i guess after this i'll use
> > the 'config -g' as default.
> Be careful to not accidentally load this bloated kernel into
> memory. :) Also, i found the time ld(1) requires to link a full -g

it's only about 9 mgs. why not? it's still less than what win95/nt4.0
eats when started... besides, i didnt notice slowing (which it probably
causes). memory is cheap.

> the same optimization level), but add -g.  NB: you gotta replace the
> COPTS ?= line by an absolute one.  Then, i remove the .o files i wanna
> force to rebuild, and just rebuild this part of the kernel.  After
> this, you can usually analyze the stacktrace.

hmm, but you still need to know which .o's you need to nuke, and for
a person without the internal knowledge it's hard to decide... so i
think i can afford running 9 meg kernels if it helps me to track down
what crashed. and wouldnt i fuck up the recompiling anyway if i've
cvsup:ed after i did the kernel? (i cvsup far more often than i
make worlds/kernels)

btw, last time my machine crashed on this:

#0  boot (howto=256) at ../../kern/kern_shutdown.c:265
#1  0xf011521a in panic (fmt=0xf01c712f "page fault")
    at ../../kern/kern_shutdown.c:392
#2  0xf01c7d8a in trap_fatal (frame=0xf503abe0) at ../../i386/i386/trap.c:754
#3  0xf01c7839 in trap_pfault (frame=0xf503abe0, usermode=0)
    at ../../i386/i386/trap.c:661
#4  0xf01c74bb in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 790, 
      tf_esi = -266200876, tf_ebp = -184352768, tf_isp = -184308728, 
      tf_ebx = 784, tf_edx = 0, tf_ecx = 513, tf_eax = -266200865, 
      tf_trapno = 12, tf_err = 2, tf_eip = -267370964, tf_cs = 8, 
      tf_eflags = 66178, tf_esp = 790, tf_ss = -266200876})
    at ../../i386/i386/trap.c:319
#5  0xf0103e2c in cd9660_getattr (ap=0x0)
    at ../../isofs/cd9660/cd9660_vnops.c:253

it doesnt list more. but, the thing got my eye is the fact i do _not_
have cdrom attached, it's few miles from the machine currently. sure,
the kernel has support, but... is that suspicious?

it was crashed by httpd-requests from the win95 machine (it works
about every time too)

since connection attempts from local ether win95 seem to crash my
machine repeatedly, should i assume it's _hardware_-related?

> cheers, J"org


mickey