From owner-freebsd-stable@FreeBSD.ORG Thu Apr 7 13:31:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8905516A4CE for ; Thu, 7 Apr 2005 13:31:07 +0000 (GMT) Received: from mail.distrust.net (mail.distrust.net [69.93.230.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF2E743D49 for ; Thu, 7 Apr 2005 13:31:06 +0000 (GMT) (envelope-from dsze@alumni.uwaterloo.ca) Received: from eeyore.distrust.net (CPE00a0c978120d-CM00122570472e.cpe.net.cable.rogers.com [70.24.0.197]) (authenticated bits=0) by mail.distrust.net (8.13.1/8.12.11) with ESMTP id j37DV5du012207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 7 Apr 2005 08:31:06 -0500 (CDT) (envelope-from dsze@alumni.uwaterloo.ca) Message-Id: <6.2.1.2.2.20050407092323.05dfa160@mail.distrust.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Thu, 07 Apr 2005 09:31:12 -0400 To: Anthony Downer From: David Sze In-Reply-To: <444747A80F040044A3C2F4F1339C47EB044E07D9@LONSMSXM01.emea.i me.reuters.com> References: <444747A80F040044A3C2F4F1339C47EB044E07D9@LONSMSXM01.emea.ime.reuters.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV 0.83/813/Thu Apr 7 05:20:51 2005 on mail.distrust.net X-Virus-Status: Clean cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.11-Release IPS device issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 13:31:07 -0000 At 09:13 AM 06/04/2005 +0100, Anthony Downer wrote this to All: >Hello Folks, > >(I am afraid) we are using FreeBSD as the initial boot/hardware/disk >configuration tool for our Standard Windows Server builds. > >We have a bootable CD that identifies hardware, partitions disk zero, >copies the install files over and commences the Windows installation >process. > >This is working fine on a large number of machines/scsi controllers, but >the ServeRAID is causing some issues. >I am attempting to use the 4.11-Release IPS driver on an IBM xSeries 342 >with a ServeRAID 4Lx RAID controller. >(Controller BIOS/Firmware 7.10.18 - Two 18GB drives in a mirrored >formation) > >Whilst we have successfully tested 5.3 with the IPS driver for this >purpose we are getting some odd errors in 4.11 >(At this time it is not possible to migrate to 5.3 for our purposes) > >When copying a large number of files (the i386 folder) using cp from a >mounted CD to a DOS formatted partition on ipsd0 we are getting the >following errors: >---cut here--- >devstat_end_transaction: HELP!! busy_count for ipsd0 is < 0 (-1)! >panic: vwakeup: neg numoutput > >syncing disks... ips0: WARNING: command timeout. Adapter is in toaster >mode, resetting to known state >devstat_end_transaction: HELP!! busy_count for ipsd0 is < 0 (-1)! >ips0: resetting adapter, this may take up to 5 minutes >ips0: syncing config >ips0: ERROR: unable to get a command! can't sync cache! >ips0: adapter clear failed >ips0: AIEE! adapter reset failed, giving up and going home! Have a nice >day. >---cut here--- I get the same panic on an IBM xSeries 346 with a ServeRAID-7k controller (Six 15K RPM 36GB drives, two as RAID1, four as RAID0). The panic occurs at random points while sysinstall is copying distributions. If I do a minimal install, that completes successfully, but then the same panic occurs while building a new kernel. 5.4-RC1 seems to work fine, but I'm in the same boat as you; my customer doesn't want to upgrade to RELENG_5 yet. I'm going to look at backporting the -CURRENT ips driver to RELENG_4, I'll post patches (and a PR) if I'm successful.