From owner-freebsd-current@FreeBSD.ORG Fri Dec 5 23:53:29 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA24A1065672 for ; Fri, 5 Dec 2008 23:53:29 +0000 (UTC) (envelope-from nakaji@kankyo-u.ac.jp) Received: from www.heimat.gr.jp (unknown [IPv6:2001:3e0:a84::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4D5598FC08 for ; Fri, 5 Dec 2008 23:53:28 +0000 (UTC) (envelope-from nakaji@kankyo-u.ac.jp) X-Virus-Scanned: amavisd-new at heimat.gr.jp Received: from ra333.heimat.gr.jp.kankyo-u.ac.jp (ra333.heimat.gr.jp [IPv6:2001:3e0:a84:0:200:4cff:fe17:573c]) by www.heimat.gr.jp (8.14.3/8.14.3) with ESMTP id mB5NrLaq056547; Sat, 6 Dec 2008 08:53:22 +0900 (JST) (envelope-from nakaji@kankyo-u.ac.jp) From: NAKAJI Hiroyuki To: freebsd-current@freebsd.org References: <87zljb8nw6.fsf@roddy.4407.kankyo-u.ac.jp> <3a142e750812050613w4e9155bat950f03716aa58beb@mail.gmail.com> Date: Sat, 06 Dec 2008 08:53:21 +0900 In-Reply-To: <3a142e750812050613w4e9155bat950f03716aa58beb@mail.gmail.com> (Paul B. Mahol's message of "Fri, 5 Dec 2008 15:13:38 +0100") Message-ID: <863ah2qivi.fsf@ra333.heimat.gr.jp> User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, score=-6.1 required=13.0 tests=BAYES_00, CONTENT_TYPE_PRESENT,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on www.heimat.gr.jp Cc: Subject: Re: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 05 Dec 2008 23:53:29 -0000 Thanks for advice. I noticed I had just upgraded the kernel only and the userland remains old, that is, kernel is on Dec 3 while userland is on Oct 20. I'll do installworld too, after next buildworld, buildkernel, installkernel and reboot. And, I found same panic this morning (JST), but before I read Koshy's instruction, I typed 'reset' without doadump and I cannot show you a full bt. I'll do it when next panic. So, what I have to do are three: 1. Full upgrade to the latest kernel and userland (world) 2. Observe whether a panic occurs, and 3. When panic, save the crash dump and get full bt with kgdb I hope it will not reach to the step three. Thanks. >>>>> In <3a142e750812050613w4e9155bat950f03716aa58beb@mail.gmail.com> >>>>> "Paul B. Mahol" wrote: Paul> Full bt would be better, also make sure that world and kernel are in Paul> sync (because of recent libc changes). >>>>> In <84dead720812050840j28c95014wf76095c3d6def985@mail.gmail.com> >>>>> "Joseph Koshy" wrote: > > Fatal trap 12: page fault while in kernel mode > > cpuid = 0; apic id = 00 > > fault virtual address = 0x0 > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc0a57285 > > Why this occurs and what do I have to check? Koshy> The trap is being caused by a null pointer access. Koshy> You may want to take a full dump and use kgdb(1) to investigate the matter: Koshy> ddb> call doadump Koshy> ddb> reset Koshy> and after the reboot finishes, Koshy> # kgdb /boot/kernel/kernel /var/crash/vmcore.N Koshy> where "vmcore.N" is the name of the dump file saved by savecore(8). -- NAKAJI Hiroyuki