Date: Fri, 16 Jul 2010 23:20:51 -0500 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: Bryan Vyhmeister <freebsd@bsdjournal.net> Cc: Peter Grehan <grehan@freebsd.org>, freebsd-ppc@freebsd.org Subject: Re: ANNOUNCE: powerpc64 now in -CURRENT Message-ID: <4C412FA3.6000405@freebsd.org> In-Reply-To: <AANLkTimo31AX_j-IAMSe38gHHZb6NfQAGVUN6JKGIPa1@mail.gmail.com> References: <20100713164320.40351367@anacreon.physics.wisc.edu> <B39EFC30-F914-48BF-8FEA-CCA49B2FB93E@freebsd.org> <4C40E3DB.2050305@freebsd.org> <AANLkTimo31AX_j-IAMSe38gHHZb6NfQAGVUN6JKGIPa1@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 07/16/10 19:19, Bryan Vyhmeister wrote: > On Fri, Jul 16, 2010 at 6:57 PM, Peter Grehan<grehan@freebsd.org> wrote: > >>> http://people.freebsd.org/~nwhitehorn/FreeBSD-9.0-20100715-SNAP-powerpc64 >>> >> This booted fine on the first (1.6GHz 7,2) and last (quad 2.5GHz 11,2) G5 >> towers. Now to try an install :) >> > Out of curiosity, how much memory was in each of these systems? I > think both of my systems have 4 GB of RAM. Could that make any > difference on the SATA side? > I don't think so, especially since drive detection is a PIO operation. My work desktop has 5.5 GB, and has performed well in daily use for several months now. I strongly suspect there is some kind of timeout in ATA device detection that is ever-so-slightly too short with some controllers, and that that is causing the problem here. -Nathanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C412FA3.6000405>