On Tue, May 20, 2014 at 09:51:50AM -0400, John D. Verne wrote: > On Mon, May 19, 2014 at 11:19:23AM -0700, Mike Larkin wrote: > > On Mon, May 19, 2014 at 01:42:49PM -0400, John D. Verne wrote: > > > On Sun, May 18, 2014 at 03:04:30PM -0400, John D. Verne wrote: > > > > I just got a new amd64 box to run OpenBSD on, but it is panicking on > > > > boot > > > > when I try to run the 5.5 kernel on it. > > > > > > > > The panic is "unknown MPS interrupt trigger 2" somewhere in the acpi > > > > code. > > > > > > > > bsd.rd, bsd and bsd.mp all panic in the same places, as does bsd.rd from > > > > the latest amd64 snapshot. > > > > > > > > > > NetBSD 6.1.4 manages to enumerate all the ACPI stuff when I use their > > > boot image. So there's that. > > > > > > As an aside, I was surprised at how different the src/sys tree is from > > > OpenBSD. But I'm going to try and see how they handle the Intel ACPICA > > > 20110623 device, which seems to be the thing that is not working right. > > > > > > > Get a dump of the AML using FreeBSD then. Can't really help otherwise. > > > Ok, thanks for the tip. I managed to get FreeBSD 11-current to boot, and > I've run acpidump -td to get the attached output. I hope this is what > you wanted. If not, I have the FreeBSD liveCD running on the OpenBSD > snapshot install on this hardware. I am at your disposal. > > I've also booted the OpenBSD snapshot from May 19 by disabling the > acpi0 device via UKC, and then tweaked the kernel in the same manner > FreeBSD does, which allows the boot process to not panic with acpi > enabled. So, copying what Linux and FreeBSD does naively "fixes" things. > I'll leave the rest up to the experts. > > However, then I ran into another panic related to "lapic". During the > FreeBSD-current back-and-forth, I ended up disabling half the serial > ports on this motherboard via the BIOS. It looks like the three "back > panel" serial ports are acceptable, but the three on-board serial ports > cause a panic. FreeBSD hangs when enumerating those, and OpenBSD panics. > I'll raise this as a seperate issue, but for now I've disabled them. > Admittedly, this is a weird board, so those ports are both highly > configurable and probably presented to (what looks like) the ISA bus in > an odd manner. >
Perhaps an email of such a tremendous size is unlikely to get to the list. I'll try attaching the acpidump output. [demime 1.01d removed an attachment of type application/x-gunzip]
