[Bug 210438] NVME controller failure: panic
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jun 21 14:33:53 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210438
Bug ID: 210438
Summary: NVME controller failure: panic
Product: Base System
Version: 10.3-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: borjam at sarenet.es
Created attachment 171648
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=171648&action=edit
backtrace in ddb
I have had a controller failure in a Supermicro server with 10 NVMe drives.
The controller failure triggered a PANIC and the system panics in subsequent
reboots unless the affected drive is pulled from the system. (The drive is
fine, it seems to be a backplane/controller problem).
I am not sure wether this is a bug or an unavoidable problem, but it would be
desirable to avoid a panic due to a disk controller failure.
The first symptom was these messages in /var/log/messages at night, when the
controller
failed, apparently:
Jun 17 03:01:33 nvme1 kernel: nvme3: resetting controller
Jun 17 03:01:33 nvme1 kernel: nvme3: nvme_ctrlr_wait_for_ready called with
desired_val = 0 but cc.en = 1
In subsequent reboots, the system panics. Screen capture of a backtrace from
ddb is attached. I can't get it generate a proper dump, unfortunately
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list