l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
August 5: Social gathering
Next Installfest:
TBD
Latest News:
Jul. 4: July, August and September: Security, Photography and Programming for Kids
Page last updated:
2003 Jun 09 11:02

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Redhat 8.0 shutdown does not power off.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Redhat 8.0 shutdown does not power off.



--- Mike Simons <msimons@moria.simons-clan.com>
> Jim Angstadt wrote:
> > --- Mike Simons
<many snips>

> > Did s-u-o to get a know starting point, then:
> > 1. hung after ...TERM..., phy pwr off, phy
> pwr on
> > 2. clean to "power down", reboot
> > 3. clean to "power down", off
> > 4. clean to "power down", off
> > 5. hung after ...TERM..., phy pwr off, phy
> pwr on
> 
>   woah.  I don't remember you say the machine
> has powered off once since 
> this thread started... I just skimmed over your
> messages again and
> I see one other case that it seems that it
> powered off without you 
> touching the power button.
> 
> Jim,
> 
>   Okay, I need to verify my understanding...
> 
> - are you saying?  (yes or no)
> 
>     of the five times you tried, 
>       twice it actually turned off power,
>       twice it got stuck before killing two of
> the processes, and
>       once it rebooted instead of powering off

Yes.

> 
> - the most recent tests have all be done
> without X starting up?  (yes or no)

Yes.

> 
>   You have been shutting the machine down
> dozens of times since this
> thread started... 
> 
> - the machine never powered itself off (beside
> the two times above
>   and the one time I mentioned) since you
> started this thread?
>   (yes or no)

Yes.

> 
> - the machine *did* power itself off the three
> times mentioned above?
>   (yes or no)

Yes.

> Jim Angstadt wrote:
> > --- Mike Simons

> > > - Paste the output from:  cat /proc/cmdline
> > > - Paste the output from:  cat /proc/apm
> > 
> > AFTER
> > ro apm=realmode_power_off root=LABEL=/
> > hdc=ide-scsi
> > 1.16 1.2 0x07 0x01 0xff 0x80 -1% -1 ?
>            ^^^^
> 	   this says that APM is enabled on your
> machine... 
> 
> it says your APM supports 16 bit, 32 bit, and
> APM_IDLE calls slow the 
> CPU clock.
> 
> linux/include/linux/apm_bios.h
> ===
> /* Results of APM Installation Check */
> #define APM_16_BIT_SUPPORT      0x0001
> #define APM_32_BIT_SUPPORT      0x0002
> #define APM_IDLE_SLOWS_CLOCK    0x0004
> #define APM_BIOS_DISABLED       0x0008
> #define APM_BIOS_DISENGAGED     0x0010
> ===
> 

> Mike Simons wrote:
> > Jim Angstadt wrote:

> > - Were any settings in the BIOS changed in
> the last few months?

No.

> > 
> >   It is possible that if APM is disabled in
> the BIOS that the power off
> > feature would stop working.
> 
>   I didn't see your reply... any changes to
> BIOS settings in a long time?

My only changes -ever- to the bios were initial
date, time, and maybe boot sequence (cannot
recall).

>   I have *one* more set of things to try, using
> grub add the boot
> option "single", and try the "s-u-o" thing a
> few times, your can
> try "single apm=realmode_power_off", a few
> times too.  Let me know
> if the power goes off any of those ways.
> 
>   The "single" option should prevent the
> machine from starting most
> every service that would normally start up...
> this should prevent
> most every kernel module from being loaded
> (check "lsmod") and
> should prevent practically any services from
> starting up 
> (check "ps aux")...
> 
>   Report back if any of those two settings
> result in reliable poweroff.

The results are mixed:

With just 'single' added to boot parms:

1. s-u-o led to off
2. s-u-o led to reboot
3. s-u-o led to off
4. s-u-o led to off
5. s-u-o led to off
6. s-u-o led to off

With 'single apm=realmode_power_off' added:

1. s-u-o led to off
2. s-u-o led to off
3. s-u-o led to reboot
4. s-u-o led to off
5. s-u-o led to off
6. s-u-o led to off

On single 1, I ran lsmod and saved it, see below.

Every other single and single+apm lsmod had an
identical putput.

I also ran ps aux on single 1.  see below.  I did
a visual scan of ps aux for each subsequent run
and they all looked the same.  But, it was not an
item-by-item, like I did for lsmod.

To satisfy my own curosity, I ran 
   grub> halt 
six times in a row.  All resulted in a power off.


lsmod output:
Module                  Size  Used by    Not
tainted
ide-scsi               10512   0 
scsi_mod              107176   1  [ide-scsi]
ide-cd                 33608   0 
cdrom                  33696   0  [ide-cd]
printer                 8992   0  (unused)
mousedev                5524   0  (unused)
keybdev                 2976   0  (unused)
hid                    22244   0  (unused)
input                   5888   0  [mousedev
keybdev hid]
usb-uhci               26188   0  (unused)
ehci-hcd               17480   0  (unused)
usbcore                77024   1  [printer hid
usb-uhci ehci-hcd]
ext3                   70368   6 
jbd                    52212   6  [ext3]

ps aux output:
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT
START   TIME COMMAND
root         1  0.7  0.1  1328  416 ?        S   
09:29   0:04 init [S]   
root         2  0.0  0.0     0    0 ?        SW  
09:29   0:00 [keventd]
root         3  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kapmd]
root         4  0.0  0.0     0    0 ?        SWN 
09:29   0:00 [ksoftirqd_CPU0]
root         5  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kswapd]
root         6  0.0  0.0     0    0 ?        SW  
09:29   0:00 [bdflush]
root         7  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kupdated]
root         8  0.0  0.0     0    0 ?        SW  
09:29   0:00 [mdrecoveryd]
root        12  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kjournald]
root        68  0.0  0.0     0    0 ?        SW  
09:29   0:00 [khubd]
root       263  0.0  0.2  1656  632 ?        S   
09:29   0:00 minilogd
root       289  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kjournald]
root       290  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kjournald]
root       291  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kjournald]
root       292  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kjournald]
root       293  0.0  0.0     0    0 ?        SW  
09:29   0:00 [kjournald]
root       383  0.0  0.1  1328  416 tty1     S   
09:29   0:00 init [S]   
root       384  0.0  0.4  2268 1200 tty1     S   
09:29   0:00 /bin/sh
root       392  0.0  0.2  2540  624 tty1     R   
09:38   0:00 ps aux



__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.