http://bugzilla.kernel.org/show_bug.cgi?id=11481
------- Comment #15 from [EMAIL PROTECTED] 2008-10-16 20:01 ------- The default reboot_type is BOOT_KBD. It works for most boxes. But for some boxes it can't work well after suspend/resume. So the ACPI reboot mechanim is used by adding the boot option of "reboot=a". Maybe the reboot_type can be changed to BOOT_ACPI if the ACPI reboot mechanism is supported. But in such case the other reboot_type can't be used any more. If the default reboot_type is changed to BOOT_ACPI for your box by using DMI table, it seems ugly. IMO you can use the ACPI reboot mechanism by adding the boot option of "reboot=a". In fact there exist the other definitions of reboot_type . For example: >BOOT_TRIPLE = 't', > BOOT_KBD = 'k', #ifdef CONFIG_X86_32 > BOOT_BIOS = 'b', #endif > BOOT_ACPI = 'a', > BOOT_EFI = 'e' What Lenb said in comment #14 is right. On your box the FADT flag bit indicates that ACPI reboot is not supported. But your box can be rebooted by writing the RESET_VALUE to ACPI_RESET_REG forcibly. And the patch in comment #12 is to ignore the missing bit in the BIOS. Thanks. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla