From owner-freebsd-current Wed Sep 20 10:11:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9BDB537B424; Wed, 20 Sep 2000 10:11:09 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8KHAvi79595; Wed, 20 Sep 2000 10:10:57 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8KH9Na15429; Wed, 20 Sep 2000 10:09:23 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 20 Sep 2000 10:09:23 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Siobhan Patricia Lynch Subject: Re: recent kernel, microuptime went backwards Cc: smp@FreeBSD.ORG, "Andrey A. Chernov" , current@FreeBSD.ORG, Bruce Evans Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Sep-00 Siobhan Patricia Lynch wrote: > John, > I get these on an SMP kernel, which locks up the box, I can't even > figure out where exactly its happening. Maybe I'm just missing something > in my kernel config file? I assumed (from UPDATING) that no real change > was > needed to the SMP options? No, it is probably a bug in the code with this scheduling mess. On the quad xeon here, very recent kernels are spinning during the acd0 probe with interrupts disabled, so there may be a few places where interrupts aren't being handled properly.  -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message