From owner-freebsd-current@FreeBSD.ORG Mon May 31 22:20:31 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 098C016A4CE for ; Mon, 31 May 2004 22:20:31 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A25F143D41 for ; Mon, 31 May 2004 22:20:30 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i515RD5Z008161; Mon, 31 May 2004 23:27:13 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40BC11FA.3050404@freebsd.org> Date: Mon, 31 May 2004 23:19:54 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Ambrisko References: <200406010351.i513pLDW085953@ambrisko.com> In-Reply-To: <200406010351.i513pLDW085953@ambrisko.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Tony Byrne cc: current@freebsd.org Subject: Re: Lockups with Intel ICH5 SATA 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: Tue, 01 Jun 2004 05:20:31 -0000 Doug Ambrisko wrote: > Tony Byrne writes: > | In recent weeks my FreeBSD current box has been experiencing frequent > | hard lockups. Seldom a day goes by without the machine freezing > | solid. My hunch is that this is somehow related to the onboard Intel > | ICH5 controller and SATA HD, because during reboot after a lockup, > | the machine often complain of a DMA timeout that hangs the box > | while reading from the SATA drive. > > FYI, if the drive has a media error or does a spin down/spin up sequence > things will hang since the ata driver currently doesn't deal with the > SATA PHY registers. After a while of ignoring various issues flagged > in these bits your system will lock up solid on a inb/outb to the controller. > > Doug A. Can you explain this a bit more? Is the driver ignoring the interrupt and thus allowing an interrupt storm? Or is it ACK'ing the interrupt, but the ICH5 controller is expecting a certain further response that it's not getting? Or is it masking the interrupt entirely which in turn exposes a flaw in the ICH5 hardware? Scott