Date: Thu, 1 Jul 2004 21:53:08 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: freebsd-current@freebsd.org Subject: Re: ata unable to map interrupt Message-ID: <16612.49156.140882.83317@grasshopper.cs.duke.edu> In-Reply-To: <16612.38647.686404.398773@grasshopper.cs.duke.edu>
index | next in thread | previous in thread | raw e-mail
Andrew Gallatin writes: > > Today's kernel: > > atapci0: <ServerWorks CSB5 UDMA100 controller> 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. Drewhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16612.49156.140882.83317>