> On Jan 7, 2016, at 4:08 AM, open...@tuta.io wrote: > > Hi Mark, > Thanks for having a look at this. > The 6th of January install59.fs should have v 1.298 of acpi.c > But I still get the same 'can't map interrupt' on both EHCI and XHCI. > Let me know if there's a way to collect more support data to help investigating this. > Thanks. > Regards, >
Thank you also for continuing to look at this. On Lenovo Ideapad 100S-11 (Intel Atom Z3735F) using the January 6 amd64 snapshot it no longer reports the interrupt error but the system will not complete the boot due to a memory conflict. Sections of the dmesg are below. [skipping initial boot message thru bios0] acpi0 at bios0: rev 2 acpi0: tables DSDT FACP UEFI TCPA MSDM UEFI OEM0 DBG2 HPET LPIT APIC MCFG SLIC SSDT SSDT SSDT SSDT SSDT TPM2 SSDT SSDT SSDT FPDT WDAT CSRT BGRT acpimadt0 at acpi0 add 0xfee00000: PC-AT compat [skipping cpu0] ioapic0 at mainbus0: amid 2 ps 0xfed00000, version 20, 87 pins ioapic0: misconfigured as apic 1, remapped at apid 2 acpiprt0 at acpi0: bus 0 (PC10) pci0 at mainbus0 bus 0 0:2:0: mem address conflict 0x90000000/0x400000 0:2:0: mem address conflict 0x80000000/0x10000000 Regards, Dan
