From owner-freebsd-current Sat Mar 15 20:27: 4 2003 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 317B537B401 for ; Sat, 15 Mar 2003 20:27:03 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A61543F3F for ; Sat, 15 Mar 2003 20:27:02 -0800 (PST) (envelope-from wa1ter@myrealbox.com) Received: from myrealbox.com wa1ter@smtp-send.myrealbox.com [66.126.108.214] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.32 $ on Novell NetWare via secured & encrypted transport (TLS); Sat, 15 Mar 2003 21:27:01 -0700 Message-ID: <3E73FD1C.3010006@myrealbox.com> Date: Sat, 15 Mar 2003 20:27:08 -0800 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030213 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: GEOM_MBR breaks my kernel References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Poul-Henning Kamp wrote: > In message <3E71E323.5010808@myrealbox.com>, walt writes: > >>I've been unable to boot any kernel I've built since about March 11 >>and I've narrowed it down to the GEOM_MBR option. >> >>With GEOM_MBR I get a kernel page fault error when trying to >>mount the root filesystem at boot time. > Can you get us the messages and a traceback ? Well, no. I've been trying to find a kernel configuration that will allow me to reproduce the bug AND generate a traceback, but so far I can't find one. The problem is that just adding GEOM_MBR to a GENERIC kernel doesn't produce the bug. My normal custom kernel doesn't contain the debugging stuff, and if I start changing things the bug doesn't show. The only semi-interesting result I've come up with is this: I normally use only the 'cpu I686_CPU' flag because I have an Athlon cpu. But if I also include the 'cpu I586_CPU' flag the bug completely changes: the machine boots and the filesystems mount just fine but about ten seconds after I start X running the machine panics and reboots shortly thereafter. The panic message doesn't appear on the screen because the console is not visible at that point. Does this suggest a gcc problem? I've never really understood how more than one 'cpu' flag can be included in the kernel config file, so I'm not sure what actually changes when I do that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message