From mboxrd@z Thu Jan 1 00:00:00 1970 From: keith.busch@intel.com (Keith Busch) Date: Mon, 17 Oct 2016 12:20:43 -0400 Subject: NVME Subsystem Reset Question In-Reply-To: References: <20161012173411.GA12681@localhost.localdomain> <20161014212731.GD19383@localhost.localdomain> Message-ID: <20161017162043.GB19846@localhost.localdomain> On Mon, Oct 17, 2016@02:42:56PM +0000, Jeffrey Lien wrote: > We're using the 3.10.0-493 kernel from a Red hat 7.3 Beta install. I believe the nvme inbox driver here was back ported from the 4.5 kernel release. I've attached the dmesg output from both the intel and western digital device. Both are very similar if not identical. It does appear the link is disabled when the driver's health check runs. It may be possible it observes all 1's on a transient link state change in the health check. I'm not sure right now of a safe way to distinguish a permanently disabled device vs a transient condition with the information available. How are you sending a subsystem reset? On the Intel device, I assumed you were using a D3600, but this looks like a P3600 based on the model and firmware revision. That controller doesn't support subsystem reset, so the ioctl method should have returned -ENOTTY.