``shutdown -p now'' not working in 5.4 STABLE

[Mike Eubanks]

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
>      root at meddle.netel.rpi.edu:/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=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
>    AMD Features=0xc0480000<MP,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 
> 0xf5400000-0xf5400fff,0xf8000000-0xfbffffff 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 <mse_software at charter.net>