Date: Mon, 21 Jul 2003 12:15:17 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: ticso@cicely.de Cc: freebsd-alpha@freebsd.org Subject: Re: panic: cpu_initclocks: no clock attached Message-ID: <20030721191517.GD599@dhcp01.pn.xcllnt.net> In-Reply-To: <20030721184812.GG32645@cicely8.cicely.de> References: <20030721180848.GC32645@cicely8.cicely.de> <20030721183151.GB599@dhcp01.pn.xcllnt.net> <20030721184812.GG32645@cicely8.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 21, 2003 at 08:48:12PM +0200, Bernd Walter wrote: > > The reason is that eisa bridge support now depends on having eisa > compiled in. We'd never done this on alpha. > eisa support needs to be legalized for alpha and added to GENERIC. > I will commit this in a few minutes because my system now boots fine. > > Well theoreticaly - because vinum is broken too :( > Arglll... That's no all: Kernels built after the dc(4) newbusification and gcc33 import fail to work due to NFS hangs (the process blocks on 'nfsfsy'). The dc(4) driver functions, because when NFS hangs I still have a functional network. But other than that my Alpha is mostly useless because I use NFS a lot... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030721191517.GD599>