On Thu, Jul 01, 2010 at 08:06:52PM -0000, John Edwards wrote:
> For Mike Bianchi - what kernel was your 64-bit machine running? To find
> out run 'uname -a' and post the output.
I don't have access to that machine now, but this from a syslog kept while
debugging. You can see the "Linux version" and later the "init=/sbin/init
--verbose"
May 25 nn:nn:nn autoaud-broad1 kernel: imklog 4.2.0, log source =
/proc/kmsg started.
May 25 nn:nn:nn autoaud-broad1 rsyslogd: [origin software="rsyslogd"
swVersion="4.2.0" x-pid="989" x-info="http://www.rsyslog.com";] (re)start
May 25 nn:nn:nn autoaud-broad1 rsyslogd: rsyslogd's groupid changed to
103
May 25 nn:nn:nn autoaud-broad1 rsyslogd: rsyslogd's userid changed to
101
May 25 nn:nn:nn autoaud-broad1 rsyslogd-2039: Could no open output file
'/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] Initializing
cgroup subsys cpuset
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] Initializing
cgroup subsys cpu
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] Linux version
2.6.32-22-generic (bui...@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) )
#33-Ubuntu SMP Wed Apr 28 nn:nn:nn UTC 2010 (Ubuntu 2.6.32-22.33-generic
2.6.32.11+drm33.2)
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic
root=UUID=c2e45336-da96-4d8e-bd38-3caa7bded803 ro init=/sbin/init --verbose
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] KERNEL supported
cpus:
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] Intel
GenuineIntel
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] AMD AuthenticAMD
May 25 nn:nn:nn autoaud-broad1 kernel: [ nn.nnnnnn] Centaur
Since we are looking at old syslogs, notice the "Failed to spawn rc-sysinit"
line of this snippet ...
May 26 09:37:42 autoaud-broad1 kernel: [ 0.901072] input: Power
Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
May 26 09:37:42 autoaud-broad1 kernel: [ 0.901105] ACPI: Power
Button [PWRF]
May 26 09:37:42 autoaud-broad1 init: Failed to spawn rc-sysinit main
process: unable to open console: Input/output error
May 26 09:37:42 autoaud-broad1 init: rc-sysinit goal changed from start
to stop
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from
spawned to stopping
May 26 09:37:42 autoaud-broad1 init: Handling stopping event
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from
stopping to killed
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from
killed to post-stop
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from
post-stop to waiting
May 26 09:37:42 autoaud-broad1 init: Handling stopped event
May 26 09:37:42 autoaud-broad1 init: Handling net-device-up/failed event
May 26 09:37:42 autoaud-broad1 init: Handling started/failed event
This is one of the things that leads me to believe that we are dealing with an
upstart bug.
Failure to open the console does not sound to me like a good reason to kill a
/etc/init/*.conf script .
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
