Re: Intel SE7500WV2 not working with ACPI
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 SWV20on 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 [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ pgp0.pgp Description: PGP signature
Re: Intel SE7500WV2 not working with ACPI
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 SWV20on 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]
RE: Intel SE7500WV2 not working with ACPI
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 SWV20on 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. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel SE7500WV2 not working with ACPI
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 SWV20on 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? -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature
Re: Intel SE7500WV2 not working with ACPI
acpi0: INTEL SWV20on 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 acpi0 fails to attach, everything else is done through the legacy PCI code. The question is, why is it failing? The above-mentioned EC method could indicate the problem is in walking the namespace but we'll have to look at the ASL to be sure. Please send a url to the output of: acpidump -t -d brooks-Intel.asl Also, build with options ACPI_DEBUG and set these in your loader.conf: debug.acpi.layer=ACPI_ALL_COMPONENTS debug.acpi.level=ACPI_LV_OPREGION -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel SE7500WV2 not working with ACPI
On Tue, Nov 25, 2003 at 12:12:16PM -0800, Nate Lawson wrote: acpi0: INTEL SWV20on 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 acpi0 fails to attach, everything else is done through the legacy PCI code. The question is, why is it failing? The above-mentioned EC method could indicate the problem is in walking the namespace but we'll have to look at the ASL to be sure. Please send a url to the output of: acpidump -t -d brooks-Intel.asl http://people.freebsd.org/~brooks/debug/brooks-Intel.asl Also, build with options ACPI_DEBUG and set these in your loader.conf: debug.acpi.layer=ACPI_ALL_COMPONENTS debug.acpi.level=ACPI_LV_OPREGION There's a new dmesg with this done at: http://people.freebsd.org/~brooks/debug/dmesg-brooks-Intel Thanks, Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature