Brooks Davis wrote: >> Since acpi0 failed to probe, ACPI isn't used to route interrupts. However, >> the apic code expects ACPI to do that since it enumerated CPUs and I/O >> APICs. You are just going to have to disable ACPI for now. >> >> > acpi0: <INTEL SWV20 > on motherboard >> > ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] >> > (Node 0xc29b4660), AE_NOT_EXIST >> > acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST >> > device_probe_and_attach: acpi0 attach returned 6 >> >> If you can get this fixed, then you can re-enable ACPI again. > > What I can't figure out is why this is failing since acpi was at least > partialy working before. For instance, soft power was definalty > working. Doesn't that depend on acpi attaching?
I plan on updating our ACPI-CA to the 20031202 dist after the code freeze is over. It has some important fixes, including this one: --- Changed the initialization of Operation Regions during subsystem init to perform two entire walks of the ACPI namespace; The first to initialize the regions themselves, the second to execute the _REG methods. This fixed some interdependencies across _REG methods found on some machines. --- You might be able to work around this problem by setting: debug.acpi.disable="ec" or debug.acpi.avoid="\_SB_.PCI0.SBRG" -Nate _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
