Cannot reboot Debian Etch - 1 Core at 100% Post: 302360135

Sponsored Content

Operating Systems Linux Debian Cannot reboot Debian Etch - 1 Core at 100% Post 302360135 by jelloir on Thursday 8th of October 2009 07:31:45 AM

10-08-2009

Registered User

the non-tree view looked identical but rearranged the list.

Here is ps aux instead

Code:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   6124   680 ?        Ss   Oct07   0:00 init [2]
root         2  0.0  0.0      0     0 ?        S    Oct07   0:00 [migration/0]
root         3  0.0  0.0      0     0 ?        SN   Oct07   0:00 [ksoftirqd/0]
root         4  0.0  0.0      0     0 ?        S    Oct07   0:00 [watchdog/0]
root         5  0.0  0.0      0     0 ?        S    Oct07   0:00 [migration/1]
root         6  0.0  0.0      0     0 ?        SN   Oct07   0:00 [ksoftirqd/1]
root         7  0.0  0.0      0     0 ?        S    Oct07   0:00 [watchdog/1]
root         8  0.0  0.0      0     0 ?        S<   Oct07   0:00 [events/0]
root         9  0.0  0.0      0     0 ?        S<   Oct07   0:00 [events/1]
root        10  0.0  0.0      0     0 ?        S<   Oct07   0:00 [khelper]
root        11  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kthread]
root        16  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kblockd/0]
root        17  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kblockd/1]
root        18  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kacpid]
root       116  0.0  0.0      0     0 ?        S<   Oct07   0:00 [khubd]
root       118  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kseriod]
root       169  0.0  0.0      0     0 ?        S<   Oct07   0:17 [kswapd0]
root       170  0.0  0.0      0     0 ?        S<   Oct07   0:00 [aio/0]
root       171  0.0  0.0      0     0 ?        S<   Oct07   0:00 [aio/1]
root       689  0.0  0.0      0     0 ?        S<   Oct07   0:00 [ata/0]
root       690  0.0  0.0      0     0 ?        S<   Oct07   0:00 [ata/1]
root       691  0.0  0.0      0     0 ?        S<   Oct07   0:00 [ata_aux]
root       744  0.0  0.0      0     0 ?        S<   Oct07   0:00 [scsi_eh_0]
root       745  0.0  0.0      0     0 ?        S<   Oct07   0:00 [scsi_eh_1]
root       970  0.0  0.0      0     0 ?        D<   Oct07   0:21 [kjournald]
root      1491  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kedac]
root      1735  0.0  0.0      0     0 ?        S<   Oct07   0:00 [kmirrord]
root      2025  0.0  0.0   3728   592 ?        Ss   Oct07   0:00 /sbin/syslogd
root      2031  0.0  0.0   2656   412 ?        Ss   Oct07   0:00 /sbin/klogd -x
root      2127  0.0  0.0  25840  1236 ?        Ss   Oct07   0:00 /usr/sbin/sshd
ntp       2154  0.0  0.0  14080  1472 ?        Ss   Oct07   0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -u 101:103 -g
root      2164  0.0  0.0  11496   804 ?        Ss   Oct07   0:00 /usr/sbin/cron
root      2239  0.0  0.0   2652   536 tty1     Ss+  Oct07   0:00 /sbin/getty 38400 tty1
root      2240  0.0  0.0   2656   540 tty2     Ss+  Oct07   0:00 /sbin/getty 38400 tty2
root      2241  0.0  0.0   2656   540 tty3     Ss+  Oct07   0:00 /sbin/getty 38400 tty3
root      2242  0.0  0.0   2656   540 tty4     Ss+  Oct07   0:00 /sbin/getty 38400 tty4
root      2243  0.0  0.0   2656   540 tty5     Ss+  Oct07   0:00 /sbin/getty 38400 tty5
root      2244  0.0  0.0   2656   540 tty6     Ss+  Oct07   0:00 /sbin/getty 38400 tty6
root      3104  0.0  0.0      0     0 ?        S    11:54   0:01 [pdflush]
root      3202  0.0  0.0      0     0 ?        S    13:56   0:00 [pdflush]
root      3549  0.0  0.0  11664   908 ?        DN   21:20   0:00 mount /dev/nb0 /mnt/
root      3580  0.0  0.0  11664   908 ?        D    21:25   0:00 mount /dev/nb0 /mnt/
root      3591  0.0  0.0   6960   724 ?        D    21:28   0:00 shutdown -r 0 w
root      3700  0.0  0.0   2508   356 ?        D    21:48   0:00 reboot -f
root      3722  0.0  0.0   2508   320 ?        D    21:54   0:00 rmmod -f nbd
root      3737  0.0  0.0   6956   716 ?        D    22:02   0:00 shutdown -r 0 w
root      3739  0.0  0.0  36792  2724 ?        Ss   22:03   0:00 sshd: root@pts/5
root      3741  0.0  0.0  11548  1992 pts/5    Ss   22:03   0:00 -bash
root      3750  0.0  0.0   9656  1056 pts/5    R+   22:30   0:00 ps aux

jelloir

View Public Profile for jelloir

Find all posts by jelloir

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Install App in Debian Etch 4.0

I am trying to install a couple applications that I downloaded on my Debian Etch 4.0 OS but I don't know how. 1) I tried using sudo apt-get install...but it always tells me I'm not in the sudoers file 2) I tried using root terminal, but I cant seem to navigate anywhere and I don't know where...

2. Solaris

server reboot itself but no core dump

I wonder if anyone here came accross the same situation like me. One of server in my company reboot itself serveral days ago. I have checked /var/adm/messages... there is nothing there but a few messages mention explorer file has been generated by sysadmin. There is no core dump file either....

3. Debian

Debian Etch - install us-keyboard driver

Hi, i'm using a debian-4.0r1 on an old subnet machine. I have to extend it with an other keyboard . What i have is a DVD of etch 4.0r7. How can i install and load the keyboard-driver for the us-keyboard? Can anybody please give me a hint how to do that? Thanks in advance

LEARN ABOUT MINIX

reboot

REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME

       reboot - reboot the system immediately

SYNOPSIS

       reboot [-f]

DESCRIPTION

       Reboot  can  be	used  to  reboot  the  system  after  installing a new kernel.	It does not inform the users, but does log it's actions in
       /usr/adm/wtmp and /usr/adm/authlog.  The system is then rebooted with the reboot(2) systemcall.

       If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call.

       If the wtmp file exists, reboot logs itself as if it were a shutdown.  This is done to prevent last(1) from talking  about  system-crashes.
       Reboot is registered as is in the authlog file.

       Reboot can only be executed by the super-user.  Any other caller will be refused, either by reboot(8) or by reboot(2).

SEE ALSO

       reboot(2), shutdown(8), halt(8), boot(8).

BUGS

       The  error message's given by reboot are not always useful.  There are several routines that can fail, but which are not fatal for the pro-
       gram.

AUTHOR

       Edvard Tuinder (v892231@si.hhs.NL)

																	 REBOOT(8)