Re: Tracing NetBSD sun4v issues

[Sad Clouds <cryintothebluesky%gmail.com@localhost>]

On Fri, 23 Oct 2026 17:58:21 +0000 (UTC)
Palle Lyckegaard <palle%netbsd.org@localhost> wrote:

> On Fri, 23 Oct 2026, Sad Clouds wrote:
> 
> > [   1.0000000] cbus0 at vbus0
> > [   1.0000000] vdsk0 at cbus0 chan 0x0: ivec 0x0, 0x1
> > [   1.0000000] scsibus0 at vdsk0: 2 targets, 1 lun per target
> > [   1.0000000] "pciv-communication" at cbus0 not configured
> > [   1.0000000] "virtual-domain-service" at cbus0 not configured
> > [   1.0000000] vrtc0 at vbus0
> > [   1.0000000] pcons0 at mainbus0
> > [   1.0000000] WARNING: system needs entropy for security; see entropy(7)
> > [   1.0000262] No counter-timer -- using %stick at 1415.103MHz as system clock.
> > [   1.0000262] sd0 at scsibus0 target 1 lun 0: <SUN, Virtual Disk, 1.1> disk fixed
> > [   1.0000262] sd0: fabricating a geometry
> > [   1.0000262] sd0: 2048 MB, 2048 cyl, 64 head, 32 sec, 512 bytes/sect x 4194304 sectors
> > [   1.0000262] sd0: fabricating a geometry
> > [   1.0216888] swwdog0: software watchdog initialized
> > [   1.0216888] root on sd0a dumps on sd0b
> > [   1.0216888] root file system type: ffs
> > [   1.0216888] kern.module.path=/stand/sparc64/11.0/modules
> >
> 
> Thank you for the console output.
> 
> So the system hangs here after the last line or does it crash afterwards?

No, NetBSD-11 boots fine, that is the last relevant kernel message
before /bin/sh is started in place of init. It is NetBSD-current that
fails to boot due to interrupt issues.