From owner-freebsd-bugs@FreeBSD.ORG Fri Jan 25 22:10:03 2008 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 0DECF16A420 for ; Fri, 25 Jan 2008 22:10:03 +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 EE77213C4E5 for ; Fri, 25 Jan 2008 22:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0PMA2G8098808 for ; Fri, 25 Jan 2008 22:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0PMA2vG098807; Fri, 25 Jan 2008 22:10:02 GMT (envelope-from gnats) Date: Fri, 25 Jan 2008 22:10:02 GMT Message-Id: <200801252210.m0PMA2vG098807@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Jerry Walsh" Cc: Subject: re: kern/99529: [amr] dell poweredge 2600 with streamer powervault 100t-dat72 - device sa0 not exist X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jerry Walsh List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 22:10:03 -0000 The following reply was made to PR kern/99529; it has been noted by GNATS. From: "Jerry Walsh" To: bug-followup@FreeBSD.org, bs@vt.pl Cc: Subject: re: kern/99529: [amr] dell poweredge 2600 with streamer powervault 100t-dat72 - device sa0 not exist Date: Fri, 25 Jan 2008 21:33:53 +0000 ------=_Part_1578_23412125.1201296833058 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have the exact same machine and I too can reproduce this bug except in addition it exists in 6.2-STABLE as well as the recent 6.3-STABLE release. It was not until I rolled back to 6.0-STABLE-p18 that sa0 was detected again. ------=_Part_1578_23412125.1201296833058 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have the exact same machine and I too can reproduce this bug except in addition it exists in 6.2-STABLE as well as the recent 6.3-STABLE release.

It was not until I rolled back to 6.0-STABLE-p18 that sa0 was detected again.
------=_Part_1578_23412125.1201296833058--