Bug 268736

Summary:	FreeBSD boot stuck with comconsole in x86 Hyper-V Gen2
Product:	Base System	Reporter:	schakrabarti <schakrabarti>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Open ---
Severity:	Affects Many People	CC:	grahamperrin, lwhsu, markj, whu
Priority:	---
Version:	CURRENT
Hardware:	amd64
OS:	Any

Description schakrabarti@microsoft.com 2023-01-03 18:47:08 UTC

When booting current FreeBSD on Hyper-V x86 gen2 VM, if we set console="comconsole", then boot is getting stuck.

boot -v
Loading kernel...
/boot/kernel/kernel text=0x18b088 text=0xe1ece8 text=0x6bfa3c data=0x140 data=0x1c9b60+0x4354a0 0x8+0x199f08+0x8+0x1ba8e1|
Loading configured modules...
can't find '/boot/entropy'
can't find '/etc/hostid'
staging 0xeec00000 (not copying) tramp 0xeeb64000 PT4 0xeeb5b000
Start @ 0xffffffff8038c000 ...
EFI framebuffer information:
addr, size     0xf8000000, 0x800000
dimensions     1024 x 768
stride         1024
masks          0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
---<<BOOT>>---
APIC: Using the MADT enumerator.
No panic or call trace is seen.

Comment 1 Li-Wen Hsu freebsd_committer

2023-01-03 19:22:04 UTC

What's the git commit hash of your -CURRENT?

Comment 2 schakrabarti@microsoft.com 2023-01-03 21:08:44 UTC

(In reply to Li-Wen Hsu from comment #1)
This is the last commit.


commit a0c50eda2987334cb165802250b5f5ee9b5cffea (HEAD -> main, origin/main, origin/HEAD)
Author: Joseph Mingrone <jrm@FreeBSD.org>
Date:   Mon Dec 19 00:07:11 2022 -0400

    beinstall.sh: Check correct exit status

    When retrieving the timestamp of the last commit using git-show(1), do
    not pipe the output to head(1), otherwise the return value in $? will be
    for head(1) and not git-show(1).

    Approved by:    bapt
    Sponsored by:   The FreeBSD Foundation
    Differential Revision:  https://reviews.freebsd.org/D37742

I need to git bisect to find the culprit commit.

Comment 3 Mark Johnston freebsd_committer

2024-10-27 13:51:12 UTC

Is this still a problem with recent FreeBSD releases?