From owner-freebsd-current@FreeBSD.ORG Sun Mar 21 07:29:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D77EA16A4CE for ; Sun, 21 Mar 2004 07:29:00 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A66E43D46 for ; Sun, 21 Mar 2004 07:29:00 -0800 (PST) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i2LFShjf069690; Sun, 21 Mar 2004 16:28:58 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <405DB4AB.1010306@DeepCore.dk> Date: Sun, 21 Mar 2004 16:28:43 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040126 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <405B9DCD.9040907@6by9.org> <0a0c01c40e90$2d86e070$32cba1cd@science1> <000401c40f33$86ce9210$1e64a8c0@spotripoli.local> <405D7D7F.3090209@DeepCore.dk> <20040321140202.5e93401c@Magellan.Leidinger.net> In-Reply-To: <20040321140202.5e93401c@Magellan.Leidinger.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: current@freebsd.org cc: Putinas Piliponis Subject: Re: system lockup - ata spurious interrupts - somehow updated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2004 15:29:01 -0000 Alexander Leidinger wrote: >>That said, the ICH5 support is written "blindfolded" as I do not have >>any such HW here in the lab. So if there is a problem with ATA on those, >>someone with the HW and enough kernel clue should look into it (or >>someone could land the needed HW in my lab, which could also bring >>support for the SW RAID on intel's)... > > I have the hardware and I'm willing to fix this problem. What kernel > clue are we talking about? Enough to know your way around the kernel, instrument code to see what is going on and do new code bits to fix potential problems etc etc, that kind of thing. In some cases having test HW around to see if there are physical interrupts delivered, if devices are really selected on the HW level etc, can be very handy as well.. Most importantly is to have lots of time and persistence though... -- -Søren