Bug #1120660 “Kernel Panic when running 'sudo dpkg --configure -...” : Bugs : upstart package : Ubuntu

Revision history for this message

Rainer Rohde (rainer-rohde) wrote on 2013-02-09:

#1

AlsaInfo.txt Edit (42.0 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (68.0 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (545 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (29.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (533 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.1 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (186 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (148.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (352.8 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (121.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Rainer Rohde (rainer-rohde) wrote on 2013-02-09:

#2

Ok, just now tried to click on "software updater" from the Unity launcher, an I got a kernel panic right away. :(

Revision history for this message

Rainer Rohde (rainer-rohde) wrote on 2013-02-09:

#3

2013-02-09 16.51.06.jpg Edit (3.1 MiB, image/jpeg)

To catch the kernel panic message, I ran apt-get update && apt-get dist-upgrade from the command-line. Please see screenshot attached. I can reproduce this every time.

Revision history for this message

Brad Figg (brad-figg) wrote on 2013-02-09: Status changed to Confirmed

#4

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Rainer Rohde (rainer-rohde) wrote on 2013-02-10:

#5

I guess it comes down to lib6c:i386. I believe I need this to run Crossover and Skype and whatnot...

Revision history for this message

Tobias Wolf (towolf) wrote on 2013-02-10:

#6

I get this too and have narrowed it down to the re-exec of upstart in some packages dpkg postinst scripts.

To trigger the panic you can just run "sudo telinit u"

When I removed the Upstart rexec lines from libc6 and libjson0 postinst the dpkg configure went through.

affects:	linux (Ubuntu) → upstart (Ubuntu)
description:	updated

Revision history for this message

philuser (philuser) wrote on 2013-02-11:

#7

IMG_20130211_082951.png Edit (679.9 KiB, image/png)

Me too am affected by this bug. after the last raring upgrade, the process is terminated with the message:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

After running the command offered, I came across the bug 'kernel panics' see the attached picture.

The 'sudo telinit u' causes the same error panic.

No way to make another upgrade !
Y is there a way to delete the current dpkg?

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-02-11:

#8

Rainer - thanks for reporting this bug.

Please could those affected by this bug comment on whether:

- /var/log/upstart/ exists and is writeable
- their disks are full ('df -h')

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-02-11:

#9

... also, if you can recreate the problem via 'sudo telinit u', please can you run the following command (does not need to be run as root) and append the details to this bug:

initctl list

Thanks

Revision history for this message

philuser (philuser) wrote on 2013-02-11:

#10

Download full text (10.4 KiB)

here is the results of the following command

philuser@meghost:~$ ls -la /var/log/upstart/
total 380
drwxr-xr-x 1 root root 3774 févr. 11 09:19 .
drwxr-xr-x 1 root root 1270 févr. 11 10:36 ..
-rw-r----- 1 root root 81 févr. 6 22:14 alsa-restore.log.1.gz
-rw-r----- 1 root root 81 févr. 5 09:00 alsa-restore.log.2.gz
-rw-r----- 1 root root 140 févr. 1 13:57 alsa-restore.log.3.gz
-rw-r----- 1 root root 66 févr. 4 07:39 console-setup.log.1.gz
-rw-r----- 1 root root 78 févr. 1 13:17 dbus.log.1.gz
-rw-r----- 1 root root 195 févr. 10 13:52 gdm.log
-rw-r----- 1 root root 116 févr. 1 15:56 gdm.log.1.gz
-rw-r----- 1 root root 70 févr. 11 10:36 gssd.log
-rw-r----- 1 root root 180 févr. 11 07:46 gssd.log.1.gz
-rw-r----- 1 root root 63 févr. 10 12:01 gssd.log.2.gz
-rw-r----- 1 root root 178 févr. 6 22:14 gssd.log.3.gz
-rw-r----- 1 root root 202 févr. 5 17:01 gssd.log.4.gz
-rw-r----- 1 root root 30 févr. 11 10:36 hybrid-gfx.log
-rw-r----- 1 root root 38 févr. 11 07:46 hybrid-gfx.log.1.gz
-rw-r----- 1 root root 38 févr. 10 12:01 hybrid-gfx.log.2.gz
-rw-r----- 1 root root 38 févr. 6 22:14 hybrid-gfx.log.3.gz
-rw-r----- 1 root root 38 févr. 5 17:01 hybrid-gfx.log.4.gz
-rw-r----- 1 root root 38 févr. 5 07:39 hybrid-gfx.log.5.gz
-rw-r----- 1 root root 38 févr. 4 07:39 hybrid-gfx.log.6.gz
-rw-r----- 1 root root 35 févr. 2 13:00 hybrid-gfx.log.7.gz
-rw-r----- 1 root root 53 févr. 4 07:39 kmod.log.1.gz
-rw-r----- 1 root root 366 févr. 11 10:36 libvirt-bin.log
-rw-r----- 1 root root 243 févr. 11 07:46 libvirt-bin.log.1.gz
-rw-r----- 1 root root 172 févr. 10 12:01 libvirt-bin.log.2.gz
-rw-r----- 1 root root 227 févr. 6 22:14 libvirt-bin.log.3.gz
-rw-r----- 1 root root 207 févr. 5 17:01 libvirt-bin.log.4.gz
-rw-r----- 1 root root 280 févr. 5 07:39 libvirt-bin.log.5.gz
-rw-r----- 1 root root 191 févr. 4 07:39 libvirt-bin.log.6.gz
-rw-r----- 1 root root 2432 févr. 11 10:36 modemmanager.log
-rw-r----- 1 root root 689 févr. 11 07:46 modemmanager.log.1.gz
-rw-r----- 1 root root 365 févr. 10 12:01 modemmanager.log.2.gz
-rw-r----- 1 root root 642 févr. 6 22:14 modemmanager.log.3.gz
-rw-r----- 1 root root 571 févr. 5 17:01 modemmanager.log.4.gz
-rw-r----- 1 root root 838 févr. 5 07:39 modemmanager.log.5.gz
-rw-r----- 1 root root 367 févr. 4 07:39 modemmanager.log.6.gz
-rw-r----- 1 root root 299 févr. 2 13:00 modemmanager.log.7.gz
-rw-r----- 1 root root 225 févr. 1 14:08 procps.log.1.gz
-rw-r----- 1 root root 216 févr. 6 17:41 procps-static-network-up.log.1.gz
-rw-r----- 1 root root 232 févr. 5 17:01 procps-static-network-up.log.2.gz
-rw-r----- 1 root root 237 févr. 5 07:39 procps-static-network-up.log.3.gz
-rw-r----- 1 root root 226 févr. 4 07:39 procps-static-network-up.log.4.gz
-rw-r----- 1 root root 229 févr. 2 13:00 procps-static-network-up.log.5.gz
-rw-r----- 1 root root 226 févr. 4 07:39 procps-virtual-filesystems.log.1.gz
-rw-r----- 1 root root 124 févr. 11 10:36 qemu-kvm.log
-rw-r----- 1 root root 84 févr. 11 07:46 qemu-kvm.log.1.gz
-rw-r----- 1 root root 82 févr. 10 12:01 qemu-kvm.log.2.gz
-rw-r----- 1 root root 82 févr. 6 22:14 qemu-kvm.log.3.gz
-rw-r----- 1 root root 82...

here is the results of the following command

philuser@meghost:~$ ls -la /var/log/upstart/
total 380
drwxr-xr-x 1 root root 3774 févr. 11 09:19 .
drwxr-xr-x 1 root root 1270 févr. 11 10:36 ..
-rw-r----- 1 root root   81 févr.  6 22:14 alsa-restore.log.1.gz
-rw-r----- 1 root root   81 févr.  5 09:00 alsa-restore.log.2.gz
-rw-r----- 1 root root  140 févr.  1 13:57 alsa-restore.log.3.gz
-rw-r----- 1 root root   66 févr.  4 07:39 console-setup.log.1.gz
-rw-r----- 1 root root   78 févr.  1 13:17 dbus.log.1.gz
-rw-r----- 1 root root  195 févr. 10 13:52 gdm.log
-rw-r----- 1 root root  116 févr.  1 15:56 gdm.log.1.gz
-rw-r----- 1 root root   70 févr. 11 10:36 gssd.log
-rw-r----- 1 root root  180 févr. 11 07:46 gssd.log.1.gz
-rw-r----- 1 root root   63 févr. 10 12:01 gssd.log.2.gz
-rw-r----- 1 root root  178 févr.  6 22:14 gssd.log.3.gz
-rw-r----- 1 root root  202 févr.  5 17:01 gssd.log.4.gz
-rw-r----- 1 root root   30 févr. 11 10:36 hybrid-gfx.log
-rw-r----- 1 root root   38 févr. 11 07:46 hybrid-gfx.log.1.gz
-rw-r----- 1 root root   38 févr. 10 12:01 hybrid-gfx.log.2.gz
-rw-r----- 1 root root   38 févr.  6 22:14 hybrid-gfx.log.3.gz
-rw-r----- 1 root root   38 févr.  5 17:01 hybrid-gfx.log.4.gz
-rw-r----- 1 root root   38 févr.  5 07:39 hybrid-gfx.log.5.gz
-rw-r----- 1 root root   38 févr.  4 07:39 hybrid-gfx.log.6.gz
-rw-r----- 1 root root   35 févr.  2 13:00 hybrid-gfx.log.7.gz
-rw-r----- 1 root root   53 févr.  4 07:39 kmod.log.1.gz
-rw-r----- 1 root root  366 févr. 11 10:36 libvirt-bin.log
-rw-r----- 1 root root  243 févr. 11 07:46 libvirt-bin.log.1.gz
-rw-r----- 1 root root  172 févr. 10 12:01 libvirt-bin.log.2.gz
-rw-r----- 1 root root  227 févr.  6 22:14 libvirt-bin.log.3.gz
-rw-r----- 1 root root  207 févr.  5 17:01 libvirt-bin.log.4.gz
-rw-r----- 1 root root  280 févr.  5 07:39 libvirt-bin.log.5.gz
-rw-r----- 1 root root  191 févr.  4 07:39 libvirt-bin.log.6.gz
-rw-r----- 1 root root 2432 févr. 11 10:36 modemmanager.log
-rw-r----- 1 root root  689 févr. 11 07:46 modemmanager.log.1.gz
-rw-r----- 1 root root  365 févr. 10 12:01 modemmanager.log.2.gz
-rw-r----- 1 root root  642 févr.  6 22:14 modemmanager.log.3.gz
-rw-r----- 1 root root  571 févr.  5 17:01 modemmanager.log.4.gz
-rw-r----- 1 root root  838 févr.  5 07:39 modemmanager.log.5.gz
-rw-r----- 1 root root  367 févr.  4 07:39 modemmanager.log.6.gz
-rw-r----- 1 root root  299 févr.  2 13:00 modemmanager.log.7.gz
-rw-r----- 1 root root  225 févr.  1 14:08 procps.log.1.gz
-rw-r----- 1 root root  216 févr.  6 17:41 procps-static-network-up.log.1.gz
-rw-r----- 1 root root  232 févr.  5 17:01 procps-static-network-up.log.2.gz
-rw-r----- 1 root root  237 févr.  5 07:39 procps-static-network-up.log.3.gz
-rw-r----- 1 root root  226 févr.  4 07:39 procps-static-network-up.log.4.gz
-rw-r----- 1 root root  229 févr.  2 13:00 procps-static-network-up.log.5.gz
-rw-r----- 1 root root  226 févr.  4 07:39 procps-virtual-filesystems.log.1.gz
-rw-r----- 1 root root  124 févr. 11 10:36 qemu-kvm.log
-rw-r----- 1 root root   84 févr. 11 07:46 qemu-kvm.log.1.gz
-rw-r----- 1 root root   82 févr. 10 12:01 qemu-kvm.log.2.gz
-rw-r----- 1 root root   82 févr.  6 22:14 qemu-kvm.log.3.gz
-rw-r----- 1 root root   82 févr.  5 17:01 qemu-kvm.log.4.gz
-rw-r----- 1 root root   85 févr.  5 07:39 qemu-kvm.log.5.gz
-rw-r----- 1 root root   82 févr.  4 07:39 qemu-kvm.log.6.gz
-rw-r----- 1 root root   82 févr.  2 13:00 qemu-kvm.log.7.gz
-rw-r----- 1 root root  128 févr. 11 10:36 rsyslog.log
-rw-r----- 1 root root   89 févr. 11 07:46 rsyslog.log.1.gz
-rw-r----- 1 root root   87 févr. 10 12:01 rsyslog.log.2.gz
-rw-r----- 1 root root   87 févr.  6 22:14 rsyslog.log.3.gz
-rw-r----- 1 root root   87 févr.  5 17:01 rsyslog.log.4.gz
-rw-r----- 1 root root   90 févr.  5 07:39 rsyslog.log.5.gz
-rw-r----- 1 root root   87 févr.  4 07:39 rsyslog.log.6.gz
-rw-r----- 1 root root   84 févr.  2 13:00 rsyslog.log.7.gz
-rw-r----- 1 root root   88 févr. 11 10:36 statd.log
-rw-r----- 1 root root   67 févr. 11 07:46 statd.log.1.gz
-rw-r----- 1 root root   67 févr. 10 12:01 statd.log.2.gz
-rw-r----- 1 root root   67 févr.  6 22:14 statd.log.3.gz
-rw-r----- 1 root root   72 févr.  5 17:01 statd.log.4.gz
-rw-r----- 1 root root   76 févr. 11 08:51 upstart-socket-bridge.log
-rw-r----- 1 root root   95 févr.  6 22:14 upstart-socket-bridge.log.1.gz
-rw-r----- 1 root root   95 févr.  1 14:14 upstart-socket-bridge.log.2.gz
-rw-r----- 1 root root   74 févr. 11 08:51 upstart-udev-bridge.log
-rw-r----- 1 root root   93 févr.  6 22:14 upstart-udev-bridge.log.1.gz
-rw-r----- 1 root root   93 févr.  5 15:26 upstart-udev-bridge.log.2.gz
-rw-r----- 1 root root   89 févr.  5 07:38 upstart-udev-bridge.log.3.gz
-rw-r----- 1 root root   89 févr.  3 10:19 upstart-udev-bridge.log.4.gz
-rw-r----- 1 root root   93 févr.  2 12:58 upstart-udev-bridge.log.5.gz
-rw-r----- 1 root root 1528 févr. 11 10:36 ureadahead-other.log
-rw-r----- 1 root root  216 févr. 11 07:46 ureadahead-other.log.1.gz
-rw-r----- 1 root root  178 févr. 10 12:01 ureadahead-other.log.2.gz
-rw-r----- 1 root root  146 févr.  6 22:14 ureadahead-other.log.3.gz
-rw-r----- 1 root root   92 févr.  5 17:01 ureadahead-other.log.4.gz
-rw-r----- 1 root root   94 févr.  5 07:39 ureadahead-other.log.5.gz
-rw-r----- 1 root root  111 févr.  4 07:39 ureadahead-other.log.6.gz
-rw-r----- 1 root root   77 févr.  2 13:00 ureadahead-other.log.7.gz
-rw-r----- 1 root root   84 févr.  7 13:51 usb-creator-gtk.log.1.gz
-rw-r----- 1 root root  257 févr.  6 22:20 usb-creator-gtk.log.2.gz
-rw-r----- 1 root root  168 févr.  5 17:56 usb-creator-gtk.log.3.gz
-rw-r----- 1 root root  361 févr.  5 07:39 usb-creator-gtk.log.4.gz
-rw-r----- 1 root root  176 févr.  4 07:39 usb-creator-gtk.log.5.gz
-rw-r----- 1 root root  259 févr.  2 13:00 usb-creator-gtk.log.6.gz
-rw-r----- 1 root root   84 févr. 11 10:36 whoopsie.log
-rw-r----- 1 root root   60 févr. 11 07:46 whoopsie.log.1.gz
-rw-r----- 1 root root   60 févr. 10 12:01 whoopsie.log.2.gz
-rw-r----- 1 root root   60 févr.  6 22:14 whoopsie.log.3.gz
-rw-r----- 1 root root   60 févr.  5 17:01 whoopsie.log.4.gz
-rw-r----- 1 root root   62 févr.  5 07:39 whoopsie.log.5.gz
-rw-r----- 1 root root   60 févr.  4 07:39 whoopsie.log.6.gz
-rw-r----- 1 root root   60 févr.  2 13:00 whoopsie.log.7.gz

philuser@meghost:~$ df -h
Sys. fich.     Taille Util. Dispo Uti% Monté sur
/dev/sda2         31G  850M   28G   3% /
udev             7,8G   12K  7,8G   1% /dev
tmpfs            3,2G  948K  3,2G   1% /run
none             5,0M     0  5,0M   0% /run/lock
none             7,8G  1,3M  7,8G   1% /run/shm
none             100M  8,0K  100M   1% /run/user
cgroup           7,8G     0  7,8G   0% /sys/fs/cgroup
/dev/sda4        7,7G  2,1G  4,9G  30% /opt
/dev/sda6         16G  6,2G  7,6G  45% /home
/dev/sda3         16G  3,3G   11G  25% /usr
/dev/sda5         31G  1,9G   27G   7% /var
/dev/sda8        250M  162K  249M   1% /boot/efi

philuser@meghost:~$ initctl list
avahi-daemon start/running, process 1386
cgroup-lite start/running
mountall-net stop/waiting
mountnfs-bootclean.sh start/running
passwd stop/waiting
qemu-kvm start/running
rc stop/waiting
rsyslog start/running, process 1285
tty4 start/running, process 1399
udev start/running, process 440
upstart-udev-bridge start/running, process 438
ureadahead-other stop/waiting
whoopsie start/running, process 1544
apport start/running
console-setup stop/waiting
hwclock-save stop/waiting
idmapd-mounting stop/waiting
irqbalance start/running, process 1493
plymouth-log stop/waiting
rpcbind-boot stop/waiting
tty5 start/running, process 1406
failsafe stop/waiting
hybrid-gfx stop/waiting
modemmanager start/running, process 1342
mountall.sh start/running
rfkill-store stop/waiting
statd start/running, process 1248
atd start/running, process 1457
dbus start/running, process 1307
failsafe-x stop/waiting
mounted-var stop/waiting
plymouth stop/waiting
portmap start/running, process 792
resolvconf start/running
udev-fallback-graphics stop/waiting
autofs start/running, process 1482
checkroot.sh start/running
control-alt-delete stop/waiting
hwclock stop/waiting
mounted-proc stop/waiting
network-manager start/running, process 1426
alsa-store stop/waiting
cups-browsed start/running, process 1438
setvtrgb stop/waiting
shutdown stop/waiting
statd-mounting stop/waiting
alsa-restore stop/waiting
cron start/running, process 1456
gdm start/running, process 1458
lightdm stop/waiting
mountall stop/waiting
mounted-debugfs stop/waiting
mountkernfs.sh start/running
console stop/waiting
mounted-run stop/waiting
acpid start/running, process 1454
bluetooth start/running, process 1344
checkfs.sh start/running
checkroot-bootclean.sh start/running
kmod stop/waiting
libvirt-bin start/running, process 1531
mountnfs.sh start/running
plymouth-stop stop/waiting
rcS stop/waiting
ufw start/running
wait-for-state stop/waiting
bootmisc.sh start/running
flush-early-job-log stop/waiting
friendly-recovery stop/waiting
gssd-mounting stop/waiting
rc-sysinit stop/waiting
cups start/running, process 1375
pulseaudio stop/waiting
upstart-socket-bridge start/running, process 801
anacron stop/waiting
mountdevsubfs.sh start/running
tty2 start/running, process 1424
udevtrigger stop/waiting
container-detect stop/waiting
mounted-dev stop/waiting
mtab.sh start/running
tty3 start/running, process 1427
udev-finish stop/waiting
hostname stop/waiting
mountall-reboot stop/waiting
gssd stop/waiting
mountall-shell stop/waiting
mounted-tmp stop/waiting
network-interface (virbr0) start/running
network-interface (lo) start/running
network-interface (eth0) start/running
network-interface (eth1) start/running
network-interface (wlan0) start/running
plymouth-splash stop/waiting
plymouth-upstart-bridge stop/waiting
portmap-wait stop/waiting
tty1 start/running, process 1682
udevmonitor stop/waiting
usb-creator-gtk stop/waiting
dmesg stop/waiting
mountall-bootclean.sh start/running
network-interface-security (network-manager) start/running
network-interface-security (network-interface/eth1) start/running
network-interface-security (network-interface/eth0) start/running
network-interface-security (network-interface/wlan0) start/running
network-interface-security (network-interface/lo) start/running
network-interface-security (network-interface/virbr0) start/running
network-interface-security (networking) start/running
networking start/running
procps stop/waiting
rfkill-restore stop/waiting
tty6 start/running, process 1429
console-font stop/waiting
idmapd start/running, process 1287
network-interface-container stop/waiting
ureadahead stop/waiting
philuser@meghost:~$

hoping that this will help you to resolve my fatal dpkg kernel panic

Thanks

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-02-11:

#11

@philuser - thanks, but pleaes can you run 'initctl list' on a system that exhibits the bug when 'sudo telinit u' is run?

Revision history for this message

philuser (philuser) wrote on 2013-02-11:

#12

All my command were made for the system affected by the bug, that after reboot because the bug completely freezes the computer.
I am a dipose perform other test, if you want.

Revision history for this message

philuser (philuser) wrote on 2013-02-11:

#13

'sudo telinit u' crash immediaty the PC.

Revision history for this message

philuser (philuser) wrote on 2013-02-11:

#14

'sudo telinit u' command crashes the pc with the symptom already described, then it is no longer possible to switch from another order

Revision history for this message

Tobias Wolf (towolf) wrote on 2013-02-11:

#15

Download full text (3.3 KiB)

To chime in myself and give a differential diagnosis ...

I don’t have /var/log/upstart because /var/log is a tmpfs. Do I have to create this subfolder?

Here’s the output from my PC:

towolf@ovo:~$ initctl list
avahi-daemon start/running, process 845
mountall-net stop/waiting
mountnfs-bootclean.sh start/running
passwd stop/waiting
rc stop/waiting
rsyslog start/running, process 841
screen-cleanup stop/waiting
udev start/running, process 338
upstart-udev-bridge start/running, process 329
ureadahead-other stop/waiting
console-setup stop/waiting
hwclock-save stop/waiting
idmapd-mounting stop/waiting
plymouth-log stop/waiting
rpcbind-boot stop/waiting
failsafe stop/waiting
hybrid-gfx stop/waiting
mountall.sh start/running
rfkill-store stop/waiting
statd stop/waiting
atd start/running, process 977
dbus start/running, process 728
mounted-var stop/waiting
plymouth stop/waiting
portmap stop/waiting
resolvconf start/running
ssh start/running, process 718
udev-fallback-graphics stop/waiting
checkroot.sh start/running
control-alt-delete stop/waiting
hwclock stop/waiting
mounted-proc stop/waiting
network-manager start/running, process 838
alsa-store stop/waiting
cups-browsed start/running, process 956
setvtrgb stop/waiting
shutdown stop/waiting
statd-mounting stop/waiting
alsa-restore stop/waiting
cron start/running, process 5873
gdm start/running, process 962
lightdm stop/waiting
mountall stop/waiting
mounted-debugfs stop/waiting
mountkernfs.sh start/running
binfmt-support stop/waiting
console stop/waiting
mounted-run stop/waiting
acpid start/running, process 959
bluetooth stop/waiting
checkfs.sh start/running
checkroot-bootclean.sh start/running
kmod stop/waiting
mountnfs.sh start/running
plymouth-stop stop/waiting
rcS stop/waiting
wait-for-state stop/waiting
bootmisc.sh start/running
flush-early-job-log stop/waiting
friendly-recovery stop/waiting
gssd-mounting stop/waiting
rc-sysinit stop/waiting
cups stop/waiting
pulseaudio stop/waiting
upstart-socket-bridge start/running, process 861
anacron start/running, process 15918
mountdevsubfs.sh start/running
tty2 start/running, process 932
udevtrigger stop/waiting
container-detect stop/waiting
mounted-dev stop/waiting
mtab.sh start/running
tty3 start/running, process 934
udev-finish stop/waiting
hostname stop/waiting
mountall-reboot stop/waiting
gssd stop/waiting
mountall-shell stop/waiting
mounted-tmp stop/waiting
network-interface (lo) start/running
network-interface (wlan0) start/running
plymouth-splash stop/waiting
plymouth-upstart-bridge stop/waiting
portmap-wait stop/waiting
tty1 stop/waiting
udevmonitor stop/waiting
usb-creator-gtk stop/waiting
dmesg stop/waiting
mountall-bootclean.sh start/running
network-interface-security (network-manager) start/running
network-interface-security (network-interface/wlan0) start/running
network-interface-security (network-interface/lo) start/running
network-interface-security (networking) start/running
networking start/running
procps stop/waiting
rfkill-restore stop/waiting
console-font stop/waiting
idmapd stop/waiting
network-interface-container stop/waiting
ureadahead stop/waiting

towolf@ovo:~$ df -h /var/log/
Filesystem Size Used Avail Use% Mounted on
tm...

To chime in myself and give a differential diagnosis ...

I don’t have /var/log/upstart because /var/log is a tmpfs. Do I have to create this subfolder?

Here’s the output from my PC:

towolf@ovo:~$ initctl list
avahi-daemon start/running, process 845
mountall-net stop/waiting
mountnfs-bootclean.sh start/running
passwd stop/waiting
rc stop/waiting
rsyslog start/running, process 841
screen-cleanup stop/waiting
udev start/running, process 338
upstart-udev-bridge start/running, process 329
ureadahead-other stop/waiting
console-setup stop/waiting
hwclock-save stop/waiting
idmapd-mounting stop/waiting
plymouth-log stop/waiting
rpcbind-boot stop/waiting
failsafe stop/waiting
hybrid-gfx stop/waiting
mountall.sh start/running
rfkill-store stop/waiting
statd stop/waiting
atd start/running, process 977
dbus start/running, process 728
mounted-var stop/waiting
plymouth stop/waiting
portmap stop/waiting
resolvconf start/running
ssh start/running, process 718
udev-fallback-graphics stop/waiting
checkroot.sh start/running
control-alt-delete stop/waiting
hwclock stop/waiting
mounted-proc stop/waiting
network-manager start/running, process 838
alsa-store stop/waiting
cups-browsed start/running, process 956
setvtrgb stop/waiting
shutdown stop/waiting
statd-mounting stop/waiting
alsa-restore stop/waiting
cron start/running, process 5873
gdm start/running, process 962
lightdm stop/waiting
mountall stop/waiting
mounted-debugfs stop/waiting
mountkernfs.sh start/running
binfmt-support stop/waiting
console stop/waiting
mounted-run stop/waiting
acpid start/running, process 959
bluetooth stop/waiting
checkfs.sh start/running
checkroot-bootclean.sh start/running
kmod stop/waiting
mountnfs.sh start/running
plymouth-stop stop/waiting
rcS stop/waiting
wait-for-state stop/waiting
bootmisc.sh start/running
flush-early-job-log stop/waiting
friendly-recovery stop/waiting
gssd-mounting stop/waiting
rc-sysinit stop/waiting
cups stop/waiting
pulseaudio stop/waiting
upstart-socket-bridge start/running, process 861
anacron start/running, process 15918
mountdevsubfs.sh start/running
tty2 start/running, process 932
udevtrigger stop/waiting
container-detect stop/waiting
mounted-dev stop/waiting
mtab.sh start/running
tty3 start/running, process 934
udev-finish stop/waiting
hostname stop/waiting
mountall-reboot stop/waiting
gssd stop/waiting
mountall-shell stop/waiting
mounted-tmp stop/waiting
network-interface (lo) start/running
network-interface (wlan0) start/running
plymouth-splash stop/waiting
plymouth-upstart-bridge stop/waiting
portmap-wait stop/waiting
tty1 stop/waiting
udevmonitor stop/waiting
usb-creator-gtk stop/waiting
dmesg stop/waiting
mountall-bootclean.sh start/running
network-interface-security (network-manager) start/running
network-interface-security (network-interface/wlan0) start/running
network-interface-security (network-interface/lo) start/running
network-interface-security (networking) start/running
networking start/running
procps stop/waiting
rfkill-restore stop/waiting
console-font stop/waiting
idmapd stop/waiting
network-interface-container stop/waiting
ureadahead stop/waiting

towolf@ovo:~$ df -h /var/log/
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1,9G  896K  1,9G   1% /var/log

towolf@ovo:~$ ll -d /var/log/upstart
ls: cannot access /var/log/upstart: No such file or directory

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-02-11:

#16

@Tobias - thanks for confirming. It seems this bug relates to directory /var/log/upstart/ not existing (it will have been auto-created on a default system).

So, one way to work around this issue is to simply create the directory:

$ sudo mkdir -p /var/log/upstart

(This avoids having to modify the postinst scripts which call 'telinit u':

/var/lib/dpkg/info/upstart.postinst
/var/lib/dpkg/info/libjson0:*.postinst
/var/lib/dpkg/info/libc6:*.postinst

)

Could you confirm that creating /var/log/upstart resolves the issue for you?

Revision history for this message

Tobias Wolf (towolf) wrote on 2013-02-11:

#17

James, I cannot confitm that this fixes the issue.

Manually creating it with mkdir /var/log/upstart and doing telinit u still panicked the kernel.

Then I put mkdir /var/log/upstart into /etc/rc.local and it still panicked after a reboot.

Is it that the creation happens too late?

James Hunt (jamesodhunt) on 2013-02-11

Changed in upstart (Ubuntu):
importance:	Undecided → High
assignee:	nobody → James Hunt (jamesodhunt)

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-02-11:

#18

I am now able to reproduce this issue.

The simplest way to work around this issue until we release an update is to boot with '--no-log' to stop Upstart logging any job output.

James Hunt (jamesodhunt) on 2013-02-11

Changed in upstart:
importance:	Undecided → High
status:	New → Confirmed
assignee:	nobody → James Hunt (jamesodhunt)

Revision history for this message

philuser (philuser) wrote on 2013-02-11:

#19

Right... it work for me

Thank

Revision history for this message

filip (bandit-s-fw) wrote on 2013-02-11:

#20

workaround with --no-log worked

Revision history for this message

Lito (lito-eordes) wrote on 2013-02-14:

#21

I have the same problem.

I have my /var/log/ folder in a tmpfs filesystem and the dpkg --configure -a and I have a script to create the default /var/log and /var/cache folders. The folder /var/log/upstart exists.

Please, can you explain me where I need to add the "--no-log" option?

Thanks :)

Revision history for this message

filip (bandit-s-fw) wrote on 2013-02-14:

#22

@Lito
in the grub boot screen (if you don't see it, press shift right after bios, sometimes you need to try several times as for me it doesn't always works and it just boots right away)
use the 2nd entry (advanced i think it is called)
than highlight the first entry and hit e to edit
there you add the --no-log in between the commands quiet and (no)splash
I editted on 2 places, you will see there some kind of if loop.
than just hit F10 to boot. That worked for me.

Revision history for this message

Lito (lito-eordes) wrote on 2013-02-14:

#23

Ok, it's the same line that I can edit in /etc/default/grub?

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash elevator=deadline"

to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash elevator=deadline --no-log"

Thanks.

James Hunt (jamesodhunt) on 2013-03-08

Changed in upstart:
status:	Confirmed → Fix Released
Changed in upstart (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Rafał Cieślak (rafalcieslak256) wrote on 2013-03-16:

#24

Has this been fixed? I seem to be affected by this bug, yet I cannot update upstart to the newest version, as it triggers kernel panic when it's configured. I also cannot boot up with the --no-log option, because this causes a kernel panic immediately when the system begins to boot. I would welcome ideas on how to upgrade upstart while omitting the configuring phase, or getting around the kernel panic in some other way.

Should I report a new bug, or is it actually the same as this one, and it's just my system that cannot upgrade?

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-03-22:

#25

@Rafal - yes, the problem has been fixed in Ubuntu. Are you sure you are specifying the "--no-log" option correctly (two leading dashes)? The problem that was fixed relates directly to logging and that option disables logging entirely.

If you still have a problem, please do the following:

1) modify the boot command line in grub to add "--no-log --debug" but also remove "quiet" and "splash".
2) boot
3) take a picture of the messages on the screen and attach to this bug if possible.

Revision history for this message

alien (nalex2004) wrote on 2013-10-14:

#26

Almost every update now on Ubuntu 13.10 gives kernel panic during update.
Message like "kernel panic ..." something about "..init.."
next line "drm_kms_helper: panic occurred, switching back to text console"
lenovo g575. i386

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-10-15:

#27

@alien: Please raise a new bug with full details - take a picture of the screen showing these messages if possible and attach to the bug.

Revision history for this message

Aurel Branzeanu (thunder-riscom) wrote on 2014-01-15:

#28

150120141292.jpg Edit (502.1 KiB, image/jpeg)

My system, 64-bit Trusty, also got this bug when running 'sudo dpkg --configure -a'.
Alas, there are no log entries for this panic.
Please, take a look at the attachments and initctl list output below:

user-03-709@709-3:~$ initctl list
indicator-application start/running, process 2626
indicator-sync start/running, process 2628
unicast-local-avahi stop/waiting
update-notifier-crash stop/waiting
update-notifier-hp-firmware stop/waiting
xsession-init stop/waiting
dbus start/running, process 2328
update-notifier-cds stop/waiting
gnome-session start/running, process 2387
ssh-agent start/running
unity7 stop/waiting
unity-voice-service stop/waiting
upstart-dbus-session-bridge start/running, process 2374
logrotate stop/waiting
unity-panel-service start/running, process 2452
hud start/running, process 2381
im-config start/running
unity-gtk-module stop/waiting
session-migration stop/waiting
upstart-dbus-system-bridge start/running, process 2456
at-spi2-registryd stop/waiting
update-notifier-release stop/waiting
indicator-datetime start/running, process 2636
indicator-sound start/running, process 2638
upstart-file-bridge start/running, process 2373
gnome-settings-daemon start/running, process 2377
window-stack-bridge start/running, process 2340
re-exec stop/waiting
upstart-event-bridge start/running, process 2336
indicator-session start/running, process 2640

Revision history for this message

James Hunt (jamesodhunt) wrote on 2014-01-15:

#29

@Aurel - please raise a new bug by running "ubuntu-bug upstart" as this will attach all relevant information to the bug to allow us to investigate the problem. Thanks.

Revision history for this message

Arthur Borsboom (arthurborsboom) wrote on 2014-01-18:

#30

Yep, got the same issue on trusty.

The last thing on the console I see is setting up libc6:amd64 and then it changes into a black screen with a blinking cursor.
When I boot by adding "text" to grub I see a kernel panic which I am unable to capture in a log file.

Ubuntu
upstart package

Kernel Panic when running 'sudo dpkg --configure -a' ?

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	upstart	Fix Released	High	James Hunt
	upstart (Ubuntu)	Fix Released	High	James Hunt

Ubuntuupstart package

Kernel Panic when running 'sudo dpkg --configure -a' ?

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
upstart package