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: on motherboard
>> > ACPI-1287: *** Error: M
On 02-Dec-2003 Brooks Davis wrote:
> On Tue, Dec 02, 2003 at 05:50:27PM -0500, John Baldwin wrote:
>>
>> On 25-Nov-2003 Brooks Davis wrote:
>> > Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
>> > don't work with ACPI. Specificly, the onboard nics (em0 and em1)
>> > appe
On Tue, Dec 02, 2003 at 05:50:27PM -0500, John Baldwin wrote:
>
> On 25-Nov-2003 Brooks Davis wrote:
> > Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
> > don't work with ACPI. Specificly, the onboard nics (em0 and em1)
> > appear to not be recieving interupts. Instead,
On 25-Nov-2003 Brooks Davis wrote:
> Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
> don't work with ACPI. Specificly, the onboard nics (em0 and em1)
> appear to not be recieving interupts. Instead, they continiously get
> watchdog timeouts. In a stock current, this is
On Tue, Nov 25, 2003 at 12:12:16PM -0800, Nate Lawson wrote:
> > acpi0: 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: 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
This is the source of the problems. When acp
