[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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: Expired Status in lvm package in Ubuntu: Expired 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
[Expired for lvm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lvm (Ubuntu) Status: Incomplete => Expired -- 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: Expired Status in lvm package in Ubuntu: Expired 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. Does this issue have any relevance in later, supported releases of Ubuntu? ** Changed in: lvm (Ubuntu) Status: New => Incomplete -- 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: Incomplete 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+attachment/4673598/+files/uname-a.log -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+attachment/4673596/+files/lspci-vvnn.log -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+attachment/4673595/+files/dmesg.log -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+attachment/4673597/+files/version.log -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
Photo of the stacktrace from 3.13.0-86-generic kernel ** Attachment added: "Zdjęcie0320.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+attachment/4673551/+files/Zdj%C4%99cie0320.jpg -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
** This bug is no longer a duplicate of bug 1273261 Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
*** This bug is a duplicate of bug 1273261 *** https://bugs.launchpad.net/bugs/1273261 ** This bug has been marked a duplicate of bug 1273261 Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
Help. I can't help myself. I've read many similar issues but without luck. I did memtest, autoclean, I even enabled only single core just to be sure it's not some way of concurrency issue. Right now I've installed 3.13.0-83 kernel as I believe it was the one I've used without any problems before all this troubles. Below is my apt history which can be treated like suspect as it was last installs before problem appeared. However I didn't find any critical package here (like lvm, luks) but maybe one of you will find something strange: Commandline: apt-get install --reinstall skype Install: skype:amd64 (4.2.0.11-0ubuntu0.12.04.2), libdbusmenu-qt2:i386 (0.9.3+14.04.20140314-0ubuntu1, automatic), skype-bin:i386 (4.2.0.11-0ubuntu0.12.04.2, automatic), sni-qt:i386 (0.2.6-0ubuntu1, automatic) End-Date: 2016-05-09 19:35:39 Start-Date: 2016-05-09 19:47:41 Commandline: apt-get install --reinstall libgl1-mesa-glx:i386 Reinstall: libgl1-mesa-glx:amd64 (10.1.3-0ubuntu0.6), libgl1-mesa-glx:i386 (10.1.3-0ubuntu0.6) End-Date: 2016-05-09 19:47:44 Start-Date: 2016-05-09 19:57:51 Commandline: apt-get purge skype Purge: skype:amd64 (4.2.0.11-0ubuntu0.12.04.2) End-Date: 2016-05-09 19:57:52 Start-Date: 2016-05-10 19:19:59 Commandline: apt-get -y purge linux-headers-3.13.0-83 linux-headers-3.13.0-83-generic linux-image-3.13.0-83-generic linux-image-extra-3.13.0-83-generic Purge: linux-image-extra-3.13.0-83-generic:amd64 (3.13.0-83.127), linux-image-3.13.0-83-generic:amd64 (3.13.0-83.127), linux-headers-3.13.0-83-generic:amd64 (3.13.0-83.127), linux-headers-3.13.0-83:amd64 (3.13.0-83.127) End-Date: 2016-05-10 19:20:54 Start-Date: 2016-05-10 19:28:47 Commandline: apt-get dist-upgrade -y Install: linux-image-extra-3.13.0-86-generic:amd64 (3.13.0-86.130, automatic), linux-image-3.13.0-86-generic:amd64 (3.13.0-86.130, automatic), linux-headers-3.13.0-86:amd64 (3.13.0-86.130, automatic), linux-headers-3.13.0-86-generic:amd64 (3.13.0-86.130, automatic) Upgrade: linux-headers-generic:amd64 (3.13.0.85.91, 3.13.0.86.92), liblcms2-2:amd64 (2.5-0ubuntu4, 2.5-0ubuntu4.1), python-samba:amd64 (4.3.8+dfsg-0ubuntu0.14.04.2, 4.3.9+dfsg-0ubuntu0.14.04.1), openssh-server:amd64 (6.6p1-2ubuntu2.6, 6.6p1-2ubuntu2.7), openssh-sftp-server:amd64 (6.6p1-2ubuntu2.6, 6.6p1-2ubuntu2.7), libtevent0:amd64 (0.9.26-0ubuntu0.14.04.1, 0.9.28-0ubuntu0.14.04.1), openjdk-7-jdk:amd64 (7u95-2.6.4-0ubuntu0.14.04.2, 7u101-2.6.6-0ubuntu0.14.04.1), klibc-utils:amd64 (2.0.3-0ubuntu1, 2.0.3-0ubuntu1.14.04.1), openjdk-7-jre-headless:amd64 (7u95-2.6.4-0ubuntu0.14.04.2, 7u101-2.6.6-0ubuntu0.14.04.1), samba-common-bin:amd64 (4.3.8+dfsg-0ubuntu0.14.04.2, 4.3.9+dfsg-0ubuntu0.14.04.1), ssh:amd64 (6.6p1-2ubuntu2.6, 6.6p1-2ubuntu2.7), samba-libs:amd64 (4.3.8+dfsg-0ubuntu0.14.04.2, 4.3.9+dfsg-0ubuntu0.14.04.1), openssh-client:amd64 (6.6p1-2ubuntu2.6, 6.6p1-2ubuntu2.7), openjdk-7-jre:amd64 (7u95-2.6.4-0ubuntu0.14.04.2, 7u101-2.6.6-0ubuntu0.14.04.1), openjdk-7-source:amd64 (7u95-2.6 .4-0ubuntu0.14.04.2, 7u101-2.6.6-0ubuntu0.14.04.1), libklibc:amd64 (2.0.3-0ubuntu1, 2.0.3-0ubuntu1.14.04.1), icedtea-7-jre-jamvm:amd64 (7u95-2.6.4-0ubuntu0.14.04.2, 7u101-2.6.6-0ubuntu0.14.04.1), linux-doc:amd64 (3.13.0-85.129, 3.13.0-86.130), libwbclient0:amd64 (4.3.8+dfsg-0ubuntu0.14.04.2, 4.3.9+dfsg-0ubuntu0.14.04.1), linux-libc-dev:amd64 (3.13.0-85.129, 3.13.0-86.130), linux-libc-dev:i386 (3.13.0-85.129, 3.13.0-86.130), samba-common:amd64 (4.3.8+dfsg-0ubuntu0.14.04.2, 4.3.9+dfsg-0ubuntu0.14.04.1), linux-image-generic:amd64 (3.13.0.85.91, 3.13.0.86.92), libsmbclient:amd64 (4.3.8+dfsg-0ubuntu0.14.04.2, 4.3.9+dfsg-0ubuntu0.14.04.1), libmms0:amd64 (0.6.2-3ubuntu2, 0.6.2-3ubuntu2.1), linux-generic:amd64 (3.13.0.85.91, 3.13.0.86.92) End-Date: 2016-05-10 19:32:19 Start-Date: 2016-05-12 21:21:55 Commandline: apt-get dist-upgrade -y Upgrade: libnl-genl-3-200:amd64 (3.2.21-1, 3.2.21-1ubuntu1), libnl-3-200:amd64 (3.2.21-1, 3.2.21-1ubuntu1), lsb-base:amd64 (4.1+Debian11ubuntu6, 4.1+Debian11ubuntu6.1), lsb-release:amd64 (4.1+Debian11ubuntu6, 4.1+Debian11ubuntu6.1), libnm-util2:amd64 (0.9.8.8-0ubuntu7.2, 0.9.8.8-0ubuntu7.3), libnm-glib-vpn1:amd64 (0.9.8.8-0ubuntu7.2, 0.9.8.8-0ubuntu7.3), network-manager:amd64 (0.9.8.8-0ubuntu7.2, 0.9.8.8-0ubuntu7.3), libnl-route-3-200:amd64 (3.2.21-1, 3.2.21-1ubuntu1), libnm-glib4:amd64 (0.9.8.8-0ubuntu7.2, 0.9.8.8-0ubuntu7.3) End-Date: 2016-05-12 21:22:17 Start-Date: 2016-05-12 21:23:13 Commandline: apt-get purge linux-generic Purge: linux-generic:amd64 (3.13.0.86.92) End-Date: 2016-05-12 21:23:14Commandline: apt-get install --reinstall skype Install: skype:amd64 (4.2.0.11-0ubuntu0.12.04.2), libdbusmenu-qt2:i386 (0.9.3+14.04.20140314-0ubuntu1, automatic), skype-bin:i386 (4.2.0.11-0ubuntu0.12.04.2, automatic), sni-qt:i386 (0.2.6-0ubuntu1, automatic) End-Date: 2016-05-09 19:35:39 Start-Date: 2016-05-09 19:47:41 Commandline: apt-get install --reinstall libgl1-mesa-glx:i386 Reinstall: libgl1-mesa-glx:amd64
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
I doubt lvm was updated in last 2 weeks. -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
Looking at the stack trace, this could be an lvm bug. I'll add that bug task. ** Also affects: lvm (Ubuntu) Importance: Undecided Status: New -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
Sorry for typo. I mean previous kernel versions didn't boot also. -- 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 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+attachment/4664033/+files/Zdj%C4%99cie0317.jpg ** 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. https://bugs.launchpad.net/bugs/1581761 Title: Kernel panic - not syncing - Attempted to kill init Status in linux package in Ubuntu: Incomplete 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
So no prior kernel version boots? Can you at least mount your disk after you boot with the LiveCD? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
After multiple update-initramfs and kernel reinstalls instead of message 'fstype not found' I have 'can't open /dev/mapper/ubuntu-root no such file'. However all the rest of the stacktrace seems to be similar as already attached photo of the stacktrace. I check if I have installed lvm2 and it is. Installed 3.16.x kernel (or 3.19.x) and situation didn't changed. -- 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: Confirmed 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
I can't run apport-collect. Maybe because I'm chrooted? root@lubuntu:/# sudo apt-get install python-apport Reading package lists... Done Building dependency tree Reading state information... Done python-apport is already the newest version. The following packages were automatically installed and are no longer required: linux-headers-3.13.0-24 linux-headers-3.13.0-24-generic linux-image-3.13.0-24-generic linux-image-extra-3.13.0-24-generic Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. root@lubuntu:/# apport-collect 1581761 You need to run 'sudo apt-get install python-apport' for apport-collect to work. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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: Confirmed 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
** Package changed: ubuntu => linux (Ubuntu) -- 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 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
