From owner-freebsd-current@FreeBSD.ORG Fri Nov 7 14:31:57 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 D829C16A4CF for ; Fri, 7 Nov 2003 14:31:57 -0800 (PST) Received: from mail.speakeasy.net (mail8.speakeasy.net [216.254.0.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FA4243FD7 for ; Fri, 7 Nov 2003 14:31:57 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 9482 invoked from network); 7 Nov 2003 22:31:56 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 7 Nov 2003 22:31:56 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id hA7MVRce096493; Fri, 7 Nov 2003 17:31:27 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3FAC118B.1090800@liwing.de> Date: Fri, 07 Nov 2003 17:31:27 -0500 (EST) From: John Baldwin To: Jens Rehsack X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Lars Eggert cc: current@freebsd.org 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 22:31:58 -0000 On 07-Nov-2003 Jens Rehsack wrote: > 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. Grrr, ok. Can you try the patch at http://www.FreeBSD.org/~jhb/patches/io_apic.patch and nab a boot -v dmesg with ACPI enabled? Thanks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/