From owner-freebsd-fs@freebsd.org  Wed Feb 24 00:01:52 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 235BCAB2B8F
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 24 Feb 2016 00:01:52 +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 1446A1644
 for <freebsd-fs@FreeBSD.org>; Wed, 24 Feb 2016 00:01:52 +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 u1O01pow077423
 for <freebsd-fs@FreeBSD.org>; Wed, 24 Feb 2016 00:01:51 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 207432] panic: nvme_ctrlr_intx_handler
Date: Wed, 24 Feb 2016 00:01:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-BETA2
X-Bugzilla-Keywords: crash, needs-qa, regression
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: jimharris@FreeBSD.org
X-Bugzilla-Flags: mfc-stable10?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207432-3630-60W5UQR5K7@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207432-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-207432-3630@https.bugs.freebsd.org/bugzilla/>
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-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2016 00:01:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207432

--- Comment #7 from commit-hook@freebsd.org ---
A commit references this bug:

Author: jimharris
Date: Wed Feb 24 00:01:10 UTC 2016
New revision: 295944
URL: https://svnweb.freebsd.org/changeset/base/295944

Log:
  nvme: fix intx handler to not dereference ioq during initialization

  This was a regression from r293328, which deferred allocation
  of the controller's ioq array until after interrupts are enabled
  during boot.

  PR:           207432
  Reported and tested by: Andy Carrel <wac@google.com>
  MFC after:    3 days
  Sponsored by: Intel

Changes:
  head/sys/dev/nvme/nvme_ctrlr.c

--=20
You are receiving this mail because:
You are on the CC list for the bug.=