Watchdog still active on Aspire 3 A315-41 after booting operating system

rdos
rdos Member Posts: 1 New User
edited September 2023 in 2019 Archives
I bought an Aspire 3 laptop to run my own operating system on which runs on most x86-compatible computers. The hardware seemed to be supported, and everything works for 15-20 seconds and then the screen turns black and the computer hangs up. If I do ExitBootServices, and go into a loop in the efi loader then the computer reboots after the same time. The processor has a watchdog, and it seems to be enabled after ExitBootServices, but it doesn't help to disable it. It also doesn't help to loop in the NMI handler or the Machine Check exception, the display will still be turned off. ACPI doesn't export a watchdog object so that's not a possible way to resolve the problem.

It's even stranger that the issue can sometimes be resolved by booting into Windows 10, restart and boot into my own operating system. Once this works, I can reboot multiple times and the problem will not reappear until I turn off and on the power again.

The EFI standard states that after ExitBootServices, the BIOS should not attempt to interfere with the operating system, and if it does, it must at least export a watchdog object to ACPI.

I have upgraded the BIOS to 1.13, but that doesn't solve the problem.

Any potential solution to this problem would be appreciated.

Answers

  • JackE
    JackE ACE Posts: 45,178 Trailblazer
    Sorry, this user board is unlikely to be of much help to you on this. Firmware & ACPI implementation details are unavailable to us and probably only shared with Microsoft & Linpus. Jack E/NJ

    Jack E/NJ