From owner-freebsd-bugs@FreeBSD.ORG Wed Aug 3 12:50:09 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53F84106566B for ; Wed, 3 Aug 2011 12:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1093C8FC16 for ; Wed, 3 Aug 2011 12:50:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p73Co8jp056035 for ; Wed, 3 Aug 2011 12:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p73Co8JC056034; Wed, 3 Aug 2011 12:50:08 GMT (envelope-from gnats) Resent-Date: Wed, 3 Aug 2011 12:50:08 GMT Resent-Message-Id: <201108031250.p73Co8JC056034@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Stephane Lapie Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1D0F106566B for ; Wed, 3 Aug 2011 12:43:41 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 912C28FC13 for ; Wed, 3 Aug 2011 12:43:41 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p73ChfRC007932 for ; Wed, 3 Aug 2011 12:43:41 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p73ChfkA007910; Wed, 3 Aug 2011 12:43:41 GMT (envelope-from nobody) Message-Id: <201108031243.p73ChfkA007910@red.freebsd.org> Date: Wed, 3 Aug 2011 12:43:41 GMT From: Stephane Lapie To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/159414: isp(4)+gmultipath(8) : removing active fiber path, and gmultipath failing over to standby path provokes a kernel panic X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Aug 2011 12:50:09 -0000 >Number: 159414 >Category: kern >Synopsis: isp(4)+gmultipath(8) : removing active fiber path, and gmultipath failing over to standby path provokes a kernel panic >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Aug 03 12:50:08 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Stephane Lapie >Release: 8.2-RELEASE >Organization: Aozora Bank >Environment: FreeBSD fccbakpoda.aozora.lan 8.2-RELEASE-AZB FreeBSD 8.2-RELEASE-AZB #1: Thu Mar 3 18:39:55 UTC 2011 root@fcc4svnapf01.aozora.lan:/usr/obj/usr/src/sys/GENERIC amd64 >Description: When using FC HBAs handled by the isp(4) driver, gmultipath(8) (two fiber paths to access the same devices), and a ZFS pool, removing the active link and trying to provoke automatic failover, will cause a kernel panic. >How-To-Repeat: Remove the active fiber link (confirmable with activity LEDs from the storage unit) while I/O is going on. The kernel log will display some devices failing over, invalidated SCSI packets and devices, isp(4) handle timeouts, before panicking. Latest visible kernel trap message concerns the g_mp_kt thread. However, if gmultipath rotate is used to switch path on all devices, then it can be safely removed. This looks like a race condition between isp(4) loopdown provoking da(4) destruction, and gmultipath(8) failover. >Fix: >Release-Note: >Audit-Trail: >Unformatted: