From owner-freebsd-alpha Mon Nov 6 13:11:57 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 0F73737B4D7 for ; Mon, 6 Nov 2000 13:11:53 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eA6LBio05731 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Mon, 6 Nov 2000 22:11:46 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eA6LBUi09735; Mon, 6 Nov 2000 22:11:34 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id eA6LBT944399; Mon, 6 Nov 2000 22:11:30 +0100 (CET) (envelope-from ticso) Date: Mon, 6 Nov 2000 22:11:29 +0100 From: Bernd Walter To: alpha@FreeBSD.ORG Cc: Matthew Jacob Subject: Re: Status of -CURRENT on PC164? Message-ID: <20001106221129.A44361@cicely8.cicely.de> References: <20001106041949.A11350@dragon.nuxi.com> <20001106114150.G11350@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001106114150.G11350@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Nov 06, 2000 at 11:41:50AM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 06, 2000 at 11:41:50AM -0800, David O'Brien wrote: > On Mon, Nov 06, 2000 at 08:08:59AM -0800, Matthew Jacob wrote: > > It's not John's problem to get people to help- John's done the right > > thing within the constraints of the initial design that Doug left in > > place. > > Ok, then which FreeBSD developer that took responsibility for this code > hasn't been looking into the issue? AFAIK those that have been working > on this code don't know what is going on with the PC164. I do know there > are some debugging macros, etc. that one can run that may help give some > idea what is going on. A nice "request for output" email with a few > instructions of how to get the debug info wouldn't hurt IMHO. John already mentioned this here and AFAIK there is nothing new to say about it. Basicly everyone has the same problem and the same output using the macros. I'm quite shure that the result of this phaenomen is well known, but the current aproach unfortunately did not show the reason. The question is what is more important: The debug code that John builds (which may help finding our and future problems) or starring at the PC164 problem. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message