From owner-freebsd-bugs@FreeBSD.ORG  Mon Jul 28 11:46:06 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 77CD237B404; Mon, 28 Jul 2003 11:46:06 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9F51643F93; Mon, 28 Jul 2003 11:46:05 -0700 (PDT)
	(envelope-from schweikh@FreeBSD.org)
Received: from freefall.freebsd.org (schweikh@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6SIk5Up094981;
	Mon, 28 Jul 2003 11:46:05 -0700 (PDT)
	(envelope-from schweikh@freefall.freebsd.org)
Received: (from schweikh@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6SIk51r094977;
	Mon, 28 Jul 2003 11:46:05 -0700 (PDT)
Date: Mon, 28 Jul 2003 11:46:05 -0700 (PDT)
From: Jens Schweikhardt <schweikh@FreeBSD.org>
Message-Id: <200307281846.h6SIk51r094977@freefall.freebsd.org>
To: nickc01@corp.firstindustrial.com, schweikh@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
Subject: Re: kern/39447: 4.5R &4.6R Kernels fail to boot w/ AHA2940U2W
	attached to an IFT-3102 controller
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 18:46:06 -0000

Synopsis: 4.5R &4.6R Kernels fail to boot w/ AHA2940U2W attached to an IFT-3102 controller

State-Changed-From-To: feedback->closed
State-Changed-By: schweikh
State-Changed-When: Mon Jul 28 11:44:24 PDT 2003
State-Changed-Why: 
Closed after confirmation of submitter:

  The issue was related to the CAM layer probing the device's management
  interface (which is exposed as at the lun level) and taking 15-20
  minutes to timeout (under 4.6R). Disabling the management interface
  resolved the issue, but prevents the use the win32 based management
  console. I will note that this behavior has not been seen on the AIX
  and WinNT systems that we run with identical target disk arrays
  (meaning identical IFT-3102 controller and controller firmware).

http://www.freebsd.org/cgi/query-pr.cgi?pr=39447