From owner-freebsd-current Sat Jan 8 13:52:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 43F1F14C01; Sat, 8 Jan 2000 13:52:47 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id IAA17395; Sun, 9 Jan 2000 08:52:36 +1100 Date: Sun, 9 Jan 2000 08:52:33 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mohit Aron Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: SMP kernel panics after calling acquire_timer0 In-Reply-To: <200001082059.OAA16137@cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Jan 2000, Mohit Aron wrote: > Hi, > I'm using FreeBSD-current (snapshot from Jan 3rd) which is configured > with both SMP and APIC_IO support. This version panics upon calling > acquire_timer0() (to modify the interrupt frequency of the 8254). On the other > hand, if the kernel is not configured as an SMP, then it works fine. The panic > reports some problem with some SMP lock - I can get more details if someone > is interested in looking at the problem. This is cause by calling disable_intr() when a lock is held. disable_intr() is a funky macro in the SMP case. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message