Re: kern/52769

[Paul Goyette <paul%whooppee.com@localhost>]

The following reply was made to PR kern/52769; it has been noted by GNATS.

From: Paul Goyette <paul%whooppee.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/52769 
Date: Fri, 23 Feb 2018 08:11:33 +0800 (+08)

 On Fri, 23 Feb 2018, Paul Goyette wrote:
 
 > I can't add any more debug info to this, but I can say "me too".  I just 
 > encountered the same biolock hang, during a cvs update of a source tree 
 > sitting on an nvme(4) device.
 
 Just in case it matters, I'm on an amd64 system with MSIX interrupts:
 
 nvme0 at pci3 dev 0 function 0: Samsung Electronics (3rd vendor ID) product a804 (rev. 0x00)
 nvme0: NVMe 1.2
 nvme0: for admin queue interrupting at msix3 vec 0
 nvme0: Samsung SSD 960 PRO 512GB, firmware 2B6QCXP7, serial S3EWNX0K108171P
 nvme0: for io queue 1 interrupting at msix3 vec 1 affinity to cpu0
 nvme0: for io queue 2 interrupting at msix3 vec 2 affinity to cpu1
 nvme0: for io queue 3 interrupting at msix3 vec 3 affinity to cpu2
 nvme0: for io queue 4 interrupting at msix3 vec 4 affinity to cpu3
 nvme0: for io queue 5 interrupting at msix3 vec 5 affinity to cpu4
 nvme0: for io queue 6 interrupting at msix3 vec 6 affinity to cpu5
 nvme0: for io queue 7 interrupting at msix3 vec 7 affinity to cpu6
 ld0 at nvme0 nsid 1
 ld0: 476 GB, 62260 cyl, 255 head, 63 sec, 512 bytes/sect x 1000215216 sectors