From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 04:39:12 2005 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 4279916A4CE for ; Mon, 17 Jan 2005 04:39:12 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF0B143D3F for ; Mon, 17 Jan 2005 04:39:11 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so188191rna for ; Sun, 16 Jan 2005 20:39:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Do3KLxMTu08KdwEBI6TKJY6G3Cvyz0r0+Aq7lweGrymctqoVcT+dgLVvjbMLmzxKiqq6dU5VX3vyNalZs3fHjCQEPL2uL7aokNaBSdcfm3yRNMJWOH+wWtiZdYHQ44+0pg7cpJ+PcV2pKsC+vSssZsBdSaWUYsZVDN3Fi042d4Y= Received: by 10.38.13.52 with SMTP id 52mr32959rnm; Sun, 16 Jan 2005 20:39:10 -0800 (PST) Received: by 10.38.90.77 with HTTP; Sun, 16 Jan 2005 20:39:06 -0800 (PST) Message-ID: <6863f0c9050116203956de93dd@mail.gmail.com> Date: Sun, 16 Jan 2005 22:39:06 -0600 From: jmc To: Will Saxon In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED80504A3E1@bragi.housing.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <0E972CEE334BFE4291CD07E056C76ED80504A3E1@bragi.housing.ufl.edu> cc: stable@freebsd.org Subject: Re: Machine(s) not able to reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jmc List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 04:39:12 -0000 On Sun, 16 Jan 2005 18:39:41 -0500, Will Saxon wrote: > Hello, > > I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R > to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down > or reboot on their own. I always have to physically power them off and then back > on. They are SMP machines and I am using ACPI. There are no other apparent > problems although one machine did panic today and as a result I had to drive in > and power cycle it. I haven't heard of this problem before, and I was wondering if today's 5.3-R errata notice (more than one IPI per APIC causes deadlock) might have something to do with it. Are these machines running SMP? - John