Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Jul 2003 23:00:50 +0200
From:      Bernd Walter <ticso@cicely12.cicely.de>
To:        Marcel Moolenaar <marcel@xcllnt.net>
Cc:        freebsd-alpha@freebsd.org
Subject:   Re: panic: cpu_initclocks: no clock attached
Message-ID:  <20030721210049.GD511@cicely12.cicely.de>
In-Reply-To: <20030721205750.GA8034@ns1.xcllnt.net>
References:  <20030721180848.GC32645@cicely8.cicely.de> <20030721183151.GB599@dhcp01.pn.xcllnt.net> <20030721184812.GG32645@cicely8.cicely.de> <20030721191517.GD599@dhcp01.pn.xcllnt.net> <20030721192845.GI32645@cicely8.cicely.de> <20030721205207.GB511@cicely12.cicely.de> <20030721205750.GA8034@ns1.xcllnt.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 21, 2003 at 01:57:50PM -0700, Marcel Moolenaar wrote:
> On Mon, Jul 21, 2003 at 10:52:07PM +0200, Bernd Walter wrote:
> > On Mon, Jul 21, 2003 at 09:28:46PM +0200, Bernd Walter wrote:
> > > 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:
> > > > 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.
> > 
> > Should have been 14th...
> > I've send Greg a patch for vinum and will update to a recent current
> > once this part is fixed.
> > The system seems to work now.
> > No problem on NFS noticed so far - and I already did a lot on NFS.
> > In case it matters: all my mounts are udp over IPv6.
> 
> TCP/IPv4 in my case. None of my other machines have this problem.
> BTW: I also noticed that rpc.statd fails (world and kernel are in
> sync), because msync(2) failed. Anyway: too much to try out...

Another difference - I'm running neither statd nor lockd.

-- 
B.Walter                   BWCT                http://www.bwct.de
ticso@bwct.de                                  info@bwct.de



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030721210049.GD511>