← Back to team overview

kernel-packages team mailing list archive

[Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init


No prior kernel version boots. Yes, I can mount disks via LiveCD.

I tested the lates kernel from here http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.6-yakkety. It don't solve my problem. I attached new
photo with the stacktrace from that kernel.

I think that kernels are ok as I didn't had such issues in the past.
Maybe my OS has broke in some place? In the stacktrace there's line
stating that ubuntu-root is not existing. It does exist. I am able to
mount it via liveCd. So maybe it's some timing issue? Maybe LVM won't
initialize so fast as script would like to? In general I was updating
ubuntu once or two per month so in general I was using every kernel
ubuntu has released (I use 14.04 lts). I don't have feeling that this
happened right after update.

I do suspend my computer (to ram) on daily basis from many years but
this rather could not broke my OS(?).

** Attachment added: "Photo of stacktrace from mainline v4.6-yakkety kernel"

** Tags added: kernel-bug-exists-upstream

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Kernel panic - not syncing - Attempted to kill init

Status in linux package in Ubuntu:

Bug description:
  Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to kill init'. I tried to use previous kernel, then reinstall kernels but all that didn't help me. I have luks encrypted partition which contains multiple lvm with ext4 volumes. This was working since 14.04 was released so this not standard configuration should not cause this issue.
  I am able to run live cd, then decrypt luks partition and mount volumes and chroot. All seems to be ok. I fsck lvm and all is ok.
  I found similar issue https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping for 5 secs" message on the stacktrace in the middle) but this didn't solve the issue. Maybe I enter this hack too early in the script?

  No more idea... so mayday, mayday...
  I attached photo of the stacktrace and report of 'apport-cli linux-generic'.

To manage notifications about this bug go to: