Date: Thu, 02 Dec 2010 13:45:37 -0600 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: Paul Mather <paul@gromit.dlib.vt.edu> Cc: freebsd-ppc@freebsd.org Subject: Re: New powerpc64 snapshot Message-ID: <20101202134537.5fee174a@anacreon.physics.wisc.edu> In-Reply-To: <15A958D9-5CBE-4830-B72C-CC4DF2192BC0@gromit.dlib.vt.edu> References: <5A677521-DE86-4BA9-BA85-8003957551B5@freebsd.org> <C31BDA76-ECE9-4012-86C4-24B30ECC8162@gromit.dlib.vt.edu> <4CEBDB9D.2010309@freebsd.org> <15A958D9-5CBE-4830-B72C-CC4DF2192BC0@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Dec 2010 14:29:57 -0500 Paul Mather <paul@gromit.dlib.vt.edu> wrote: > On Nov 23, 2010, at 10:19 AM, Nathan Whitehorn wrote: > > > On 11/22/10 14:34, Paul Mather wrote: > >> 2) Usually, the system will not boot multi-user as it is unable to > >> mount the root partition after booting the kernel. Dropping into > >> the debugger and issuing a "reboot" to do a warm boot will allow > >> the system then to boot multi-user successfully. > > > > Could you do a verbose boot (boot -v at the boot prompt) and send > > the resulting dmesg? There is some issue with the built-in > > serverworks SATA controller and some hard drives that no one has > > been able to track down yet. It doesn't affect anything once the > > machine has booted. > > Since I built a new kernel using updated sources I haven't really > noticed the problem as much. My rebuilt kernel does have WITNESS > disabled. > > Verbose boot output is included at the end of this message. Thanks! I'll see what I can glean from that. > >> 4) After a while, my system fell of the network with "bge0: > >> watchdog timeout -- resetting" being output on the console > >> periodically. > > > > Odd. I've CC'ed Pyun Yong Hyeon, who maintains the bge driver. > > Maybe he has some ideas. > > Touch wood, but since rebuilding the kernel with newer sources I've > not noticed this problem again. Weird. Glad it went away :) > >> I realise the FreeBSD/powerpc64 port is experimental at this point. > >> Can anyone tell me if the above symptoms afflict the 32-bit > >> FreeBSD/powerpc 8-STABLE port? Although I like the idea of the > >> powerpc64 port allowing me to use all of the 3.5 GB RAM in this > >> machine, at this point it is more important for me to trade away > >> the extra RAM for stability (and *quietness*:). If FreeBSD/powerpc > >> 8-STABLE is more solid, I'd rather switch to that, as I'd like to > >> get this machine back into service. > >> > >> (I would be more prepared to soldier on with FreeBSD/powerpc64 if I > >> could get the fan noise problem under control. That would let me > >> do more testing without going crazy from the noise.:) > > > > All of the problems you mentioned above are also present with a > > 32-bit system. > > > I'll keep on with FreeBSD/powerpc64, then. Is ZFS supported? Is > booting from a ZFS pool supported, or do you need to do > the /boot-on-UFS workaround from before the boot loader could boot > from ZFS pools to get a largely ZFS-only system? > ZFS is supported, but booting from a ZFS pool is not, so you'll need to do the /boot-on-UFS thing. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101202134537.5fee174a>