From owner-freebsd-hackers Mon Jun 5 14:23:55 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA09233 for hackers-outgoing; Mon, 5 Jun 1995 14:23:55 -0700 Received: from w8hd.w8hd.org (w8hd.w8hd.org [198.252.159.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA09220 ; Mon, 5 Jun 1995 14:23:51 -0700 Received: (from kimc@localhost) by w8hd.w8hd.org (8.6.11/w8hd) id RAA15887; Mon, 5 Jun 1995 17:23:47 -0400 Date: Mon, 5 Jun 1995 17:23:47 -0400 (EDT) From: kim culhan To: "Justin T. Gibbs" cc: John Herks , hackers@FreeBSD.ORG Subject: Re: ed0 - device timeout ? In-Reply-To: <199506051454.HAA05144@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.ORG Precedence: bulk On Mon, 5 Jun 1995, Justin T. Gibbs wrote: > >I am randomly getting ed0 kernel device timeout messages from my Freebsd > >2.0R machine... > > > > Are you possitive that your card is really located at Irq 5? You can > boot with the "-c" option at the boot prompt to change the Irq for the > card, but this sounds very much like a mis configured IRQ. When I rebuilt with 2.0.5-ALPHA, rebooted and then compiled a new kernel the ed0 device would time-out on boot-up. Although the kernel config file was the same one used before which had ed0 at irq5, I had to change the config file to ed0 at irq10 (where it actually is.) Apparently it doesn't find the card with probing now. kim -- kimc@w8hd.org