Re: port-riscv/60482

"Jeff Rizzo via gnats" <[email protected]> Mon, 24 Aug 2026 16:10:02 +0000 (UTC)
Newsgroups	gmane.os.netbsd.bugs
Message-ID	<[email protected]>
The following reply was made to PR port-riscv/60482; it has been noted by GNATS.

From: Jeff Rizzo <[email protected]>
To: [email protected]
Cc: 
Subject: Re: port-riscv/60482
Date: Mon, 24 Aug 2026 09:06:57 -0700

 This is a multi-part message in MIME format.
 --------------wN1aVS2Qmq60sDec5sWSE0W1
 Content-Type: text/plain; charset=UTF-8; format=flowed
 Content-Transfer-Encoding: 7bit
 
 
 I was unable to duplicate this with NetBSD-11.0 (release), which
 should not be different than 11.0_RC6 in this regard - so perhaps
 this is related to the specific nvme?  Here is the relevant
 section from my dmesg:
 
 [   1.0000000] pci2 at jh7110pcie1 bus 0
 [   1.0000000] ppb1 at pci2 dev 0 function 0: vendor 1556 product 1111 (rev. 0x02)
 [   1.0000000] ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 5.0GT/s
 [   1.0000000] pci3 at ppb1 bus 1
 [   1.0000000] nvme0 at pci3 dev 0 function 0: vendor 144d product a809 (rev. 0x00)
 [   1.0000000] nvme0: NVMe 1.3
 [   1.0000000] nvme0: interrupting at plic0 irq 57
 [   1.0000000] nvme0: SAMSUNG MZALQ256HAJD-000L1, firmware BL1QFXV7, serial S4YDNF0NC73147
 [   1.0000000] ld4 at nvme0 nsid 1
 [   1.0000000] ld4: 238 GB, 31130 cyl, 255 head, 63 sec, 512 bytes/sect x 500118192 sectors (0 bytes/physsect)
 
 ...and it gets to multiuser without issue.
 
 The obvious difference I see is that my NVMe is version 1.3, not 1.4 
 (like all the ones that cause the hang).
 
 
 --------------wN1aVS2Qmq60sDec5sWSE0W1
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: 7bit
 
 <!DOCTYPE html>
 <html>
   <head>
 
     <meta http-equiv="content-type" content="text/html; charset=UTF-8">
   </head>
   <body>
     <br>
     <div class="moz-forward-container">
       <pre>I was unable to duplicate this with NetBSD-11.0 (release), which
 should not be different than 11.0_RC6 in this regard - so perhaps
 this is related to the specific nvme?  Here is the relevant
 section from my dmesg:
 
 [   1.0000000] pci2 at jh7110pcie1 bus 0
 [   1.0000000] ppb1 at pci2 dev 0 function 0: vendor 1556 product 1111 (rev. 0x02)
 [   1.0000000] ppb1: PCI Express capability version 2 &lt;Root Port of PCI-E Root Complex&gt; x1 @ 5.0GT/s
 [   1.0000000] pci3 at ppb1 bus 1
 [   1.0000000] nvme0 at pci3 dev 0 function 0: vendor 144d product a809 (rev. 0x00)
 [   1.0000000] nvme0: NVMe 1.3
 [   1.0000000] nvme0: interrupting at plic0 irq 57
 [   1.0000000] nvme0: SAMSUNG MZALQ256HAJD-000L1, firmware BL1QFXV7, serial S4YDNF0NC73147
 [   1.0000000] ld4 at nvme0 nsid 1
 [   1.0000000] ld4: 238 GB, 31130 cyl, 255 head, 63 sec, 512 bytes/sect x 500118192 sectors (0 bytes/physsect)
 
 ...and it gets to multiuser without issue.
 
 </pre>
       <p>The obvious difference I see is that my NVMe is version 1.3,
         not 1.4 (like all the ones that cause the hang).</p>
       <p><br>
       </p>
     </div>
   </body>
 </html>
 
 --------------wN1aVS2Qmq60sDec5sWSE0W1--