From owner-freebsd-current Thu Jun 6 18:35:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4127B37B405; Thu, 6 Jun 2002 18:35:40 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA16578; Thu, 6 Jun 2002 21:35:36 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g571Z6604029; Thu, 6 Jun 2002 21:35:06 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15616.3530.526275.555196@grasshopper.cs.duke.edu> Date: Thu, 6 Jun 2002 21:35:06 -0400 (EDT) To: Dag-Erling Smorgrav Cc: imp@freebsd.org, alpha@freebsd.org, current@freebsd.org Subject: Re: alpha can't map interrupt In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner -- a pci interupt line of 0 is valid. Please back out your "PCI_INTERRUPT_VALID" changes in pci.c, or change that macro to allow a value of 0. Thanks, Drew Dag-Erling Smorgrav writes: > A kernel built from last night's sources fails to allocate an > interrupt to the NIC in my Miata: <...> > dc0: port 0x9000-0x907f mem 0x80151000-0x8015107f at device 3.0 on pci0 > dc0: couldn't map interrupt > device_probe_and_attach: dc0 attach returned 6 > [...] > > May 26 kernel boots fine: <...> > dc0: port 0x9000-0x907f mem 0x80151000-0x8015107f irq 0 at device 3.0 on pci0 <..> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message