From owner-freebsd-stable@FreeBSD.ORG Wed Oct 1 11:04:22 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C20E816A4B3 for ; Wed, 1 Oct 2003 11:04:22 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0775D43FE1 for ; Wed, 1 Oct 2003 11:04:22 -0700 (PDT) (envelope-from mmarchetti@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Wed, 1 Oct 2003 14:04:21 -0400 Message-ID: From: Michael Marchetti To: "'freebsd-stable@freebsd.org'" Date: Wed, 1 Oct 2003 14:04:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: 4.7 SMP lockup X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2003 18:04:22 -0000 Hi, I'm seeing a problem with 4.7 where, very rarely, the system seems to "lockup". No panic is given. I was able to track it down to all processors were halted (in the idle loop) since machdep.cpu_idle_hlt=1. The system is a 2 physical XEON procs with hyperthreading enabled. The system was behaving as though the 8254 system clock was not going off. The only thing I can think of is some kind of lapic problem where the interrupt is not being delivered to the CPU. Any others encounter such a problem? thanks, mike.