[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2019-01-13 Thread Launchpad Bug Tracker
[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.

[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2018-11-14 Thread Joseph Salisbury
** Tags removed: kernel-key ** Tags added: kernel-da-key -- 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/1792134 Title: Upgrading to 4.15.0-33 caused the system to fail to boot Status

[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2018-10-15 Thread Joseph Salisbury
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2018-10-14 Thread Julien Thomas
Good afternoon. I faced a similar issue today and installed the suggested -35 kernel. Tt did not fix the issue for me however it seems to be an EFI related issue: 1. the grub was always empty (could get grub console from a USB install) 2. the grub console (or menu) was not available without the

[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2018-09-17 Thread Joseph Salisbury
Were you able to test he -35 kernel posted in comment #3? -- 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/1792134 Title: Upgrading to 4.15.0-33 caused the system to fail to boot Status

[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2018-09-15 Thread Michael Richey
Same issue here. Upgrade to 4.15.0-34 gave this error: VFS Unable to mount root fs on unknown-block(0,0) choosing the previous version in grub works. I re-ran update-initramfs and update-grub, no changes. Removed and reinstalled 4.15.0-34, no changes. -- You received this bug notification

[Kernel-packages] [Bug 1792134] Re: Upgrading to 4.15.0-33 caused the system to fail to boot

2018-09-12 Thread Joseph Salisbury
I built a 4.15.0-35 test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792100 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the