The lines "Kernel logging re-started after SIGSTOP" are strange.
I have the same messages (with / on ext3), also seeing / is busy when I
shutdown or reboot. It seems klogd and syslogd are not terminated anymore, and
keep the file system busy.
As a work-around, I have created symlinks in /etc/rc{0,6}.d to terminate klogd
and syslogd, and now I can shutdown and reboot without problems. Also, the log
lines "Kernel logging re-started after SIGSTOP" have stopped.
Can you please create those symlinks and verify if that solves the issue for
you as well?
You can do this with the commands:
$ cd /etc/rc0.d
$ sudo ln -s ../init.d/klogd K89klogd
$ sudo ln -s ../init.d/sysklogd K90sysklogd
$ cd /etc/rc6.d
$ sudo ln -s ../init.d/klogd K89klogd
$ sudo ln -s ../init.d/sysklogd K90sysklogd
Then try a few shutdowns and reboots and see if it helps. Please report
back your results.
--
initscripts in jaunty does not umount root filesystem jfs
https://bugs.launchpad.net/bugs/302871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
