Huh... do you really think, that the change not to show the message did
solve that bug?
There is some process not reacting on int/term signals which prevents
clean unmount of file system and thus forcing fsck to be run on the next
system start.
--
init rc main process stopped and continued in
I've just realised that these messages appear at all because the log
priority is low enough that they appear, booting with --quiet on the
kernel command-line is enough to hide them. But we use quiet not --
quiet, Upstart should respect that
** Changed in: upstart (Ubuntu)
Status: Won't
** Branch linked: lp:~ubuntu-core-dev/upstart/ubuntu
--
init rc main process stopped and continued in loop on system reboot/shutdown
https://bugs.launchpad.net/bugs/401333
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug was fixed in the package upstart - 0.6.3-4
---
upstart (0.6.3-4) karmic; urgency=low
[ Scott James Remnant ]
* Reduce the priority of the stopped by/continued by messages so that
they are only shown when --verbose on the kernel command-line.
LP: #401333.
* Add
I have similar problem with filesystems recovering at every booting up,
and have a filed a bug 434224
That issue isn't resolved with last upstart and Ko updates which, as
supposed, fix this one.
--
init rc main process stopped and continued in loop on system reboot/shutdown
I have this problem since two days (Linux 2.6.31-10, upstart 0.6.3-3).
After ca. 10 of these STOP/CONT cycles the system finally reboots/shuts
down. Two times, I was even dropped to an emergency shell after starting
the system later and had to fsck my filesystem. One is karmic amd64, the
other
same here
i always get this after reboot instead of the nice screen and this looks
somehow ill
also i had to fsck my partitions just as martin emrich wrote
--
init rc main process stopped and continued in loop on system reboot/shutdown
https://bugs.launchpad.net/bugs/401333
You received this
On Thu, 2009-09-17 at 07:23 +, Martin Emrich wrote:
** Changed in: upstart (Ubuntu)
Status: Won't Fix = New
Please don't revert this status.
Scott
--
Scott James Remnant
sc...@canonical.com
** Changed in: upstart (Ubuntu)
Status: New = Won't Fix
--
init rc main process
I'm getting the same bug... is it normal that Karmic is taking a long
time to shut down? It feels like it takes three times as long as Jaunty
shutting down. Without the splash screen I see these two lines:
init: rc main process stopped by STOP signal
init: rc main process continued by CONT signal
On Thu, 2009-09-17 at 19:02 +, Kaaahn! wrote:
I'm getting the same bug... is it normal that Karmic is taking a long
time to shut down? It feels like it takes three times as long as Jaunty
shutting down.
No, but these messages are not relevant to that.
Scott
--
Scott James Remnant
This is perfectly normal. init is simply reporting that something is
stopping and continuing its rc process; the thing that's doing that is
killall5 being run from rc as part of the process of killing all system
processes.
** Changed in: upstart (Ubuntu)
Status: Confirmed = Won't Fix
--
I still have this problem.. and the after shutdown it asks me to run
'fsck'. Really strange.
** Changed in: ubuntu
Status: Invalid = Fix Released
** Package changed: ubuntu = upstart (Ubuntu)
** Changed in: upstart (Ubuntu)
Status: Fix Released = Confirmed
--
init rc main
Maybe it could be a kernel problem. Bug 418560
--
init rc main process stopped and continued in loop on system reboot/shutdown
https://bugs.launchpad.net/bugs/401333
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I moved this bug to Invalid because it has been resolved with some
update before even confirmed and I was too lazy to find which update was
it.
You can easilly distinguish between these two bugs... if you wait long
enough (30 seconds) and your computer does not restart/shutdown then you
are
Not reproducible any more.
** Changed in: ubuntu
Status: New = Invalid
--
init rc main process stopped and continued in loop on system reboot/shutdown
https://bugs.launchpad.net/bugs/401333
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Today I did another reboot and noticed that the issue has disappeared.
Might be fixed by upstart: 0.6.2-1
--
init rc main process stopped and continued in loop on system reboot/shutdown
https://bugs.launchpad.net/bugs/401333
You received this bug notification because you are a member of Ubuntu
16 matches
Mail list logo
