NetBSD Problem Report #56399

From www@netbsd.org  Tue Sep 14 01:44:21 2021
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 1515E1A9239
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 14 Sep 2021 01:44:21 +0000 (UTC)
Message-Id: <20210914014419.B0A411A923A@mollari.NetBSD.org>
Date: Tue, 14 Sep 2021 01:44:19 +0000 (UTC)
From: carenas@gmail.com
Reply-To: carenas@gmail.com
To: gnats-bugs@NetBSD.org
Subject: NetBSD HEAD snapshot i386 fails to boot under HyperV (64 bit)
X-Send-Pr-Version: www-1.0

>Number:         56399
>Category:       kern
>Synopsis:       NetBSD HEAD snapshot i386 fails to boot under HyperV (64 bit)
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 14 01:45:00 +0000 2021
>Last-Modified:  Thu Oct 03 17:00:02 +0000 2024
>Originator:     Carlo Arenas
>Release:        any available snapshot of HEAD for i386
>Organization:
>Environment:
>Description:
Trying to boot in a single or multi CPU VM will result in a KDB prompt
after failing to initialize the CPUs as shown by :

...
[  1.0000030] vmbus0 at acpi0 (VMB8, VMBUS-0): Hyper-V VMBus
[  1.0000030] fatal protection fault in supervisor mode
[  1.0000030] trap type 4 code 0 eip 0xc0488dab cs 0x8 eflags 0x246 cr2 0 ilevel 0x8 esp 0x4
[  1.0000030] curlwp 0xc14e8f00 pid 0 lid 0 lowest kstack 0xc17902c0
kernel: supervisor trap protection fault, code=0
Stopped in pid 0.0 (system) at netbsd:vmbus_init_synic_md+0xa6:    wrmsr

NetBSD 9.2 (release or current) doesn't show the problem, and neither does an AMD64 snapshot in the same hypervisor.
>How-To-Repeat:
Under Hyper-V (using it locally in Windows 10, but should also behave the same in Azure), create a new VM machine or upgrade a running VM from NetBSD 9.2 and try to boot.
>Fix:

>Audit-Trail:
From: John Verne <john.verne@ricoh.ca>
To: "gnats-bugs@NetBSD.org" <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: kern/56399
Date: Thu, 3 Oct 2024 13:53:50 +0000

 I have four screen captures showing the fault and the backtrace -- I'm not =
 able to transcribe these by hand without making a lot of mistakes.=0A=
 =0A=
 I'll save them and provide them on demand, as I don't know if PRs accept wh=
 atever-encoded data from incoming emails, and any share site is an opportun=
 ity for bit-rot.=0A=

From: John Verne <john.verne@ricoh.ca>
To: "gnats-bugs@NetBSD.org" <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: kern/56399
Date: Thu, 3 Oct 2024 13:27:46 +0000

 Hyper-V on Windows 11 has the exact same issue booting NetBSD 10.0 i386. I'=
 ll try to capture the gdb details as outlined in the HowTo document and app=
 end them here, if anyone thinks it'll be useful.=0A=
 =0A=
 I tried various virtualization options related to CPUs, memory, etc.=0A=
 =0A=
 NetBSD 9.4 i386 boots without error with the default settings.=0A=
 =A0=

From: John Verne <john.verne@ricoh.ca>
To: "gnats-bugs@NetBSD.org" <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: kern/56399
Date: Thu, 3 Oct 2024 15:10:18 +0000

 Looks like this is possibly fixed in kern/58653? I'll wait until 10.1 as I'=
 m not quite in a spot to apply a diff and check before that.=

Home	PR Database Search