On Mon, Aug 02, 2010 at 03:24:28AM -0000, Robbie Williamson wrote:
> :
> 2) It has *something* to do with when lo0 is activated, i.e. a race condition
I disagree, it has something to do with not being able to write /dev/console.
See my analysis in bugs 581291 and 543506.
> 3) There are apparently a few hacky workarounds, but no fix
They _are_ hacky, _BUT_ they give some of us reliable boots.
They should be distributed until a fix is found.
> 4) There is no concrete evidence that this is a kernel issue
> 5) There is no concrete evidence that this is an upstart issue
I disagree. There is strong, but inconclusive, evidence that it is EITHER
a kernel or upstart issue (maybe both). Again see 543506.
> This bug is officially "on the radar", so we will figure out what's
> causing the issue and address it in an SRU, but it's too late for
> 10.04.1.
I do not see why the hacky workarounds can not be part of the official
distribution until the real fixes are implemented.
I strongly recommend distributing the workarounds, including the
init='/bin/sbin --verbose'
I had some evidence that it _helped_ improve boot reliability.
It certainly helped with boot sequence visibility.
I would think you would want to increase the population of reliable boots.
The evidence is that over the past months newer 10.4 updates have been
reducing that population.
On Mon, Aug 02, 2010 at 03:24:28AM -0000, Robbie Williamson wrote:
> :
> 2) It has *something* to do with when lo0 is activated, i.e. a race condition
I disagree, it has something to do with not being able to write /dev/console.
See my analysis in bugs 581291 and 543506.
> 3) There are apparently a few hacky workarounds, but no fix
They _are_ hacky, _BUT_ they give some of us reliable boots.
They should be distributed until a fix is found.
> 4) There is no concrete evidence that this is a kernel issue
> 5) There is no concrete evidence that this is an upstart issue
I disagree. There is strong, but inconclusive, evidence that it is EITHER
a kernel or upstart issue (maybe both). Again see 543506.
> This bug is officially "on the radar", so we will figure out what's
> causing the issue and address it in an SRU, but it's too late for
> 10.04.1.
I do not see why the hacky workarounds can not be part of the official
distribution until the real fixes are implemented.
I strongly recommend distributing the workarounds, including the
init='/bin/sbin --verbose'
I had some evidence that it _helped_ improve boot reliability.
It certainly helped with boot sequence visibility.
I would think you would want to increase the population of reliable boots.
The evidence is that over the past months newer 10.4 updates have been
reducing that population.