From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 13 02:10:15 2006 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9054A16A41F for ; Fri, 13 Jan 2006 02:10:15 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E78243D62 for ; Fri, 13 Jan 2006 02:10:05 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: by uproxy.gmail.com with SMTP id j3so54907ugf for ; Thu, 12 Jan 2006 18:10:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Jl0+wfhT1+VY80SQ32D25jAI8ScXTYsdHQxmpVp2X7LuhaARFKVxLnVI1U8gPE211etOWSjTvdXN1CwMqC0FN64mHdLS+dApBSMK8Oph6+p1n98EJmShueB/c+y6yKI/UdJjhMTlpOJ1aEhSLfIqG5zHw/MECVml7lTwHSF7jzE= Received: by 10.48.202.9 with SMTP id z9mr15059nff; Thu, 12 Jan 2006 12:34:50 -0800 (PST) Received: by 10.48.14.8 with HTTP; Thu, 12 Jan 2006 12:34:49 -0800 (PST) Message-ID: Date: Thu, 12 Jan 2006 12:34:49 -0800 From: Tom Cumming To: Vinod R Kashyap In-Reply-To: MIME-Version: 1.0 References: <20060109185914.GD81914@elvis.mu.org> <20060109210653.GG81914@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Alfred Perlstein , tcumming@amcc.com, scsi@freebsd.org Subject: Re: 3ware 9500 locks up on 6.0-stable! X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2006 02:10:15 -0000 When it says it's initializing (and you said 12%). Does the initializing make forward progress, or is it stuck at 12%? Why I'm asking, is that Vinode says you'd see these messages under heavy load, and initializing + any load might be a, "heavy" load. It still doesn't explain a hard lockup. The messages above are similar to a SCSI "busy" status... that's normal. There's some more things to check using the cli, I have to look try'm here first. Do you know of any specific steps you can do to reliably reproduce the lockups? I get the impression there should be. tom.c