From owner-freebsd-current@FreeBSD.ORG Fri Jul 2 01:54:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2107016A4CE for ; Fri, 2 Jul 2004 01:54:29 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63A5543D45 for ; Fri, 2 Jul 2004 01:54:28 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i621rDqM028003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 Jul 2004 21:53:13 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i621r8TH007988; Thu, 1 Jul 2004 21:53:08 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16612.49156.140882.83317@grasshopper.cs.duke.edu> Date: Thu, 1 Jul 2004 21:53:08 -0400 (EDT) To: freebsd-current@freebsd.org In-Reply-To: <16612.38647.686404.398773@grasshopper.cs.duke.edu> References: <16612.38647.686404.398773@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: Re: ata unable to map interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2004 01:54:29 -0000 Andrew Gallatin writes: > > Today's kernel: > > atapci0: port 0xffa0-0xffaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 > atapci0: unable to map interrupt Argh! Unable to map interrupt, not I/O port. Sorry.. An I/O port mapping was the last thing that left me at a mountroot prompt on this f'ing box. The problem is really with mapping interrupts. I've left mptable, and verbose boot output from working and nonworking kernels at http://people.freebsd.org/~gallatin/ata_irq/ As I said before, it doesn't seem to matter if I enable or disable ACPI. I've also tried set hw.apic.mixed_mode=0 A kernel from another box from June 19th seems to work, so maybe it happened in the last 12 days or so. Drew