[Bug 1120660] Re: Kernel Panic when running 'sudo dpkg --configure -a' ?

[Tobias Wolf]

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 at 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 at ovo:~$ df -h /var/log/
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1,9G  896K  1,9G   1% /var/log


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

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

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

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Recently, I am seeing a few kernel panics. [ Assertion failed in
  log_serialise ]

  The latest one happens when asked to run E: dpkg was interrupted, you
  must manually run 'sudo dpkg --configure -a' to correct the problem.

  I've also seen them when trying to change compiz settings.

  They seem to have started a couple of days ago in the middle of an
  upgrade, I guess during some Xorg and/or nvidia related upgrades.

  However, it happens now each and every time when running 'sudo dpkg
  --configure -a'.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-5-generic 3.8.0-5.10
  ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
  Uname: Linux 3.8.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  rrohde     2427 F.... pulseaudio
   /dev/snd/controlC0:  rrohde     2427 F.... pulseaudio
  Date: Sat Feb  9 16:33:02 2013
  MachineType: ASUSTeK COMPUTER INC. G75VW
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-5-generic root=UUID=c8cd22e4-05f7-4b13-94d4-1899febff264 ro elevator=noop acpi_osi=linux splash acpi_backlight=vendor quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-5-generic N/A
   linux-backports-modules-3.8.0-5-generic  N/A
   linux-firmware                           1.101
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G75VW.222
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G75VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.222:bd11/06/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G75VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1120660/+subscriptions