From owner-freebsd-hackers Fri Jul 28 12:18:29 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id MAA27295 for hackers-outgoing; Fri, 28 Jul 1995 12:18:29 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id MAA27285 for ; Fri, 28 Jul 1995 12:18:26 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA02109; Fri, 28 Jul 1995 12:18:04 -0700 From: "Rodney W. Grimes" Message-Id: <199507281918.MAA02109@gndrsh.aac.dev.com> Subject: Re: 2.0.5-950622-SNAP on a big machine To: davidg@Root.COM Date: Fri, 28 Jul 1995 12:18:04 -0700 (PDT) Cc: junkmail@pht.com, gary@palmer.demon.co.uk, hackers@freebsd.org In-Reply-To: <199507281737.KAA00174@corbin.Root.COM> from "David Greenman" at Jul 28, 95 10:37:21 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 905 Sender: hackers-owner@freebsd.org Precedence: bulk > > >Jul 26 16:23:38 gandalf /kernel: ed0: device timeout > > This usually indicates that the irq isn't set properly in the kernel. Find > out how the card is configured and then change the setting in 'userconfig' > with "-c" at the Boot: prompt. > And if this happens to be a PCI machine I just went through a similiar failure with a customer who was adding an ed0 device on IRQ10 which had been assigned by the P-n-P bios to one of his PCI cards. So make sure if this is a PCI machine that you have properly set the PCI P-n-P bios to state that IRQ x is in use by the ISA bus. The PCI code does not seem to be registering it's interrupts so that the ISA code does proper conflict detection. That is a bug that needs fixed, and badly :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD