[Bug 682831] Re: lost console output early in boot

Scott Moser smoser at ubuntu.com
Mon Oct 7 13:33:47 UTC 2013


** Changed in: plymouth (Ubuntu Lucid)
       Status: Triaged => Won't Fix

** Changed in: linux-ec2 (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: linux-ec2 (Ubuntu Lucid)
       Status: Triaged => Invalid

** Changed in: cloud-init (Ubuntu Lucid)
       Status: Triaged => Won't Fix

** Description changed:

  Binary package hint: plymouth
  
  I see some lost output in the ec2 console log when I boot via pv-grub
  (meaning a kernel and ramdisk is loaded from inside the instance).
  
  Some info:
-  * changing 'console=hvc0' to 'console=tty0' does not seem to change behavior
-  * the "lost" messages are in /var/log/boot.log
-  * disabling plymouth fixes the problem (sudo sh -c 'for x in /etc/init/plymouth*; do mv ${x} ${x}.disabled; done')
-  * I found this when attempting to get lucid able to use pv-grub kernels (Bug 671103)
-  * We saw a similar issue in maverick, but when adding 'console=hvc0' it went away (Bug 606373)
+  * changing 'console=hvc0' to 'console=tty0' does not seem to change behavior
+  * the "lost" messages are in /var/log/boot.log
+  * disabling plymouth fixes the problem (sudo sh -c 'for x in /etc/init/plymouth*; do mv ${x} ${x}.disabled; done')
+  * I found this when attempting to get lucid able to use pv-grub kernels (Bug 671103)
+  * We saw a similar issue in maverick, but when adding 'console=hvc0' it went away (Bug 606373)
+ 
+ Related bugs:
+  * bug 1235231:  plymouth loses output to /dev/console (such as ci-info: messages) 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: plymouth 0.8.2-2ubuntu2.2
  ProcVersionSignature: User Name 2.6.32-310.20-ec2 2.6.32.24+drm33.11
  Uname: Linux 2.6.32-310-ec2 i686
  Architecture: i386
  CurrentDmesg: [   13.731707] eth0: no IPv6 routers present
  Date: Mon Nov 29 19:37:00 2010
  DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
  Ec2AMI: ami-8c0c5cc9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-1b
  Ec2InstanceType: t1.micro
  Ec2Kernel: aki-99a0f1dc
  Ec2Ramdisk: unavailable
  Lspci:
-  
+ 
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcCmdLine: root=UUID=ce492d03-a18c-4075-871e-1631ed7e0244 ro console=hvc0
  ProcEnviron:
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB:
-  
+ 
  ProcModules: ipv6 243034 10 - Live 0xe7a5f000
  SourcePackage: plymouth
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/682831

Title:
  lost console output early in boot

Status in “cloud-init” package in Ubuntu:
  Fix Released
Status in “linux-ec2” package in Ubuntu:
  Invalid
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “cloud-init” source package in Lucid:
  Won't Fix
Status in “linux-ec2” source package in Lucid:
  Invalid
Status in “plymouth” source package in Lucid:
  Won't Fix

Bug description:
  Binary package hint: plymouth

  I see some lost output in the ec2 console log when I boot via pv-grub
  (meaning a kernel and ramdisk is loaded from inside the instance).

  Some info:
   * changing 'console=hvc0' to 'console=tty0' does not seem to change behavior
   * the "lost" messages are in /var/log/boot.log
   * disabling plymouth fixes the problem (sudo sh -c 'for x in /etc/init/plymouth*; do mv ${x} ${x}.disabled; done')
   * I found this when attempting to get lucid able to use pv-grub kernels (Bug 671103)
   * We saw a similar issue in maverick, but when adding 'console=hvc0' it went away (Bug 606373)

  Related bugs:
   * bug 1235231:  plymouth loses output to /dev/console (such as ci-info: messages) 

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: plymouth 0.8.2-2ubuntu2.2
  ProcVersionSignature: User Name 2.6.32-310.20-ec2 2.6.32.24+drm33.11
  Uname: Linux 2.6.32-310-ec2 i686
  Architecture: i386
  CurrentDmesg: [   13.731707] eth0: no IPv6 routers present
  Date: Mon Nov 29 19:37:00 2010
  DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
  Ec2AMI: ami-8c0c5cc9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-1b
  Ec2InstanceType: t1.micro
  Ec2Kernel: aki-99a0f1dc
  Ec2Ramdisk: unavailable
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcCmdLine: root=UUID=ce492d03-a18c-4075-871e-1631ed7e0244 ro console=hvc0
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcModules: ipv6 243034 10 - Live 0xe7a5f000
  SourcePackage: plymouth
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/682831/+subscriptions



More information about the foundations-bugs mailing list