From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 07:38:38 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 6129916A4CE for ; Tue, 4 Nov 2003 07:38:38 -0800 (PST) Received: from mail.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED09743FDD for ; Tue, 4 Nov 2003 07:38:36 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 5205 invoked from network); 4 Nov 2003 15:38:36 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 4 Nov 2003 15:38:36 -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 hA4FcCce069382; Tue, 4 Nov 2003 10:38:12 -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: <20031104122624.J72398@beagle.fokus.fraunhofer.de> Date: Tue, 04 Nov 2003 10:38:12 -0500 (EST) From: John Baldwin To: harti@freebsd.org X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: current@freebsd.org Subject: RE: New interrupt stuff breaks ASUS 2 CPU system 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, 04 Nov 2003 15:38:38 -0000 On 04-Nov-2003 Harti Brandt wrote: > > Hi, > > I have an ASUS system with 2 CPUs that I need to run at HZ=10000. This > worked until yesterday, but with the new interrupt code it doesn't boot > anymore. It works for the standard HZ, but if I set HZ=1000 I get a double > fault. I suspect a race condition in the interrupt handling. My config > file has > > options SMP > device apic > options HZ=1000 Ok, I can try to reproduce. > Device configuration finished. > Timecounter "TSC" frequency 1380009492 Hz quality -100 > Timecounters cpuid = 0; apic id = 00 > instruction pointer = 0x8:0xc048995d > stack pointer = 0x10:0xc0821bf4 > frame pointer cpuid = 0; apic id = 00 > > 0xc048995d is in critical_exit. It is the jmp after the popf from > cpu_critical_exit. This is where interrupts are re-enabled, so you are getting an interrupt. It might be helpful to figure what type of fault you are actually getting. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/