enuhtac <enuhtac_lists <at> gmx.de> writes: > > Mark Kettenis <mark.kettenis <at> xs4all.nl> writes: > > > > > > Date: Sun, 19 Oct 2014 17:59:29 +0200 > > > From: Julien Dehaese <jdehaese <at> gmail.com> > > > > > > Hi, > > > I'm trying to get openbsd running on an Intel Baytrail motherboard with > a > > > SSD disk. > > > > > > Motherboard is Asrock Q1900-ITX, 4GB RAM > > > Kingston SSD model : SV300S37A60G > > > > > > Steps to reproduce: > > > - performed standard install of openbsd 5.6-current (19/10/2014) - > today. > > > All went well during the install until the first reboot after install. > > > - during the first reboot after install, openbsd raises a panic : > > > lapic_set_lvt > > > - ran the trace and ps when debugger prompt appeared. > > > > > > Same error occurs at each reboot. > > > > Does a GENERIC (non-MP) kernel boot on the machine? The installer > > should have installed one as bsd.sp, which you can specify at the > > boot> prompt. > > > > If that kernel boots, can you send use acpidump(8) output for this > machine? > > > > Thanks, > > > > Mark > > > > >
I took the ACPI specs and the kernel sources and tried to figure out what's going on. Obviously the "Local APIC NMI Structure" (aka ACPI_MADT_LAPIC_NMI) entries in the ACPI MADT table contain garbage in the flags field. Also the content of the lint field seems rather strange to me - although I do not know its meaning. This is also the reason for the kernel panic: the kernel sees '171' in this field but expects '0' or '1'. Are there any means to fix this? E.g. can I assume save default values for the flags and lint fields? enuhtac
