> 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 > >
The first sign during the boot process of garbage in the ACPI_MADT_LAPIC_NMI structures mentioned by me earlier are these lines: acpimadt0: bogus nmi for apid 0 acpimadt0: bogus nmi for apid 2 Here the kernel detects wrong values in the flags fields and removes the corresponding ACPI_MADT_LAPIC_NMI entries. A third entry (for apid 1) goes through unnoticed because by chance the flag values are spec conform. Nevertheless the lint entry is bogus which causes the kernel panic later on. The "ehci_sync_hc: tsleep() = 35" is probably also a follow up error of the faulty LAPIC setup because the USB driver is waiting for some interrupt to occur which never happens. Still I do not know what to do to fix this issue.
