From owner-freebsd-current@FreeBSD.ORG Fri May 14 08:53:25 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 759B416A4CE for ; Fri, 14 May 2004 08:53:25 -0700 (PDT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0702F43D4C for ; Fri, 14 May 2004 08:53:25 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 27520 invoked from network); 14 May 2004 15:37:51 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 14 May 2004 15:37:51 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4EFbfP4027150; Fri, 14 May 2004 11:37:42 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Fri, 14 May 2004 11:38:09 -0400 User-Agent: KMail/1.6 References: <40A3C047.80804@volja.net> <200405131550.28566.jhb@FreeBSD.org> <40A49439.9080409@volja.net> In-Reply-To: <40A49439.9080409@volja.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405141138.09168.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx 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 15:53:25 -0000 On Friday 14 May 2004 05:41 am, Android66 wrote: > Hi! > > Thanks! Disabling DMA works. > > Also, I tried booting from a 4.9 CD and floppies (4.9 and 5.2.1-RELEASE) > and I got the same error. I have disabled everything ACPI related but to > no avail. > > 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