Is there a sure bet way to - 1) Cause a system reset by setting the 32-bit FACS waking vector to a particular address? Setting it to 0xffff0 did not help as hoped. 2) Failing that, is there a way to cause a system reset by tweaking the 16-bit wakeup code? While zero length idt always causes a system reset in protected mode, the same won't work in real mode. Keyboard reset approach also did not work in real mode for some reason. It would be nice to know if there is a trick similar to zero length idt that could be used in real mode that is sure to cause system reset early on in the real mode wakeup code path. I normally inject system reset code at different points in the early wakeup code path to troubleshoot resume issues and information on the above will help better troubleshoot some S3 resume issues I encounter. Thanks, Kamala -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
