[Bug 1160079] Re: plymouth aborts in cloud images
Steve Langasek
steve.langasek at canonical.com
Tue Mar 4 21:45:39 UTC 2014
We've managed to extract a core from one of these crashes; backtrace
follows:
Core was generated by `@sbin/plymouthd --mode=boot --attach-to-session'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fd06f377f79 in __GI_raise (sig=sig at entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x00007fd06f377f79 in __GI_raise (sig=sig at entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007fd06f37b388 in __GI_abort () at abort.c:89
#2 0x00007fd06f370e36 in __assert_fail_base (
fmt=0x7fd06f4c24b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=assertion at entry=0x7fd06f713f37 "terminal != ((void *)0)",
file=file at entry=0x7fd06f713f28 "ply-terminal.c", line=line at entry=611,
function=function at entry=0x7fd06f714860 <__PRETTY_FUNCTION__.7286> "ply_terminal_open") at assert.c:92
#3 0x00007fd06f370ee2 in __GI___assert_fail (
assertion=assertion at entry=0x7fd06f713f37 "terminal != ((void *)0)",
file=file at entry=0x7fd06f713f28 "ply-terminal.c", line=line at entry=611,
function=function at entry=0x7fd06f714860 <__PRETTY_FUNCTION__.7286> "ply_terminal_open") at assert.c:101
#4 0x00007fd06f70e5ff in ply_terminal_open (terminal=0x0)
at ply-terminal.c:611
#5 0x000000000040d6eb in add_display_and_keyboard_for_terminal (
terminal=0x149e900, state=0x7fff14ff8d00) at main.c:1539
#6 add_display_and_keyboard_for_console (console=0x149e8e0 "/dev/ttyS0",
null=<optimized out>, state=0x7fff14ff8d00) at main.c:1953
#7 0x00007fd06f921f63 in ply_hashtable_foreach (
hashtable=hashtable at entry=0x149e710,
func=func at entry=0x40d650 <add_display_and_keyboard_for_console>,
user_data=user_data at entry=0x7fff14ff8d00) at ply-hashtable.c:280
#8 0x000000000040c943 in check_for_consoles (
state=state at entry=0x7fff14ff8d00, default_tty=<optimized out>,
should_add_displays=should_add_displays at entry=true) at main.c:2158
#9 0x000000000040d0ec in on_show_splash (state=0x7fff14ff8d00) at main.c:916
#10 0x00000000004065d9 in ply_boot_connection_on_request (connection=0x149e4d0)
at ply-boot-server.c:702
#11 0x00007fd06f91ee76 in ply_event_loop_handle_met_status_for_source (
status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0x149e5b0, loop=0x1497150)
at ply-event-loop.c:1060
#12 ply_event_loop_process_pending_events (loop=loop at entry=0x1497150)
at ply-event-loop.c:1336
#13 0x00007fd06f91f620 in ply_event_loop_run (loop=0x1497150)
at ply-event-loop.c:1368
#14 0x0000000000404c3d in main (argc=<optimized out>, argv=<optimized out>)
at main.c:2563
--
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/1160079
Title:
plymouth aborts in cloud images
Status in “plymouth” package in Ubuntu:
Confirmed
Bug description:
On cloud-images for EC2 and Windows Azure, plymouth aborts:
On EC2:
[ 22.254620] init: udev-fallback-graphics main process (476) terminated with status 1
[ 23.567151] init: plymouth main process (222) killed by ABRT signal
[ 23.568554] init: plymouth-splash main process (500) terminated with status 2
[ 34.348406] init: plymouth-log main process (683) terminated with status 1
[ 34.383796] init: failsafe main process (684) killed by TERM signal
[ 35.339450] init: plymouth-upstart-bridge main process (743) terminated with status 1
...
[ 91.558062] init: upstart-udev-bridge main process (318) terminated with status 1
[ 91.558099] init: upstart-udev-bridge main process ended, respawning
[ 91.558307] init: upstart-socket-bridge main process (451) terminated with status 1
[ 91.558338] init: upstart-socket-bridge main process ended, respawning
[ 93.223765] udevd[1892]: starting version 175
[ 145.040013] [sched_delayed] sched: RT throttling activated
On Windows Azure:
[ 20.976606] init: udev-fallback-graphics main process (779) terminated with status 1
[ 21.080416] init: plymouth main process (305) killed by ABRT signal
[ 21.080873] init: plymouth-splash main process (795) terminated with status 2
[ 26.593268] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 146.622805] init: plymouth-log main process (885) terminated with status 1
[ 146.682413] init: plymouth-upstart-bridge main process (917) terminated with status 1
[ 266.641541] init: failsafe main process (887) killed by TERM signal
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-14.24~lp1157952v1-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
CurrentDmesg: [ 267.056969] init: plymouth-stop pre-start process (1343) terminated with status 1
Date: Mon Mar 25 22:39:09 2013
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic root=UUID=b3710ec6-2639-4979-9c91-6adf61c4289a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic root=UUID=b3710ec6-2639-4979-9c91-6adf61c4289a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 0247-9366-4976-0268-3671-4900-85
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
---
ApportVersion: 2.9.2-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
CurrentDmesg:
[ 166.490641] init: plymouth main process (1087) killed by ABRT signal
[ 166.492124] init: plymouth-splash main process (1100) terminated with status 2
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
DistroRelease: Ubuntu 13.04
Ec2AMI: ami-3c5bc055
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1d
Ec2InstanceType: t1.micro
Ec2Kernel: aki-88aa75e1
Ec2Ramdisk: unavailable
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MarkForUpload: True
Package: plymouth 0.8.8-0ubuntu6
PackageArchitecture: amd64
ProcCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
ProcFB:
ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
ProcModules:
acpiphp 23954 0 - Live 0x0000000000000000 (F)
dm_crypt 22820 0 - Live 0x0000000000000000 (F)
isofs 39815 0 - Live 0x0000000000000000 (F)
microcode 22881 0 - Live 0x0000000000000000 (F)
ProcVersionSignature: User Name 3.8.0-14.24-generic 3.8.4
Tags: raring ec2-images
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 3.8.0-14-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev video
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1160079/+subscriptions
More information about the foundations-bugs
mailing list