Re: Shutdown -p now not working in 5.4 STABLE
From: Zoran Kolic [EMAIL PROTECTED] Date: 2005/08/06 Sat AM 12:39:31 EDT To: [EMAIL PROTECTED] CC: freebsd-stable@freebsd.org Subject: Re: Shutdown -p now not working in 5.4 STABLE Hi Mike! If you still manage this puzzle, is there something in your bios that affects 5.4 and not 5.1? Must be power menue with apm and other stuff. Acpi is on and should take the whole process for you. Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] You were right! I was using a auto-power up feature to power the machine on automatically at a certain time every day. Everyting works after disabling it in the CMOS setup. I was planning to use the `shutdown -p now' command to compliment the auto power on feature in the BIOS to alleviate the need for the client to turn it off and on. This is not only because there isn't much computer literacy, but also because I didn't want the disks spinning during the time no one is in the office. I'm curious, between 5.1 and 5.4, was the change made to more accurately represent the hardware the system was running on (fixing a problem), or was it simply due to other circumstances that resulted in the functionality being broken? I would definitely be interested in creating a patch to regain the functionality if the development team didn't do it for a reason. I don't want to break what someone else has taken the time to fix. Thanks, Mike Eubanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
At 8:43 PM -0700 8/4/05, Mike Eubanks wrote: On Thu, 2005-08-04 at 19:14 -0400, Garance A Drosihn wrote: Hmm. The more I think about this, the more I think I tripped across something similar once. I think it was something like I turned on 'APM' somewhere, or I added it to my kernel, or something. For power-down, you need to be using ACPI, not APM. But from your dmesg output, it looks like you are using ACPI, so I am probably not helping much with that guess either. Ok, I built APM into the kernel and gave it a few tries, fiddling with different things. Sorry, my comments were not as clear as they should have been. What I meant is that my problem was *caused* by adding APM into the mix, when it should not have been there. That's what I meant by: For power-down, you need to be using ACPI, not APM. But all of this is just vague memory anyway. I haven't had any problems with my machines powering down for quite awhile now. (through many different system builds...) -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
On Fri, 2005-08-05 at 12:29 +0200, Owe Jørgensen wrote: Mike Eubanks wrote: On Thu, 2005-08-04 at 14:21 -0700, J. Nyhuis wrote: Wouldn't you want a -h for halt to prevent it from powering back up? Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 [EMAIL PROTECTED] On Thu, 4 Aug 2005, 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. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] Yeah, the `-h' option does halt the system. The system does not power down though as it should with `-p' (halt and power down). I guess it would be more healthy for the system and your fitness if you reached down and turned it off manually after a shutdown -h :-) Right you are. Once the machine is being used, though, I will need one arm that is at least 240 miles in length and rippling back muscles to carry the weight of my arm. :-) -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
On Fri, 2005-08-05 at 16:03 -0400, Garance A Drosihn wrote: At 8:43 PM -0700 8/4/05, Mike Eubanks wrote: On Thu, 2005-08-04 at 19:14 -0400, Garance A Drosihn wrote: Hmm. The more I think about this, the more I think I tripped across something similar once. I think it was something like I turned on 'APM' somewhere, or I added it to my kernel, or something. For power-down, you need to be using ACPI, not APM. But from your dmesg output, it looks like you are using ACPI, so I am probably not helping much with that guess either. Ok, I built APM into the kernel and gave it a few tries, fiddling with different things. Sorry, my comments were not as clear as they should have been. What I meant is that my problem was *caused* by adding APM into the mix, when it should not have been there. That's what I meant by: For power-down, you need to be using ACPI, not APM. But all of this is just vague memory anyway. I haven't had any problems with my machines powering down for quite awhile now. (through many different system builds...) Garance, That's ok. I figured it wouldn't hurt to give it a try anyway. I am currently rebuilding it. I've never had a problem quite like this one. Evidence for problem seems to be inconsistent in the fact that it works fully on one version, and sometimes on the other. In the end, I fear my install is the only thing questionable at this point when considering the other dual-Athlon 5.4 system operates without a problem. Thanks again -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shutdown -p now not working in 5.4 STABLE
Hi Mike! If you still manage this puzzle, is there something in your bios that affects 5.4 and not 5.1? Must be power menue with apm and other stuff. Acpi is on and should take the whole process for you. Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
``shutdown -p now'' not working in 5.4 STABLE
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. I have tried the GENERIC kernel as well as several custom kernels. I'm stuck at this point. Are there any sysctl flags that may be of importance or something else I may be missing. I haven't changed anything with respect loader.conf or device hints yet. The hardware is roughly two years old - 09/2003 Motherboard: GA-7N400-L BIOS: Award Modular BIOS -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
``shutdown -p now'' not working in 5.4 STABLE
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. I have tried the GENERIC kernel as well as several custom kernels. I'm stuck at this point. Are there any sysctl flags that may be of importance or something else I may be missing. I haven't changed anything with respect loader.conf or device hints yet. The hardware is roughly two years old - 09/2003 Motherboard: GA-7N400-L BIOS: Award Modular BIOS -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
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. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
Wouldn't you want a -h for halt to prevent it from powering back up? Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 [EMAIL PROTECTED] On Thu, 4 Aug 2005, 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. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
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 memory, RAM 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 [EMAIL PROTECTED]:/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=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc040AMIE,DSP,3DNow! real memory = 1073676288 (1023 MB) avail memory = 1045323776 (996 MB) acpi0: Nvidia AWRDACPI 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: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf0-0xcf3,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: NVIDIA nForce2 AGP Controller mem 0xd800-0xdbff at device 0.0 on pci0 pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) - Any ideas are welcome. -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
On Thu, 2005-08-04 at 14:21 -0700, J. Nyhuis wrote: Wouldn't you want a -h for halt to prevent it from powering back up? Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 [EMAIL PROTECTED] On Thu, 4 Aug 2005, 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. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] Yeah, the `-h' option does halt the system. The system does not power down though as it should with `-p' (halt and power down). -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
On Thu, Aug 04, 2005 at 02:25:17PM -0700, Mike Eubanks wrote: 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 memory, RAM 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 [EMAIL PROTECTED]:/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=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc040AMIE,DSP,3DNow! real memory = 1073676288 (1023 MB) avail memory = 1045323776 (996 MB) acpi0: Nvidia AWRDACPI 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: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf0-0xcf3,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: NVIDIA nForce2 AGP Controller mem 0xd800-0xdbff at device 0.0 on pci0 pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) - Any ideas are welcome. -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] This works for me...as root place apm_enable=YES in the /etc/rc.conf file -- FreeBSD 5.4-RELEASE i386 GENERIC-NEW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ``shutdown -p now'' not working in 5.4 STABLE
On Thu, 2005-08-04 at 19:14 -0400, Garance A Drosihn wrote: At 2:25 PM -0700 8/4/05, Mike Eubanks wrote: 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. Hmm. The more I think about this, the more I think I tripped across something similar once. I think it was something like I turned on 'APM' somewhere, or I added it to my kernel, or something. For power-down, you need to be using ACPI, not APM. But from your dmesg output, it looks like you are using ACPI, so I am probably not helping much with that guess either. Here's the start of my dmesg output. Seems like our machines are fairly similar: # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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 Jul 28 19:58:50 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/Dual-Athlon2k-5x ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) MP 2000+ (1666.74-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 1073217536 (1023 MB) avail memory = 1040592896 (992 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: AMD 762 host to AGP bridge port 0x1010-0x1013 mem 0xf540-0xf5400fff,0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 5.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD 768 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 Ok, I built APM into the kernel and gave it a few tries, fiddling with different things. Unfortunately no luck. The dmesg snip above looks identical to my dual processor system. The main difference between them and the machine that is acting up is the line right after npx0: dual-processor Athlon MP (Tyan board) + acpi0: PTLTD RSDT on motherboard single processor Athlon XP (Gigabyte board - problem child) + acpi0: Nvidia AWRDACPI on motherboard I imagine this is due to the different motherboards and their BIOS. After digging around through the kernel and acpi source for awhile, I decided to power the system down completely and unplug it. The `shutdown -p now' command worked one time. I repeated this process several more times, each with a single `shutdown -p now' command working. After that, I put my 5.1-RELEASE HDD back in (pulling the 5.4-STABLE disk out). The 5.1 system still works perfect with power down working every time. If all else fails, I will simply stay with the older system. I am going to try a clean 5.4 install again, though, just to make sure things didn't go haywire when I was building the system last time. Once I have the base 5.4-STABLE system installed again, I should be able to verify whether there is a hardware compatibility issue stemming from a code difference between the two branches (5.1 and 5.4), or if my work was simply sleep deprived. If it happens to be a hardware issue, I'll send a follow up. Cheers, -- Mike Eubanks [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
