Re: ata unable to map interrupt

From: John Baldwin <jhb_at_FreeBSD.org>
Date: Fri, 2 Jul 2004 00:12:15 -0400
On Thursday 01 July 2004 09:53 pm, Andrew Gallatin wrote:
> 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.

I think this is a problem with ATA.  Soren made a change to dev/pci/pci.c for 
the ATA native mode allocation that might be suspect.

-- 
John Baldwin <jhb_at_FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
Received on Fri Jul 02 2004 - 02:22:17 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:59 UTC