kern/54761: nvme corruption on GENERIC without DIAGNOSTIC

[abs%absd.org@localhost]

>Number:         54761
>Category:       kern
>Synopsis:       nvme corruption on GENERIC without DIAGNOSTIC
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 13 18:25:00 +0000 2019
>Originator:     abs%absd.org@localhost
>Release:        NetBSD 9.0_RC1
>Organization:
	
>Environment:
System: NetBSD forsaken.absd.org 9.0_RC1 NetBSD 9.0_RC1 (GENERIC_DIAGNOSTIC) #0: Thu Dec 5 11:44:08 GMT 2019 abs%iris.absd.org@localhost:/opt/netbsd/9/sys/arch/amd64/compile/GENERIC_DIAGNOSTIC amd64
Architecture: x86_64
Machine: amd64
>Description:
	Significant filesystem corruption seen when updating a netbsd-9 machine from releng 2019-11-19 to 2019-12-03

	System is running /home as wapbl on cgd0 on ld0 at nvme0 (samsung MZVLB512HAJQ-000L7)

	System "seemed" stuttery in Firefox and IDEA, gradle build hung and on clean reboot significant
        corruption found (lost local copy of two git repos)

	Tracking releng builds of netbsd-9
          2019-11-19 OK
          2019-12-03 BAD
          2019-12-05 BAD
          2019-12-05 Locally built GENERIC+DIAGNOSTIC OK

>How-To-Repeat:
        Boot a recent netbsd-9 kernel without DIAGNOSTIC using wapbl on cgd0 on ld0 at nvme0, or
        (presumably) the appropriate subset thereof
>Fix:
        Obvkously a workaround is to include DIAGNOSTIC