On Mon, May 19, 2014 at 03:56:05PM -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. > > > > Well, the FreeBSD boot panics in a similar sort of way. "Bogus interrupt > trigger mode". This is from memory -- I didn't get a full copy of the boot > messages, though it did have "acpi" and "madt" in backtrace. > > I can get it if this is important, though this is starting to look like > a Windows-only box. > However, the FreeBSD message allowed my Google-fu to work. This looks apropos:
http://forums.freenas.org/index.php?threads/kernel-panic-bogus-interrupt-trigger-mode-on-intel-j1900.20851/ And http://www.freebsd.org/cgi/query-pr.cgi?pr=187966 Nearly the exact hardware I have. Which also appears to have a buggy BIOS. -- John D. Verne <j...@clevermonkey.org>
