From owner-freebsd-hackers Mon Apr 21 03:27:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04264 for hackers-outgoing; Mon, 21 Apr 1997 03:27:08 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA04245; Mon, 21 Apr 1997 03:27:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id DAA03554; Mon, 21 Apr 1997 03:28:51 -0700 (PDT) Message-Id: <199704211028.DAA03554@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Simon Shapiro cc: freebsd-hackers@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Mystery of the X11 Panic... In-reply-to: Your message of "Mon, 21 Apr 1997 00:31:25 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 21 Apr 1997 03:28:51 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Running 2.2.1-970415 and later, shortly after starting X11, while clicking ... >these problems. the better news is that I managed to catch this panic >while X11 was running: > >Fatal trap 12 - Page fault while in kernel mode. in virtual address >0xf71e0014. Tracing back shows that bash (?!) was the culprit, causing it >after calling _Xsyscall -> _syscall -> _vm_open -> _spec_open. > >Things go south at _spec_open + 0x6e, complaining about cmpl $0,0(%eax). > >Now, I am a pretty good shell programmer, but never lerned how to panic a >kernel with running a program on one :-) > >There is no explicit bash call on my part, to trigger the fault, but much >of the X11 activity forks and exec's all over the place. But you know that >already... > >Anyway, any help will be appreciated...! I must stabilize this kernel!!! This is almost certainly caused by the bug I fixed in kern_exec.c on April 18th. You say "-970415" and later...does this mean that you've updated your source in the past day or so? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project