From owner-freebsd-current@FreeBSD.ORG Sat Aug 2 02:12:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C1D137B404 for ; Sat, 2 Aug 2003 02:12:25 -0700 (PDT) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9AE143FCB for ; Sat, 2 Aug 2003 02:12:24 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc17n.dialup.mindspring.com ([209.86.4.247] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19isR3-0006bd-00; Sat, 02 Aug 2003 02:12:21 -0700 Message-ID: <3F2B803C.21D38E0B@mindspring.com> Date: Sat, 02 Aug 2003 02:11:24 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Eivind Olsen References: <1079.192.168.0.3.1059811884.squirrel@webmail.aminor.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a42c1155bf859bdae7e04ca04527410e1e548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org Subject: Re: Yet another crash in FreeBSD 5.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2003 09:12:25 -0000 Eivind Olsen wrote: > Can anyone suggest what I do next to find out about this crash? > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x14 Dereference of NULL pointer; reference is for element at offset 0x14 in some structure; this is the equivalent of 5 32 bit ints or pointers into the structure. > db> trace > g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at g_dev_strategy+0x29 > launch_requests(c299bf00,0,10000,ffffffff,47) at launch_requests+0x448 > vinumstart(c5ada2d0,0,c22ab000,cfb5294c,c02e5bc6) at vinumstart+0x2b2 gdb -k kernel.debug (gdb) list *(g_dev_strategy+29) [ ... ] (gdb) list *(launch_requests+448) [ ... ] (gdb) list *(vinumstart+2b2) [ ... ] Will give you the exact source lines involved, assuming you built a debug kernel. You don't actually need a crash dump to debug a stack traceback. -- Terry