| View previous topic :: View next topic |
| Author |
Message |
jathey
n00b
Joined: 22 Oct 2002
Posts: 48
|
 Posted: Mon Jun 02, 2003 10:34 pm Post subject: can no longer shutdown; "sync: no job control in this s |
 |
|
This is something that has been bugging me for a while. I don't remember what I did to cause this, but when I shutdown my computer either from within KDE or from the shell using shutdown -h now I get the following-
| Code: | # shutdown -h now
Broadcast message from root (vc/1) (Mon Jun 2 19:30:18 2003):
<INIT scripts shutting down...>
* Remounting remaining filesystems readonly...
sync: no job control in this shell
sync-2.05b# |
I presume I'm now in single-user mode. I can't do much in this weird sync-shell, and I have to hold in the power button for five seconds for the machine to turn off.
Could this have anything to do with ACPI? I would love for my system to be able to shut itself off... |
|
| Back to top |
|
 |
jathey
n00b
Joined: 22 Oct 2002
Posts: 48
|
| Posted: Mon Jun 09, 2003 6:58 pm Post subject: It gets weirder |
|
|
In an attempt to solve my problem, I tried emerging the latest version of e2fsprogs. After a lot of compiling, this appeared on my console:
| Code: | gcc -o e2fsck.shared dict.o unix.o e2fsck.o super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o swapfs.o badblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o recovery.o region.o revoke.o ea_refcount.o rehash.o ../lib/libext2fs.so ../lib/libcom_err.so ../lib/libblkid.so ../lib/libuuid.so
/bin/cp e2fsck.shared e2fsck
gcc -static -o e2fsck.static dict.o unix.o e2fsck.o super.o pass1.o pass1b.o pass2.o pass3.o pass4.o pass5.o journal.o swapfs.o badblocks.o util.o dirinfo.o dx_dirinfo.o ehandler.o problem.o message.o recovery.o region.o revoke.o ea_refcount.o rehash.o \
../lib/libext2fs.a ../lib/libcom_err.a ../lib/libblkid.a ../lib/libuuid.a
../util/subst -f ../util/subst.conf ./e2fsck.8.in e2fsck.8
sync-2.05b#
|
There's that sync shell again! Here's what I tried doing from there -
| Code: | sync-2.05b# pwd
/var/tmp/portage/e2fsprogs-1.33/work/e2fsprogs-1.33/e2fsck
sync-2.05b# ps
PID TTY TIME CMD
2670 pts/0 00:00:00 su
2673 pts/0 00:00:00 bash
25284 pts/0 00:00:00 python2.2
25405 pts/0 00:00:00 sandbox
25406 pts/0 00:00:00 ebuild.sh
27732 pts/0 00:00:00 emake
27733 pts/0 00:00:00 make
28642 pts/0 00:00:00 make
28653 pts/0 00:00:00 sh
28657 pts/0 00:00:00 sh
28658 pts/0 00:00:00 make
28740 pts/0 00:00:00 sync
28747 pts/0 00:00:00 ps
sync-2.05b# exit
exit
make[2]: Leaving directory `/var/tmp/portage/e2fsprogs-1.33/work/e2fsprogs-1.33/e2fsck'
making all in debugfs
|
And the emerge keeps going!
What on earth is going on? And why am I the only person on the planet with this problem? |
|
| Back to top |
|
|
jathey
n00b
Joined: 22 Oct 2002
Posts: 48
|
| Posted: Fri Jun 13, 2003 7:27 pm Post subject: Another update |
|
|
I discovered that if I type "exit" at the sync shell prompt that appears when I try to turn off or restart my computer, I end up in another sync-shell prompt. Like, a monkey, I keep trying, and after the third exit, my computer finally responds as it's supposed to - by either restarting or powering down. This is consistent, repeatable behavior.
Anybody have a clue what's causing sync to freak out? Should I just file a bug against this? I still feel like I'm the only person in the world with this issue. |
|
| Back to top |
|
|
|
Kernel & Hardware
