Date: Wed, 7 Jan 2004 13:07:40 -0500 From: "Will Saxon" <WillS@housing.ufl.edu> To: <obrien@freebsd.org> Cc: freebsd-amd64@freebsd.org Subject: RE: AMD64 support in 5.x versions Message-ID: <0E972CEE334BFE4291CD07E056C76ED8DB368C@bragi.housing.ufl.edu>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0E972CEE334BFE4291CD07E056C76ED8DB368C>