(The "acpidump -dt | gzip" is attached...) ACPI says that IOAPIC 2 lives at 0xfec30000. Yet, when the ioapic_attach() code tries to check it, the read_vers_and_size gets 0xffffffff - basically saying that it failed to read the apic's register, even though the address block was just mapped a few lines earlier. And since we determine that ID #15 is not the desired ID #2, we attempt to re-write the ID register, which fails.
I did a quick check, and FreeBSD actually has code that "punts" if the value read from the register comes back as 0xffffffff, while OpenBSD seems to ignore it the same as NetBSD. I haven't verified myself, but the retailer of this system claims that it worked "just fine" under Centos (RedHat Linux?).
I don't know much about the x86 hardware architecture, so I'm at a loss on how to proceed with this problem. The only devices known to live on this ioapic are the two GigE LAN ports, but it's difficult to imagine having the great 12-Core Opteron server being disconnected from everything else. :)
Any hints, clues, suggestions, or even wild-* guesses would be welcomed. ------------------------------------------------------------------------- | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | | Kernel Developer | | pgoyette at netbsd.org | -------------------------------------------------------------------------
Attachment:
acpidump.gz
Description: Binary data