From owner-freebsd-current@FreeBSD.ORG Fri Nov 7 13:41:36 2003 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 38CFA16A4CE for ; Fri, 7 Nov 2003 13:41:36 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 001CF43FA3 for ; Fri, 7 Nov 2003 13:41:34 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 69151 invoked from network); 7 Nov 2003 21:41:31 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 7 Nov 2003 21:41:31 -0000 Message-ID: <3FAC118B.1090800@liwing.de> Date: Fri, 07 Nov 2003 21:41:31 +0000 From: Jens Rehsack User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031102 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: Lars Eggert References: <3FAC0E7F.9040607@isi.edu> In-Reply-To: <3FAC0E7F.9040607@isi.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: John Baldwin Subject: Re: New interrupt code slows hyperthreading down 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: Fri, 07 Nov 2003 21:41:36 -0000 Lars Eggert wrote: > John Baldwin wrote: > >> On 07-Nov-2003 Lars Eggert wrote: >> >>> Jens Rehsack wrote: >>> >>>> interrupt total rate >>>> irq1: atkbd0 512 2 >>>> irq8: rtc 23419 127 >>>> irq13: npx0 1 0 >>>> irq14: ata0 4422 24 >>>> irq15: ata1 82 0 >>>> irq16: uhci0 uhci3 5379815 29238 >>> >>> >>> This looks similar to what I described in the "fwohci0 running wild" >>> thread. In both cases, irq16 seems to cause the problem... >> >> >> Really. Does this only happen with ACPI enabled? > > Don't know about "only", since I have never booted this machine without > ACPI. I'll test next time I'm rebooting. Don't do it. I do it for testing a few minutes ago - and it prevents irq 16 from storming. But it does because the machine hangs at boot with: isa_probe_children: probing PnP devices I let it probe for about 10 minutes (you'll never know :-)), but it wont do. Jens