From owner-freebsd-stable@FreeBSD.ORG Thu Aug 4 21:25:25 2005 Return-Path: X-Original-To: stable@freebsd.org 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 254F916A41F for ; Thu, 4 Aug 2005 21:25:25 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxsf39.cluster1.charter.net (mxsf39.cluster1.charter.net [209.225.28.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB75743D45 for ; Thu, 4 Aug 2005 21:25:24 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxip29a.cluster1.charter.net (mxip29a.cluster1.charter.net [209.225.28.188]) by mxsf39.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j74LPNIV027282 for ; Thu, 4 Aug 2005 17:25:23 -0400 Received: from 68-186-85-19.dhcp.knwk.wa.charter.com (HELO yak.mseubanks.net) ([68.186.85.19]) by mxip29a.cluster1.charter.net with ESMTP; 04 Aug 2005 17:25:23 -0400 X-IronPort-AV: i="3.95,168,1120449600"; d="scan'208"; a="21298659:sNHT16789546" From: Mike Eubanks To: stable@freebsd.org In-Reply-To: References: <1123187556.786.25.camel@yak.mseubanks.net> Content-Type: text/plain Date: Thu, 04 Aug 2005 14:25:17 -0700 Message-Id: <1123190717.786.49.camel@yak.mseubanks.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: ``shutdown -p now'' not working in 5.4 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mse_software@charter.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2005 21:25:25 -0000 On Thu, 2005-08-04 at 17:09 -0400, Garance A Drosihn wrote: > At 1:32 PM -0700 8/4/05, Mike Eubanks wrote: > >I have finished migrating my system from 5.1-RELEASE to 5.4-STABLE. > >The system no longer powers down using either the `shutdown -p now' > >or `acpiconf -s 5' commands. Instead it always restarts. > > This won't help much, but I have a system running 5.4-STABLE as of > Thu Jul 28, and `shutdown -p now' works on that. Dual-athlon. > Ok. I'm also running a dual-athlon with 5.4-STABLE...no problems. I really don't know why this machine is behaving the way it is, it has always worked fine under 5.1-RELEASE. I'm hoping it is something fairly simple though. Other than the lack of a NVIDIA memory controller (pci0 at device 0.x), I'd say everything looks fine. Below is a snip of the dmesg output for the current custom kernel compiled with updated source: ----------------- Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #0: Thu Aug 4 18:54:47 PDT 2005 root@kadavu.mseubanks.net:/usr/obj/usr/src/sys/kadavu Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 2700+ (2162.74-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 Features=0x383fbff AMD Features=0xc0400000 real memory = 1073676288 (1023 MB) avail memory = 1045323776 (996 MB) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf0-0xcf3,0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xd8000000-0xdbffffff at device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) ----------------- Any ideas are welcome. -- Mike Eubanks