From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 08:47:07 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACFBC16A4CF; Sat, 24 Jan 2004 08:47:07 -0800 (PST) Received: from vir2.relay.fluke.com (vir2.relay.fluke.com [129.196.184.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1380D43D67; Sat, 24 Jan 2004 08:47:03 -0800 (PST) (envelope-from paul@fluke.com) Received: from [192.168.0.106] ([129.196.191.160] unverified) by vir2.relay.fluke.com with Microsoft SMTPSVC(5.0.2195.5329); Sat, 24 Jan 2004 08:47:00 -0800 Date: Sat, 24 Jan 2004 08:46:57 -0800 (PST) From: Paul Lutt X-X-Sender: paul@myst.wavecable.com To: "Matthew N. Dodd" In-Reply-To: <20040124054046.W57327@sasami.jurai.net> Message-ID: References: <20040124054046.W57327@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 24 Jan 2004 16:47:00.0153 (UTC) FILETIME=[AFA9F290:01C3E299] cc: Paul Lutt cc: freebsd-hardware@FreeBSD.ORG Subject: Re: HP DL360 G3 Hangs on Disk Removal X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2004 16:47:07 -0000 On Sat, 24 Jan 2004, Matthew N. Dodd wrote: > On Fri, 23 Jan 2004, Paul Lutt wrote: > > What I got was a system that wasn't totally locked up, but it could not > > perform any disk access. I had a shell open on the console. Pressing > > enter would bring up a new prompt. Trying to do anything that required > > reading the disk would cause the shell to hang. > > I've seen this with the ida(4) driver as well, though only on re-insertion > of a hotswap disk. Failure was the same. With the system cracked open > and the status LEDs on the controller available for viewing you could see > when the controller locked up. > > After going over the driver and instrumenting the interrupt handler and > installing a watchdog timeout routine I see no way that this condition > could be caused by the driver, unless we're supposed to be doing something > that we don't know about. > > What model CISS card do you have? > > -- > 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 > lspci shows the following (Yes, I've installed Debian in the interim) 00:04.0 RAID bus controller: Compaq Computer Corporation Smart Array 5i/532 (rev 01) This is all a bit frustrating because I have several Linux based Proliant servers with the CISS hardware and they behave properly when the disk is removed and re-inserted. We also have LOTS of Windows based servers that behave properly given the same test. Makes me suspect some sort of driver issue. Paul Lutt Fluke Corporation