From owner-freebsd-bugs Wed Apr 24 22:51:30 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA17696 for bugs-outgoing; Wed, 24 Apr 1996 22:51:30 -0700 (PDT) Received: from irz201.inf.tu-dresden.de (irz201.inf.tu-dresden.de [141.76.1.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA17685 for ; Wed, 24 Apr 1996 22:51:24 -0700 (PDT) Received: from sax.sax.de by irz201.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA24441; Thu, 25 Apr 1996 07:50:57 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id HAA03317; Thu, 25 Apr 1996 07:50:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA00914; Thu, 25 Apr 1996 07:05:35 +0200 (MET DST) From: J Wunsch Message-Id: <199604250505.HAA00914@uriah.heep.sax.de> Subject: Re: Bug report To: freebsd-bugs@FreeBSD.org (FreeBSD bugs list) Date: Thu, 25 Apr 1996 07:05:34 +0200 (MET DST) Cc: gary@systemics.com (Gary Howland) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <317EA7F1.41C67EA6@systemics.com> from "Gary Howland" at Apr 25, 96 00:15:13 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Gary Howland wrote: (Btw, was it your intention to write in ISO-8859-2?) > Now when I boot > I get a "page fault in kernel mode" consistently just after finding > the SCSI cdrom. It seems to be complaing about my "vga0 - pci:14" > card, although a trace shows a listing of scsi probes. I haven't > included the trace since I couldn't be bothered to write it down > (since I can reproduce the error at will). Catching the trace is easy if you've got a second computer you can use as a serial terminal (e.g. with kermit). Hook it up onto your first serial line (ttyd0/COM1:), setup kermit for 9600 baud, and enable session logging. As soon as the ``boot:'' prompt appears, enter `-h'. This will turn your kermit session into the system console. I think you can compile a kernel, right? Could i convince you to read the section about kernel debugging in the handbook, and try to build a kernel with DDB enabled? Of course, this will only be useful if you can log your session, so you could mail or post relevant traces. This should give you at least a stack trace of where the system crashes. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)