From owner-freebsd-alpha  Fri Apr 26  0:58:29 2002
Delivered-To: freebsd-alpha@freebsd.org
Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170])
	by hub.freebsd.org (Postfix) with ESMTP
	id 98E7537B404; Fri, 26 Apr 2002 00:58:20 -0700 (PDT)
Received: from storm.FreeBSD.org.uk (uucp@localhost [127.0.0.1])
	by storm.FreeBSD.org.uk (8.12.2/8.12.2) with ESMTP id g3Q7tW1R069925;
	Fri, 26 Apr 2002 08:55:32 +0100 (BST)
	(envelope-from mark@grimreaper.grondar.org)
Received: (from uucp@localhost)
	by storm.FreeBSD.org.uk (8.12.2/8.12.2/Submit) with UUCP id g3Q7tWwg069924;
	Fri, 26 Apr 2002 08:55:32 +0100 (BST)
Received: from grimreaper.grondar.org (localhost [127.0.0.1])
	by grimreaper.grondar.org (8.12.3/8.12.3) with ESMTP id g3Q7o7d0029078;
	Fri, 26 Apr 2002 08:50:07 +0100 (BST)
	(envelope-from mark@grimreaper.grondar.org)
Message-Id: <200204260750.g3Q7o7d0029078@grimreaper.grondar.org>
To: Peter Wemm <peter@wemm.org>
Cc: Marcel Moolenaar <marcel@cup.hp.com>,
	John Baldwin <jhb@FreeBSD.ORG>, alpha@FreeBSD.ORG
Subject: Re: panic: cpu_initclocks: no clocks attached 
References: <20020426000652.60C0C380F@overcee.wemm.org> 
In-Reply-To: <20020426000652.60C0C380F@overcee.wemm.org> ; from Peter Wemm <peter@wemm.org>  "Thu, 25 Apr 2002 17:06:52 PDT."
Date: Fri, 26 Apr 2002 08:50:07 +0100
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-alpha.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-alpha>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-alpha>
X-Loop: FreeBSD.org

> I stuck a #if 0 around kern_environment.c:  init_dynamic_kenv and the
> associated SYSINIT.  My alpha is working with mcclock fine.  I thought
> it might be worth mentioning this if you need to get back up and running
> asap.
> 
> Secondly, I've had to remove 'device random' because my PC164SX was locking
> up like crazy and running extremely slowly.  I had to break into ddb to get
> out of the lockups.  Anyway, just commenting out 'device random' and then
> relinking the kernel made it go back to normal.

I'm very keen to fix this. Firstly, what is a PC164SX? (The headers
suggest that it is some kind of Alpha).

Can you put the 'device random' back in, and try turning off entropy
harvesting by turning off each of the following sysctls to see if any
of them "fix" the problem?

kern.random.sys.harvest.ethernet
kern.random.sys.harvest.point_to_point
kern.random.sys.harvest.interrupt

I am suspecting that a high-rate interrupt is being harvested, and
that this is the problem.

Also, please run 'systat 2 -vmstat' for a while, and stare at the irqs
(top-right-ish) and see if any/which of them are high-rate interrupt
sources, and let me know which.

Is it possible to get an account on this box?

Thanks!

M
-- 
o       Mark Murray
\_
O.\_    Warning: this .sig is umop ap!sdn
#text/plain; name=cv.doc [Mark Murray CV Plain Text] cv.doc
#application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message