From owner-freebsd-alpha Wed Sep 2 01:48:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16598 for freebsd-alpha-outgoing; Wed, 2 Sep 1998 01:48:31 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16588 for ; Wed, 2 Sep 1998 01:48:29 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA04229; Wed, 2 Sep 1998 09:47:01 +0100 (BST) Date: Wed, 2 Sep 1998 09:47:01 +0100 (BST) From: Doug Rabson To: Andrew Gallatin cc: shimon@simon-shapiro.org, freebsd-alpha@FreeBSD.ORG Subject: Re: Alpha Install - oops! In-Reply-To: <13804.2770.473870.7600@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 1 Sep 1998, Andrew Gallatin wrote: > > Simon Shapiro writes: > > > > Andrew Gallatin, On 31-Aug-98 you wrote: > > > > > I think you may have more luck if you power-cycle the box. When I've > > > seen this under NetBSD/alpha, I suspected it was caused by the IDE > > > controller acting as a noise generator, and was able to cure it by > > > disabling the ide controller. > > > > How? > > > > (I think there is a problem we may want to solve here, still) > > > > ... > > Under NetBSD, simply leaving all references to the ide controller out > of the config file did the trick. Under NetBSD, the ide controller > got sort of half-attached -- enough for the isa irq to be enabled, but > no devices on the controller were successfully attached. > > Doug - Does the ISA code disable all/most interrupts at boot time, or > does it leave things as it found them? I'm worried the console > firmware might be leaving the ide ISA irq enabled on Simon's machine. I don't mask out all the ISA interrupts when I initialise the ISA bus. I think that is probably what is going wrong. The current theory is that booting NetBSD first leaves something enabled (probably the irq) which I can't cope with. I'm having trouble testing this idea this morning since I can't seem to get NetBSD work properly. The GENERIC kernel from 1.3F shows the same slow printing effect as Simon had with FreeBSD. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message