From owner-freebsd-current@FreeBSD.ORG Sun Nov 9 17:06:44 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 7A6C016A4CE for ; Sun, 9 Nov 2003 17:06:44 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 180CE43FDF for ; Sun, 9 Nov 2003 17:06:42 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 17643 invoked from network); 10 Nov 2003 01:06:40 -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 ; 10 Nov 2003 01:06:40 -0000 Message-ID: <3FAEE49F.4080003@liwing.de> Date: Mon, 10 Nov 2003 01:06:39 +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: John Baldwin References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: Mon, 10 Nov 2003 01:06:44 -0000 John Baldwin wrote: > On 07-Nov-2003 Jens Rehsack wrote: > >>John Baldwin wrote: >> >>>Thanks, IRQ 16 was programmed as level, activelo, so it wasn't an >>>off by one error there. Grr. >> >>I've seen, but I didn't found a bios option to set it to edge. >>Is there anything I can do on my machine to fix the problem, or >>should Asus be notified for a bios update or ...? > > No, level is correct. The APIC code doesn't mask edge triggered > interrupts, and if it thought IRQ 16 was edge rather than level, > that could explain the high interrupt rate. Since that isn't the > case I'm not sure why it's triggering so many interrupts. Ok, but what I can do now to get my machine running with HTT again? It's out main development machine and with the single-processor config it runs mostly with a very high load. Is there any chance to get it running just before the new interrupt code. Could it be fixed? Regards, Jens