Date: Thu, 15 Jun 2006 21:05:18 +1000 From: Alexander Logvinov <abuse@akavia.ru> To: freebsd-acpi@freebsd.org Subject: Re[2]: Machine did not reboot Message-ID: <681310105.20060615210518@akavia.ru> In-Reply-To: <448C867B.3010708@root.org> References: <1182686709.20060605133201@akavia.ru> <200606062022.59336.jkim@FreeBSD.org> <121000959.20060607154424@akavia.ru> <200606071524.07284.jkim@FreeBSD.org> <448C867B.3010708@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Nate. >> I don't know what ACPI spec. says (I guess I'll have to look it up) >> but Linux doesn't seem to use it except for ACPI init failure case. >> Now I have another evil hack (attached). It will help rebooting >> without RESET_REG support and/or with broken BIOS. Basically, it >> just bypasses AcpiDisable(), which may cause hang when ACPI_DISABLE >> through SMI_CMD is issued. > Thanks for both your efforts. I've committed and MFCd a patch that does > the same things. I left out Jung-uk's hack because it's better just to > not run AcpiTerminate at all than grovel in its internals. After updating src/sys/dev/acpica/acpi.c to v 1.214.2.5 2006/06/11 I get a "ACPI reset failed - timeout" message. I call Jung-uk's hack with AcpiGbl_OriginalMode = ACPI_SYS_MODE_ACPI and AcpiTerminate() manually but it doesn't help. May it be anything wrong with my kernel configuration? -- WBR
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?681310105.20060615210518>