← Back to team overview

kernel-packages team mailing list archive

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

 

I think it was similar to
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 but
that seems to be marked as fixed.

It's 15 days I can't start my Linux :( Can anyone help me?

Yesterday I made those steps (via chroot):
apt-get autoclean
apt-get clean
apt-get update
apt-get upgrade
apt-get dist-upgrade
apt-get -f install
dpkg --configure -a
apt-get install linux-generic (3.13.0-86-generic was installed)
update-initramfs.distrib -k all -c
update-grub2

I can't still boot but I've got little different stacktrace. I attach
photo of this stacktrace.

More over I get my backup and verified if there were changes in /etc but
there were none that I could suspect for giving me this issue. In past I
had many kernel panics... but then usually update-initramfs -k all -c
solve the problem. However this issue is helpless.

Anyone please? 15 days without computer is like a year. I don't even
have a hint what else I can do.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1581761

Title:
  Kernel panic - not syncing - Attempted to kill init

Status in linux package in Ubuntu:
  Incomplete
Status in lvm package in Ubuntu:
  New

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+subscriptions