From owner-freebsd-proliant@FreeBSD.ORG Thu Oct 19 03:31:31 2006 Return-Path: X-Original-To: freebsd-proliant@FreeBSD.org Delivered-To: freebsd-proliant@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B099116A412; Thu, 19 Oct 2006 03:31:31 +0000 (UTC) (envelope-from aquatique@rusunix.org) Received: from rusunix.org (rusunix.org [81.176.113.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F34343D5F; Thu, 19 Oct 2006 03:31:31 +0000 (GMT) (envelope-from aquatique@rusunix.org) Received: by rusunix.org (Postfix, from userid 1111) id 1629D4518F; Thu, 19 Oct 2006 10:31:27 +0700 (OMSST) Date: Thu, 19 Oct 2006 10:31:27 +0700 From: "Evgueni V. Gavrilov" To: freebsd-proliant@FreeBSD.org Message-ID: <20061019033126.GA21428@rusunix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.12-2006-07-14 Cc: Mike Smith Subject: ProLiant DL360 G4p: ciss(4) boottime oddity X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2006 03:31:31 -0000 ehlo I've got several ProLiant DL360 G4p servers running RELENG_6. Everything is ok except boottime: boot process becomes frozen for several minutes after these messages Oct 18 16:38:35 siziph kernel: da0 at ciss0 bus 0 target 0 lun 0 Oct 18 16:38:35 siziph kernel: da0: Fixed Direct Access SCSI-0 device Oct 18 16:38:35 siziph kernel: da0: 135.168MB/s transfers Oct 18 16:38:35 siziph kernel: da0: 286095MB (585922680 512 byte sectors: 255H 63S/T 36472C) Several minutes later boot process proceeds Oct 18 16:38:35 siziph kernel: GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install. Oct 18 16:38:35 siziph kernel: Trying to mount root from ufs:/dev/da0s1a One of those servers (DL360 G4p) still out of production, so I can utilize it for investigation on the trouble. Are there any developers/hackers who interested in solving of the trouble? Also I would be glad to receive advises since I ain't kernel hacker :)