[Bug 554172] Re: comment #181

[Mike Bianchi]

On Tue, Jul 20, 2010 at 09:49:13AM -0000, Kai Krakow wrote:
> I don't think that any workarounds could really fix this - the
> workarounds just modify timing or reduce impact.

You are absolutely right.
These are workarounds.

But they are the best we can do because I, for one, do not have the time
to chase this problem as a bug in /bin/init
nor the knowledge to chase it as a bug in the kernel.

The workarounds that work for me (follow the links in comment 180) allowed
me to deliver a working machine to a customer.  But I have given up on 10.4
until this bug is properly addressed.

>I think the problem is really much more lowlevel - device nodes that are not ready, or
> events emitted by upstart in wrong order or wrong timing.

I think that point has already been made and has been apparent for months.
See 
  https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/54
and
  https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/58
and
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/comments/136

> I don't want to be mean, but I'd suggest to move such repeating
> discussions to the support forum (or stay there), this is a bug
> tracker. Add yourself to CC to express your urge for a fix but move
> "did you try this and that" to a forum and report back if a
> work-around really fixes a problem reproducibly for multiple people.
> Especially since the backref is actually a forum link!

This bug is labeled Confirmed, of High Importance, and _Unassigned_ !

We are trying, desperately to get someone actively working on the problem.
I've been told by Canonical Support that they are not working on it because
they have not been able to reproduce it!

The activity here is an attempt to get their attention,
demonstrating that it is a real bug affecting more than a few people.
My experience has been that discussions in the forums do not get any
attention at all from Canonical.

If you read all the activity in this and
duplicate bugs (especially #543506) some of us have put a lot of effort
into narrowing down the specific symptoms that cause this class of
"(something) does not start on boot" bug.

My hope is that by accumulating enough evidence here we may get someone
to modify /bin/init so it will determine that /dev/console is writable
before progressing with the /etc/init/*.conf scripts
_or_ fix the underlying kernel bug.

-- 
CUPS and other system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.