Re: kern/53059 (repeated nvmectl identify nvme0 locks up sytem)

[Frank Kardel <kardel%netbsd.org@localhost>]

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

From: Frank Kardel <kardel%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/53059 (repeated nvmectl identify nvme0 locks up sytem)
Date: Fri, 16 Mar 2018 20:10:19 +0100

 It seems to be with all ioctl triggered admin-q interactions that are 
 processed via polled command. E. g, smartd will lead to a system lockup 
 after 22:30h.
 
 Thanks for looking into it.
 
 
 On 03/16/18 20:05, jdolecek%NetBSD.org@localhost wrote:
 > Synopsis: repeated nvmectl identify nvme0 locks up sytem
 >
 > State-Changed-From-To: feedback->analyzed
 > State-Changed-By: jdolecek%NetBSD.org@localhost
 > State-Changed-When: Fri, 16 Mar 2018 19:05:37 +0000
 > State-Changed-Why:
 > That patch is unlikely to help here. I'm going to refactor the code
 > to avoid polled command for identify, which should fix the issue.
 >
 >
 >