From owner-freebsd-current@FreeBSD.ORG Fri Mar 19 17:26:46 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 2729916A4CE for ; Fri, 19 Mar 2004 17:26:46 -0800 (PST) Received: from imap.multamedio.de (imap.multamedio.de [62.52.48.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50A9243D3F for ; Fri, 19 Mar 2004 17:26:45 -0800 (PST) (envelope-from alex@6by9.org) Received: from 6by9.org (pD9E69330.dip.t-dialin.net [217.230.147.48]) ESMTP id B0A84296C; Sat, 20 Mar 2004 02:26:42 +0100 (CET) Message-ID: <405B9DCD.9040907@6by9.org> Date: Sat, 20 Mar 2004 02:26: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: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: 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 01:26:46 -0000 > Hi all, > Just today I saw the commitments to /dev/ata src for releng 5_2 and rebuild kernel ( custom ) and the system which was working fine for few days, lockup in a few hours with WRITE_DMA error on LBA XXX .. the disk is attached to ICH5 SATA controller and build raid with atacontrol ( but in bios raid its disabled ). As somewhere I saw , it's recommended to disable hyperthreading and now I am running with disabled. My mb is Asus P4P800 deluxe > Just now i tried to reboot the computer for geting verbose dmesg, and also one problem comes here, it's says syncing disk, done, Uptime XX minutes and stops without actual rebooting > ( later I find out what couse this problems - at this time it gives me million spurious interupts on console ) > Hmm and I cannot boot it in verbose mode... > it gives me millions of spurious interrupts on ata2 and ata3 controllers ...both with hyperthreadin on and off... > I just enabled on running system > sysctl hw.acpi.verbose=1 > sysctl debug.bootverbose=1 > and I can see in the log this messages: > this amount of messages are generated in 1-2 minutes period > also as well I tested my older kernel - if I boot in verbose mode I get same thousands spurious interrupts... > > ata3: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata2: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > ata3: spurious interrupt - status=0x50 error=0x00 > > any help ? Hi Putinas, 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. Regards, Alexander Mueller