From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 7 10:08:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F87A16A4CE; Wed, 7 Jan 2004 10:08:08 -0800 (PST) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1738443D67; Wed, 7 Jan 2004 10:07:41 -0800 (PST) (envelope-from WillS@housing.ufl.edu) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Wed, 7 Jan 2004 13:07:40 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED8DB368C@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AMD64 support in 5.x versions Thread-Index: AcPVR58lj8d3K+GHS2Op9OGfdZmpkwAAYC/Q From: "Will Saxon" To: cc: Adriaan de Groot cc: "Michael J. Pelletier" cc: freebsd-amd64@freebsd.org Subject: RE: AMD64 support in 5.x versions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2004 18:08:08 -0000 Yes it looks like this exact problem with other broadcom chipsets was = 'fixed' around July. The firmware initialization is timing out so you = have to give it more time :). -Will > -----Original Message----- > From: David O'Brien [mailto:obrien@freebsd.org] > Sent: Wednesday, January 07, 2004 12:57 PM > To: Will Saxon > Cc: Adriaan de Groot; freebsd-amd64@freebsd.org; Michael J. Pelletier > Subject: Re: AMD64 support in 5.x versions >=20 >=20 > On Tue, Jan 06, 2004 at 10:43:54PM -0500, Will Saxon wrote: > > I downloaded the 5.2-RC2 AMD64 miniinst ISO to try on a MSI K8T800 > > based dual opteron system today. I found that the system=20 > panicked when > > I used ACPI, and without ACPI the onboard broadcom ethernet is not > > initialized correctly (something about return type/code of 6 I > > believe). This may or may not be AMD64 related. >=20 > I've seen this on quad Opteron servers in my lab, but I haven't had a > chance to keep one down (ie, not running Linux) for long=20 > enough to debug > it. The bge(4) maintainer suggested finding the delay=20 > statements in the > driver and adding another "0" to them. >=20