Re: port-sparc64/59787: Enabling DIAGNOSTIC for GENERIC on sparc64 (Ultra-45) causes SIR (Software Initiated Reset) at kernel init.

["Alexander Schreiber via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Alexander Schreiber <als%thangorodrim.ch@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-sparc64/59787: Enabling DIAGNOSTIC for GENERIC on sparc64
 (Ultra-45) causes SIR (Software Initiated Reset) at kernel init.
Date: Tue, 25 Nov 2025 21:24:31 +0100

 On Sun, Nov 23, 2025 at 11:35:00PM +0000, gnats-admin%netbsd.org@localhost wrote:
 > Thank you very much for your problem report.
 > It has the internal identification `port-sparc64/59787'.
 > The individual assigned to look at your
 > report is: port-sparc64-maintainer. 
 
 Did some simple testing by removing spkr from the config and rebooting.
 This succeeded and the machine booted successfully.
 
 Updated diff:
 
 diff -urN GENERIC GALADRIEL 
 --- GENERIC     2023-10-09 23:33:46.000000000 +0000
 +++ GALADRIEL   2025-11-25 19:47:38.501583684 +0000
 @@ -82,7 +82,7 @@
  options        DDB                     # kernel dynamic debugger
  options        DDB_HISTORY_SIZE=100    # enable history editing in DDB
  options        DDB_VERBOSE_HELP        # enable verbose online help
 -#options       DDB_ONPANIC=1           # see also sysctl(7): `ddb.onpanic'
 +options        DDB_ONPANIC=1           # see also sysctl(7): `ddb.onpanic'
  
  ## You may also use gdb, on another computer connected to this machine over
  ## a serial port.
 @@ -100,7 +100,7 @@
  ## Adds code to the kernel that does internal consistency checks, and will
  ## cause the kernel to panic if corruption of internal data structures
  ## is detected.
 -#options       DIAGNOSTIC      # extra kernel sanity checking
 +options        DIAGNOSTIC      # extra kernel sanity checking
  
  ## Enable (possibly expensive) debugging code that may also display messages
  ## on the system console
 @@ -745,7 +745,7 @@
  
  audio*         at audiobus?
  
 -spkr*          at audio?                       # PC speaker (synthesized)
 +# spkr*                at audio?                       # PC speaker (synthesized)
  
  midi*          at midibus?
 
 
 It looks like something in the spkr driver is unhappy enough to
 trigger a reset. So I gain DIAGNOSTIC but lose the spkr .. eh,
 acceptable trade-off.
 
 I'm happy to try patches if applicable.
 
 Kind regards,
            Alex.
 -- 
 "Opportunity is missed by most people because it is dressed in overalls and
  looks like work."                                      -- Thomas A. Edison