From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 06:55:44 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 F2EFC16A4CE for ; Tue, 20 Jul 2004 06:55:43 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9269B43D1D for ; Tue, 20 Jul 2004 06:55:43 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6K71k7D057227; Tue, 20 Jul 2004 01:01:46 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40FCC1AA.9060609@freebsd.org> Date: Tue, 20 Jul 2004 00:54:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eriksson References: In-Reply-To: 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: freebsd-current@freebsd.org Subject: Re: HEADS UP [Re: thread+preemption stability improvement] 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, 20 Jul 2004 06:55:44 -0000 Daniel Eriksson wrote: >>I have set aside some time on the server (normally a busy >>production-type >>server) to try a few different configs (SHED_ULE instead of SHED_4BSD, >>turning off apic, removing polling) to see if any of them >>will have any >>impact. > > > I have just tried a number of different combinations of sheduler, acpi, > apic, polling, ... > > No matter what I do, the only way to prevent errors like the one below seems > to be to run with preemption turned off. > > Interrupt storm detected on "irq20: atapci4"; throttling interrupt source > ad20: FAILURE - already active DMA on this device > ad20: setting up DMA failed > > See my recent mail on this list entitled "Kernel preemption leads to SATA > instability (how to debug?)" for machine configuration and further > information. > > /Daniel Eriksson > Thanks for the report. I'm sure that there is a bug of some sort in the ATA driver that is being exposed by PREEMPTION, but I'm also going to consider turning off preemption in the next day or two since this isn't the only lingering problem. Scott