From owner-freebsd-hackers Tue Oct 22 12: 8:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E7B137B401; Tue, 22 Oct 2002 12:08:58 -0700 (PDT) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id C449E43E6A; Tue, 22 Oct 2002 12:08:57 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0482.cvx21-bradley.dialup.earthlink.net ([209.179.193.227] helo=mindspring.com) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1844Oe-00060W-00; Tue, 22 Oct 2002 12:08:56 -0700 Message-ID: <3DB5A201.BF8B34C1@mindspring.com> Date: Tue, 22 Oct 2002 12:07:45 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: hackers@FreeBSD.org, Diego Wentz Antunes Subject: Re: Kernel Panic Problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > Panic #1: > > --- > > > > Is this a full backtrace? I don't see any way that the stack > > could have started with "trap_pfault"... it had to be running > > something to cause a page fault. > > It's a fault from userland perhaps. Panic #3 was a fault in userland, and it showed the process in the stack backtrace. This one also isn't, because the 'usermode' argument to trap_pfault is 0. > > Panic #2: > > --- > >#9 0xc02607aa in generic_bcopy () > >#10 0xc0247c30 in scstart (tp=0xc0879b00) at ../../dev/syscons/syscons.c:1285 [ ... ] > generic_bcopy() is an asm function which may not have a full frame. > Thus, when gdb walks back over the stacktrace, it may skip the frame > that called generic_bcopy() and go to the previous frame. ddb sometimes > does a better job with backtraces for some reason. This is a good point. He should take a backtrace from ddb, at the time of the panic. There is still the little problem of the line numbers not matching the FreeBSD source code. If he can't provide at least a CVS timestamp to use to check out a source tree identical to his, I'm feeling pretty strongly that he's running with local modifications that he's not telling us about, and that these modifications are likely the source of his problem. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message