From owner-freebsd-current@FreeBSD.ORG Sat Mar 20 11:52:42 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 D10DB16A4CE for ; Sat, 20 Mar 2004 11:52:42 -0800 (PST) Received: from imap.multamedio.de (imap.multamedio.de [62.52.48.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40CA343D1F for ; Sat, 20 Mar 2004 11:52:42 -0800 (PST) (envelope-from alex@6by9.org) Received: from 6by9.org (pD95422C0.dip.t-dialin.net [217.84.34.192]) ESMTP id 730DC29AC; Sat, 20 Mar 2004 20:52:39 +0100 (CET) Message-ID: <405CA105.5050606@6by9.org> Date: Sat, 20 Mar 2004 20:52:37 +0100 From: Alexander Mueller User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030524 X-Accept-Language: de-de, en-us, en MIME-Version: 1.0 To: Elliot Finley References: <405B9DCD.9040907@6by9.org> <0a0c01c40e90$2d86e070$32cba1cd@science1> In-Reply-To: <0a0c01c40e90$2d86e070$32cba1cd@science1> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: system lockup - ata related and spurious interrupts 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: Sat, 20 Mar 2004 19:52:42 -0000 > ----- Original Message ----- > From: "Alexander Mueller" > To: > Sent: Friday, March 19, 2004 6:26 PM > Subject: system lockup - ata related and spurious interrupts > > > >>I can't offer you any help but at least I can tell you that I'm >>experiencing exactly the same two problems: TIMEOUT - WRITE_DMA >>when hyperthreading is enabled and inability to reboot or power >>off when hyperthreading is disabled. My hardware is similar to >>yours: Asus P4C800E Deluxe with P4 3.0 GHz using the onboard >>SATA controller integrated into the ICH5. My hard disk is a >>WD Raptor 740GD. Currently nobody seems to take care of this >>problem although there must be quity a lot of people out there >>running into similar troubles. > > > plus one. > > Elliot Shame on me! I should have taken a look a the freebsd-current archive first. I guess it's no excuse that I've subscribed to freebsd-current just yesterday... Alexander