From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 12 23:27:53 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 1D83516A41F for ; Thu, 12 Jan 2006 23:27:53 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id F38F743D72 for ; Thu, 12 Jan 2006 23:27:44 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 8B3171A3C30; Thu, 12 Jan 2006 15:27:44 -0800 (PST) Date: Thu, 12 Jan 2006 15:27:44 -0800 From: Alfred Perlstein To: Tom Cumming Message-ID: <20060112232744.GF72376@elvis.mu.org> References: <20060109185914.GD81914@elvis.mu.org> <20060109210653.GG81914@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: Vinod R Kashyap , 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: Thu, 12 Jan 2006 23:27:53 -0000 * Tom Cumming [060112 15:20] wrote: > > 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 It seems fine on 5-stable. I have the following plans: .) upgrade the device's firmware. .) turn off questionable devices in the system BIOS (nvidia ethernet+APCI) .) re-try with 6.x I'll let you know what I figure out. thank you! -- - Alfred Perlstein