From owner-freebsd-current@FreeBSD.ORG Fri May 14 11:17:19 2004 Return-Path: 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 9E1DB16A4CE; Fri, 14 May 2004 11:17:19 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4901443D58; Fri, 14 May 2004 11:17:19 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) i4EIHI7Z031736; Fri, 14 May 2004 11:17:18 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i4EIHIsH031735; Fri, 14 May 2004 11:17:18 -0700 (PDT) (envelope-from dillon) Date: Fri, 14 May 2004 11:17:18 -0700 (PDT) From: Matthew Dillon Message-Id: <200405141817.i4EIHIsH031735@apollo.backplane.com> To: John Baldwin References: <40A3C047.80804@volja.net> <200405131550.28566.jhb@FreeBSD.org> <40A49439.9080409@volja.net> <200405141138.09168.jhb@FreeBSD.org> cc: freebsd-current@freebsd.org cc: Android66 Subject: Re: BTX halted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 May 2004 18:17:19 -0000 :> :> BTW, if it's not a bother, what does the code below actually do? I don't :> speak asm so I can't tell what are the bad things that my BIOS does :) : :It tries to see if it is running in protected mode with paging enabled so it :can walk the page tables to extract physical addresses for its DMA. The vm86 :monitor that our boot code uses doesn't let the BIOS read the page table :pointer register (%cr3) so it blows up. : :-- :John Baldwin <>< http://www.FreeBSD.org/~jhb/ :"Power Users Use the Power to Serve" = http://www.FreeBSD.org I wonder if this is related to random BTX faults I get on my Athlon 64 3200+ boxes. We're using the 5.x boot loader for DFly. Most of the time the boot loader is able to load and boot the kernel, but about 20% of the time (more if I don't have a keyboard plugged in) it fails with a BTX fault in random places, before it even gets to the menu. It's very non-deterministic. Most of the time its fine, some times it fails on cold boot, sometimes it fails after a reset button boot, sometimes it fails after a 'reboot'. Once the kernel is running everything always works dandy, and it happens to both of my Shuttle (FN85 MB) boxes, but never on my tower (K8V MB) box, so I am positive it isn't a hardware issue. -Matt