panic: cpu_initclocks: no clock attached
Bernd Walter
ticso at cicely8.cicely.de
Mon Jul 21 12:28:55 PDT 2003
On Mon, Jul 21, 2003 at 12:15:17PM -0700, Marcel Moolenaar wrote:
> 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...
I will see - the system is a NFS client too, but it run with a fxp
based card.
But it's not updated to the latest version - the checkout happend
on 17th.
--
B.Walter BWCT http://www.bwct.de
ticso at bwct.de info at bwct.de
More information about the freebsd-alpha
mailing list