[FS#4176] Crashing or rebooting early in boot on x86_64

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - ShadowFlare (ShadowFlare) 

Attached to Project - OpenWrt/LEDE Project
Summary - Crashing or rebooting early in boot on x86_64
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - openwrt-21.02
Due in Version - Undecided
Due Date - Undecided
Details - I hadn't updated my VM in a while, so sorry for finding this so late.

I have a VM on Hyper-V Server 2019 that had been running OpenWrt 21.02 RC3 on x86_64 with EFI and using squashfs as the rootfs type in a generation 2 (EFI-supporting) Hyper-V VM, and recently I tried updating to a build of 21.02.1. Very early in boot (after Grub, while OpenWrt is booting) it just reboots, and keeps doing this repeatedly. I tried to watch for any error message flashing on the screen just before the reboot, but I couldn't spot anything, and also the failsafe option from the boot menu doesn't help.

I've tested this with a fresh clean install without my configs on a new virtual hard drive, and the problem still occurs. Other than my own build of 21.02.1, I've found it happens on the official builds, too. I checkpointed the VM and started testing official builds, finding that it started with 21.02 release (RC4 was fine) and it continues through to 21.02.1 and also a snapshot build from master that I tried.

I skimmed through the few commits between RC4 and 21.02 release and found this commit affecting x86_64:

[[https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=750b966866b098a2e9a8693d313111ed1e892ab6]]

After reverting the change in my local tree, rebuilding 21.02.1, and installing the image on my VM, it boots successfully with no problems.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4176

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.