From owner-freebsd-current@FreeBSD.ORG  Tue Nov  4 07:50:36 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 BD7D816A4DF; Tue,  4 Nov 2003 07:50:36 -0800 (PST)
Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de
	[193.174.154.14])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 187A643FB1; Tue,  4 Nov 2003 07:50:35 -0800 (PST)
	(envelope-from brandt@fokus.fraunhofer.de)
Received: from beagle (beagle [193.175.132.100])hA4FoX003888;
	Tue, 4 Nov 2003 16:50:33 +0100 (MET)
Date: Tue, 4 Nov 2003 16:50:33 +0100 (CET)
From: Harti Brandt <brandt@fokus.fraunhofer.de>
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: <XFMail.20031104103812.jhb@FreeBSD.org>
Message-ID: <20031104164938.D72398@beagle.fokus.fraunhofer.de>
References: <XFMail.20031104103812.jhb@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Reply-To: harti@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2003 15:50:36 -0000

On Tue, 4 Nov 2003, John Baldwin wrote:

JB>
JB>On 04-Nov-2003 Harti Brandt wrote:
JB>>
JB>> Hi,
JB>>
JB>> I have an ASUS system with 2 CPUs that I need to run at HZ=10000. This
JB>> worked until yesterday, but with the new interrupt code it doesn't boot
JB>> anymore. It works for the standard HZ, but if I set HZ=1000 I get a double
JB>> fault. I suspect a race condition in the interrupt handling. My config
JB>> file has
JB>>
JB>> options SMP
JB>> device apic
JB>> options HZ=1000
JB>
JB>Ok, I can try to reproduce.
JB>
JB>> Device configuration finished.
JB>> Timecounter "TSC" frequency 1380009492 Hz quality -100
JB>> Timecounters cpuid = 0; apic id = 00
JB>> instruction pointer   = 0x8:0xc048995d
JB>> stack pointer         = 0x10:0xc0821bf4
JB>> frame pointer        cpuid = 0; apic id = 00
JB>>
JB>> 0xc048995d is in critical_exit. It is the jmp after the popf from
JB>> cpu_critical_exit.
JB>
JB>This is where interrupts are re-enabled, so you are getting an interrupt.
JB>It might be helpful to figure what type of fault you are actually getting.

tf_err is 0, tf_trapno is 30 (decimal).

harti
-- 
harti brandt,
http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private
brandt@fokus.fraunhofer.de, harti@freebsd.org