Re: port-amd64/58982: NetBSD 10.1 install image (amd64) failed to boot on J3455-ITX board (ASRock)

["Andrius V via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR port-amd64/58982; it has been noted by GNATS.

From: Andrius V <vezhlys%gmail.com@localhost>
To: wgstuken%grimme-reitenspezial.de@localhost
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: port-amd64/58982: NetBSD 10.1 install image (amd64) failed to
 boot on J3455-ITX board (ASRock)
Date: Sun, 12 Jan 2025 23:14:58 +0200

 On Sun, Jan 12, 2025 at 10:02=E2=80=AFPM <wgstuken%grimme-reitenspezial.de@localhost>=
  wrote:
 >
 > Hi,
 >
 > just as remark at the beginning : today it was nessesary to reset the
 > CMOS after trying to boot of 10.1 in SMP mode (by accident) ....
 > VGA monitor output was dark - even for bios setup menus.
 > There must have something thrown some bombs around ...
 > This has not happend yesterday - do not ask me why ...
 
 Weird indeed, can't comment on this, likely some machine state was
 messed up. I had issues with certain graphics cards in the past too.
 
 >
 > I had a try with 10.1 and 'boot -12'
 > This bring up the kernel but failed to initialize USB - keyboard lost,
 > no input possible.
 >
 > next try 'boot -2'
 > This bring up the kernel, but failed to setup sd0 (the USB-stick),
 > keyboard not working anymore -> nothing to boot from ...
 >
 > next try 'boot -1'
 > This bring up the kernel and allows to boot from USB-stick. (two times
 > due to USB initialisation problem when USB-stick attached to same
 > hardware as keyboard also connected.)
 > It enters system setup. I dropped to shell from there.
 >
 > the boot -1 and boot -2 messages are inside attached file - system not
 > powered down inbetween so all messages are there ...
 >
 > The 'boot -2 try failed to setup 'all' interrupt handler - no devices
 > active ...
 >
 > The 'boot -1' looks better ....
 
 Yes, not all systems boot well without ACPI especially (-2 option) or
 SMP (-1). Combinations in-between can result in unexpected issues. Not
 out the question that there are more issues.
 
 > "cpuctl -a cpu0" runs into usage message
 > "cat /proc/cpuinfo' - output attached too.
 >
 > I run 'cpuctl identify 0' - this looks like what you like to get with
 > above cpuctl call.
 > See output attached.
 
 I can't seem to find attached files? Can you please try to resend them
 or copy of them output to the email itself?
 
 
 >
 > Last thing I've done today: try with NetBSD-8.0-amd64-uefi-install.img
 > ...
 >
 > Boot failed too with 'failed to start CPU1' ....
 > 'boot -1' comes up again.
 >
 > So looks like this is not covered by whatever workaround in 8.0.
 >
 
 Thanks for all of your testing, not working workaround adds to my
 suspicion regarding stepping. Currently netbsd code applies errata to
 stepping 9 only.
 If we can confirm that your CPU stepping is different, removing the
 check hopefully will help to solve the boot issue at least.
 
 Regards,
 Andrius V