From owner-freebsd-bugs@freebsd.org Tue Jun 21 14:33:53 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27B1BAC4499 for ; Tue, 21 Jun 2016 14:33:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17E0F12D5 for ; Tue, 21 Jun 2016 14:33:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5LEXqt9073754 for ; Tue, 21 Jun 2016 14:33:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 210438] NVME controller failure: panic Date: Tue, 21 Jun 2016 14:33:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: borjam@sarenet.es X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2016 14:33:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210438 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@FreeBSD.org Reporter: borjam@sarenet.es Created attachment 171648 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D171648&action= =3Dedit 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 =3D 0 but cc.en =3D 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 --=20 You are receiving this mail because: You are the assignee for the bug.=