From owner-freebsd-current Thu Aug 1 6:14:57 2002 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 9090737B400 for ; Thu, 1 Aug 2002 06:14:52 -0700 (PDT) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2911943E5E for ; Thu, 1 Aug 2002 06:14:51 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwa@localhost [127.0.0.1]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id g71DEYY08828; Thu, 1 Aug 2002 22:14:34 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: michaelnottebrock@gmx.net Cc: freebsd-current@freebsd.org Subject: Re: kernel panic on boot, acpica related? In-Reply-To: <3D49307C.5050903@gmx.net> References: <3D49307C.5050903@gmx.net> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20020801221434X.iwasaki@jp.FreeBSD.org> Date: Thu, 01 Aug 2002 22:14:34 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 24 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 10.000 msec > > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x8:0xc4109ac1 > stack pointer = 0x10:0xd6855ce4 > frame pointer = 0x10:0xd6855d0c > code segment = base0x0, limit 0xfffff, type 0x16 > = DPL 0, pres 1, def 32, gran 1 > processor eflags = interrupt enabled, resume, IOPL=0 > current process = 21 (irq10:fxp0 sn0+++*) ^^^^^^^^^^^^^^^^^^^^ > kernel: type 9 trap, code=0 > Stopped at 0xc4109ac1: lcall $0xc410,0xa040c410 > db> trace > _end (c158d300,d6855d48,c04897b1,356,0) at 9xc4109ac1 > fork_exit (c02ae2c0,c158d300,d6855d48) at fork_exit+0xaf > fork_trampoline () at fork_trampoline+0x1a Hmmm, I don't think so. How about typing unset acpi_load in loader prompt, and see if this panic disappear or still happen? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message