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) >> > appear to not be recieving interupts. Instead, they continiously get >> > watchdog timeouts. In a stock current, this is an instant panic. With >> > a minor fix to the watchdog function, the system sees to be more or less >> > funcitonal other then not having a network. Disabling ACPI makes the >> > nics work. I have updated the BIOS to the latest version[0]. >> > >> > I've included ACPI and non-ACPI dmesg output below. What else is needed >> > to diagnose this problem? Any patches I should try? >> >> 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? Yes. What does a dmesg from a UP kernel or a kernel w/o 'device apic' show? -- John Baldwin <jhb_at_FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ End of MIME message
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:32 UTC