From owner-freebsd-stable@FreeBSD.ORG Thu Apr 6 00:09:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D20E316A400 for ; Thu, 6 Apr 2006 00:09:52 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C70143D46 for ; Thu, 6 Apr 2006 00:09:52 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by pproxy.gmail.com with SMTP id o67so5672pye for ; Wed, 05 Apr 2006 17:09:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Zk4E8uwx5zmXiaTXx37s9h6/g6HPke6SILsKtHgqg/Fy2gYisNPfURHEwV78wPFdktjMH0+tsmr9+PJlF/N1LBmHkKAwig8dQEh6iq5SC8yYr0f/lRr75NNqPRzNKbpeFn8YRjZVnyUBcIDGHT2wLlj8rafRsexhgwvH5/2gFww= Received: by 10.35.101.9 with SMTP id d9mr295361pym; Wed, 05 Apr 2006 17:09:36 -0700 (PDT) Received: by 10.35.36.5 with HTTP; Wed, 5 Apr 2006 17:09:36 -0700 (PDT) Message-ID: <2a41acea0604051709v379c2cc0he5642f76494db8b@mail.gmail.com> Date: Wed, 5 Apr 2006 17:09:36 -0700 From: "Jack Vogel" To: "David Gilbert" In-Reply-To: <17460.22467.330090.949775@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17460.22467.330090.949775@canoe.dclg.ca> Cc: freebsd-stable@freebsd.org Subject: Re: Frustrating inability to boot amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2006 00:09:52 -0000 On 4/5/06, David Gilbert wrote: > At this point, I've been through 4 AMD64 motherboards. Commonly, > AE_BAD_CHARACTER stops ACPI (or apic?) from figuring out the system > --- this has happened on 3 out of four boards. On this latest board, > it can turn off APIC. If I do that, FreeBSD hangs after detecting the > disks. The only "wrong" thing on the screen is > > module_register_init: MOD_LOAD (amr_linux, 0xffffffff805ebcc0, 0) > error 6 > > I have tested boot CDs for amd64 from 6.0-RELEASE, 6.1-BETA1 and > 6.1-BETA4. None have successfully booted on these boards. > > Strangely enough, i386 boots fine, APIC and all. > > Dave. Whats the first thing anyone that might help you gonna need??? Motherboard details, chipset, memory, etc etc... :) I have two different amd64 systems, both have run FreeBSD 6 RELEASE, and one is running CURRENT, so its not the architecture in general thats broken. One last resort you might try, boot Failsafe, I've had that work when just turning off ACPI doesnt. Good luck,