From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 02:12:45 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 89D2816A503 for ; Thu, 11 Mar 2004 02:12:45 -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 60D5F43D39 for ; Thu, 11 Mar 2004 02:12:44 -0800 (PST) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (csc-gw1.novi.dk [130.225.63.24]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i2BACQsX037998; Thu, 11 Mar 2004 11:12:41 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <40503B8A.7040105@DeepCore.dk> Date: Thu, 11 Mar 2004 11:12:26 +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: Putinas Piliponis References: <001801c40745$043449d0$1e64a8c0@spotripoli.local> In-Reply-To: <001801c40745$043449d0$1e64a8c0@spotripoli.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 X-Mailman-Approved-At: Thu, 11 Mar 2004 05:24:08 -0800 cc: current@freebsd.org Subject: Re: still spurious interrupts with 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: Thu, 11 Mar 2004 10:12:45 -0000 Putinas Piliponis wrote: > Hi all, > I upgraded from 5.2.1 to todays current and I get this: > ( my mobo is Asus P4P800 Deluxe ) > If I boot with hint acpi disabled - I get panic > If I boot with apic disabled - doesn't make difference > HTT is disabled in bios, and SMP not compiled in kernel. > > If I try to boot in verbose mode, I continues repeating this > ata3: spurious interupt - status=0x50 error=0x00 > ( really alot I even cannot get dmesg output from booting, because this ata3: blabla fill ups all the available space for msg ) > but it still continues booting. Getting spurious interrupts does not nessesarily mean that something is wrong, they will show up if you have shared irq's... If that is not the problem it most likelu is a problem with interrupt routing or semialr resource messups so that the interrupt is not properly ack'ed to the device causing interrupt storms... -- -Søren