From owner-freebsd-amd64@FreeBSD.ORG Thu May 12 18:50:05 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F17DE16A4D0 for ; Thu, 12 May 2005 18:50:05 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF2B143D7F for ; Thu, 12 May 2005 18:50:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4CIo5WN043425 for ; Thu, 12 May 2005 18:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4CIo5EX043424; Thu, 12 May 2005 18:50:05 GMT (envelope-from gnats) Date: Thu, 12 May 2005 18:50:05 GMT Message-Id: <200505121850.j4CIo5EX043424@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Niall Douglas" Subject: Re: amd64/80691: amd64 kernel hangs on load X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Niall Douglas List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2005 18:50:06 -0000 The following reply was made to PR amd64/80691; it has been noted by GNATS. From: "Niall Douglas" To: bug-followup@freebsd.org Cc: Kent Palmkvist Subject: Re: amd64/80691: amd64 kernel hangs on load Date: Thu, 12 May 2005 19:47:59 +0100 On 12 May 2005 at 15:53, Kent Palmkvist wrote: > I got a similar error as you when I tried my Acer Aspire 1522WLMi with > FreeBSD 5.3. It turned out to be a problem with the BIOS setup: There > was an entry to enable/disable USB legacy support. If I disabled this, > then FreeBSD booted correctly. Tried this, and it now works fine. Thank you very much for the tip. Point 1: There really should be an FAQ entry in the amd64 release notes specifying this problem and workaround Point 2: It's still a bug in the amd64 implementation as i386 works fine. Cheers, Niall