From owner-freebsd-current@FreeBSD.ORG Tue Aug 12 04:54:24 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 0B44537B401 for ; Tue, 12 Aug 2003 04:54:24 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26A3E43F75 for ; Tue, 12 Aug 2003 04:54:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfigt.dialup.mindspring.com ([165.247.202.29] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19mXjI-0000JM-00; Tue, 12 Aug 2003 04:54:21 -0700 Message-ID: <3F38D515.2950D743@mindspring.com> Date: Tue, 12 Aug 2003 04:52:53 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bosko Milekic References: <20030811100549.GA33392@technokratis.com> <20030811130937.GA34564@technokratis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a45f54e9a7ad514a79f9d74a9195328b8a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: Mark Johnston cc: current@freebsd.org Subject: Re: 5.1, Data Corruption, Intel, Oh my! [patch] - Fatal trap 12 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: Tue, 12 Aug 2003 11:54:24 -0000 Bosko Milekic wrote: > > db> trace > > _mtx_lock_flags(0,0,c07aa287,11e,c0c21aaa) at _mtx_lock_flags+0x43 > > vm_fault(c102f000,c0000000,2,0,c08205c0) at vm_fault+0x2b4 > > trap_pfault(c0c21b9e,0,c00004d8,100000,c00004d8) at trap_pfault+0x152 > > trap(6c200018,10,1bc40060,1c,0) at trap+0x30d > > calltrap() at calltrap+0x5 > > --- trap 0xc, eip = 0x5949, esp = 0xc0c21bde, dbp = 0xc0c21be4 --- > > (null)(1bf80058,0,530e0102,80202,505a61) at 0x5949 > > db> FWIW: This is a NULL function pointer that's trying to call a function that hasn't been initialized, or has been explicitly NULL'ed out. Decoding the pointer values to find out what the object are would probably go a long way toward knowing what's going on. Last time I saw one of these, it was the NFS lease function. He might also want to look for any function pointer that takes 5 arguments; Linux threads is a likely suspect, in that the thread mailboxes are at a fixed location, so he should make sure to recompile any kernel modules when he compiles his new kernel. BTW: Good work on the patch, both you and Peter! -- Terry