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

["wgstuken%grimme-reitenspezial.de@localhost via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: wgstuken%grimme-reitenspezial.de@localhost
To: Andrius V <vezhlys%gmail.com@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: Thu, 16 Jan 2025 21:06:23 +0100

 Hi - system run into same error again ...
 So just down load sources and build them failed on i386 system
 
 I try to find some time to localte the problem - I do not think it makes 
 sense to start cross-build for amd64 in this state ..
 
 Am 16.01.2025 10:30, schrieb wgstuken%grimme-reitenspezial.de@localhost:
 > Hi again - update
 > 
 > I have setup old Celeron (32-Bit only) system in the meanwhile.
 > Loaded complete source and had a try with 'make release'
 > It build for long time on this slow CPU and then run into error during
 > setup of ramdisk-big
 > sysinstmsgs.fr not found
 > /usr/src/deistrib/i396/i386/ramdisks/ramdisk-big/sysinstmsgs.fr
 > 
 > retry of 'make release' (without clearing everything) starts relinking
 > lot of things from TOOL part - I forgot to disable the tools-build.
 > Inside compilers also lot of object files are rebuild .... (looks like
 > complete gcc build is done again)
 > So it will take some time until I come to the point where it was
 > failing before again ...
 > Will send update if it runs into same error or not.
 > 
 > I have not started amd64 build on this system till now - so may need
 > some more days to get to the point where I can test the 'fix'.
 > 
 > sorry
 > 
 > W. Stukenbrock
 > 
 > Am 14.01.2025 08:29, schrieb wgstuken%grimme-reitenspezial.de@localhost:
 >> Hi,
 >> 
 >> my current plan is to setup an unused system with 10.1 because I have
 >> always build the system from the sources.
 >> I have some patches inside that has not reached the main source, but
 >> some of then I need.
 >> So I have to integrate them again. (Some kernel related, some 
 >> user-level)
 >> 
 >> But I cannot give an eta for this atm. - lot of 'normal' work.
 >> I try to do this in parallel now to get forward with this.
 >> 
 >> 
 >> W. Stukenbrock
 >> 
 >> Am 13.01.2025 15:30, schrieb Andrius V:
 >>> On Mon, Jan 13, 2025 at 12:01â?¯PM wgstuken%grimme-reitenspezial.de@localhost via
 >>> gnats <gnats-admin%netbsd.org@localhost> wrote:
 >>>> 
 >>>> The following reply was made to PR port-amd64/58982; it has been 
 >>>> noted by GNATS.
 >>>> 
 >>>> From: wgstuken%grimme-reitenspezial.de@localhost
 >>>> To: gnats-bugs%netbsd.org@localhost
 >>>> Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 >>>>  netbsd-bugs%netbsd.org@localhost
 >>>> Subject: Re: port-amd64/58982: NetBSD 10.1 install image (amd64) 
 >>>> failed to
 >>>>  boot on J3455-ITX board (ASRock)
 >>>> Date: Mon, 13 Jan 2025 08:31:35 +0100
 >>>> 
 >>>>  Hi,
 >>> Hi,
 >>>> 
 >>>>  I had attached them .....
 >>> Sorry about that, maybe there were filtered out by mail server, not 
 >>> sure.
 >>> 
 >>>> 
 >>>>  now as inline copy again:
 >>>> 
 >>>>  output of cpuctl identify 0 ...
 >>>> 
 >>>>  cpu0: highest basic info 00000015
 >>>>  cpu0: highest extended info 80000008
 >>>>  cpu0: "Intel(R) Celeron(R) CPU J3455 @ 1.50GHz"
 >>>>  cpu0: Intel Atom (Goldmont) (686-class), 1497.60 MHz
 >>>>  cpu0: TSC freq CPUID 1497600000 Hz
 >>>>  cpu0: family 0x6 model 0x5c stepping 0xa (id 0x506ca)
 >>> ...
 >>>>  cpu family     : 6
 >>>>  model          : 92
 >>>>  model name     : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
 >>>>  stepping       : 10
 >>> Thanks again. I can confirm that your CPU has a newer stepping 0xa
 >>> (10), thus a workaround is not applied. I will prepare the patch to
 >>> remove the stepping check.
 >>> It will be possible to test either by building kernel from current
 >>> source or taking current image from
 >>> https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/ around a day
 >>> after commit.
 >>> I will inform separately and let's see how it boots afterwards.
 >>> 
 >>> Regards,
 >>> Andrius V