[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2019-02-14 Thread Andy Whitcroft
This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed. ** Tags removed: verification-needed-bionic ** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic -- You received this bug

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-12-30 Thread Anantha Krishna K S
Wifi not working after upgrading to Disco Dingo development version -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-11-17 Thread Rob Tongue
Adding my $0.02, whatever it is worth. I ran into this on a RamNode VPS. downgrading to 4.15.0-20-generic made it boot again. Attaching dmesg from that machine. $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name :

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-10-28 Thread chetan Mehra
Hi I am on Carbon X1 2015 and I was using ubuntu mate 16.04. The system suggested that I update to 18.04. I did that and went for run. I came back my screen was still there but the menu was gone. I forced a restart. I now get a screen for bios load then sda3_crypt. I put in my password and I get

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-09-21 Thread Sib Andela
** Changed in: ubuntu Status: Confirmed => Fix Released -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-09-20 Thread Stefan Szabo
Linux 4.15.0-34 fails to boot in VirtualBox. 4.4.0-135 boots OK, same everything else. stefan@stefan-lubuntu12:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic stefan@stefan-lubuntu12:~$ uname -a

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-09-04 Thread jerome
I have this exact issue with ANY kernel above 4.15.0-20. I tried over a dozen different versions higher and ONLY 4.15.0-20 works straight away. So I seriously doubt its an issue with just 4.15.0-24, at least on my machine. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-08-04 Thread Gannet
Hello. With kernel -29 my VM boots fast as usual. But another strange thing I'm discovering is that plymouth image still blinking over desktop. It happens from time to time. Not always, but regularly. -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-08-04 Thread azanaz
The updated kernel doesn't fix the issue for me. I still need to have 3 or 4 usb sticks connected to the computer so it can boot correctly and not get stuck on a blank screen. Probably still an entropy issue. -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-27 Thread Joachim Schwender
I noticed similar effect with very recent (4.17) kernels. In 4.16.8 there were changes in random.c due to a security flaw. The function that detects "having enough entropy" is now strictly blocking. In the early boot phase this is bad on any machine without enough entropy sources. The kernel has 3

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-25 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-29.31 --- linux (4.15.0-29.31) bionic; urgency=medium * linux: 4.15.0-29.31 -proposed tracker (LP: #1782173) * [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler (LP: #116) - ipmi_ssif: Fix kernel panic

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-24 Thread moe
@Joseph Salisbury: I am confused. Looking at USN-3718-1 (https://usn.ubuntu.com/3718-1/) and USN-3718-2 (https://usn.ubuntu.com/3718-2/) it seems like CVE-1108 is fixed in Ubuntu 18.04 LTS for several linux kernel flavors (azure, gcp, hwe, kvm, oem and stock) and a subset for Ubuntu 16.04 LTS.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-24 Thread moe
I mean CVE-2018-1108 ... -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed Status in linux

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-20 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-29.31 --- linux (4.15.0-29.31) bionic; urgency=medium * linux: 4.15.0-29.31 -proposed tracker (LP: #1782173) * [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler (LP: #116) - ipmi_ssif: Fix kernel panic

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-18 Thread Joseph Salisbury
** Tags removed: kernel-key ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-18 Thread Piotr Czekalski
Same here with Lenovo Yoga S1 laptop :(. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Confirmed

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-16 Thread TR Precht
This effected me after my first reboot in a couple weeks. I tried earlier kernels, still wouldn't boot. Hangs on "[ OK ] Started GNOME Display Manager. Dispatcher Service..tem changes.pp link was shut down" I was able to switch to lightdm to get in, but any time I try to update I get

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-16 Thread Ralf Hersel
Installing the entropy daemon 'haveged' (sudo apt install haveged) worked on my notebook (Clevo, Tuxedo MS-1753, Kernel 4.15.0-24-generic). Boot time is as normal. Also manually adding entropy by moving the mouse like hell, reduced the boot time from 5 to 1.4 minutes. -- You received this bug

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-15 Thread Mark Fraser
Seeing this on Kubuntu 18.04 too. The haveged work around worked yesterday, but this morning I had to go back to 4.13 - the only previous kernel I have installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-15 Thread Wes Newell
Has to be the right shift key on my 18.04lts system, but I've always just used tapping the Esc key immediately after post until the grub menu comes up. I explained earlier how to remove the .24 kernel. But don't try to remove the one you are running at the time. Not sure what would happen then.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-15 Thread Ki Sung Bae
@delosari https://forum.snapcraft.io/t/snapd-service-delays-startup-in- ubuntu-18-04-with-4-15-0-24/6205/10 says pressing shift key continuously during boot could be a workaround. It worked for me. -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-15 Thread delosari
Thank you Wes Newell for your reply. I only installed ubuntu on this computer (big big big mistake) I do not have the grub menu at start. After typing many commands which I did not understand ubuntu started. I have lost the sound however and now I am afraid to turn it off. If I run: dpkg -l |

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-14 Thread Wes Newell
Easiest thing to do is just delete the .24 kernel. During boot, start tapping the esc key repeatedly. You should get the grub menu. Select the advanced option, and then load the last good kernel, which should be the .23 one if you've kept the system up to date. Once it boots and everything is

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-14 Thread delosari
Please could anyone share some detailed instructions on how to apply these quick fixes... I am having these issues with my dell Inspiron 15 7000 series all of a sudden with ubuntu 18.04 I try to run ctrl+alt+f1 but it goes to bios. Please some advice... I am having this issue just know while

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread Mark
@joverstreet1, kernel 24 was installed first, by Ubuntu Software Updater. I then installed haveged to work around a kernel change to getrandom(). My SSD is not Western Digital but the SSD has nothing to do with the problem, at least not the one that is the focus of this bug report. The kernel

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread wpshooter
tim-smith: I installed haveged and then install kernel #24 and unlike before now seems to boot and run just fine. Are the developers of the kernel aware of this problem ? Sounds like adding haveged is a patchwork fix at best and that some change to the kernel itself needs to be made - what that

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread wpshooter
Did you install haveged "BEFORE" you attempted update to kernel #24 ? Is you SSD a Western Digital, may I ask ? Perhaps haveged is a solution but does not sound like a particularly good one. How is one supposed to know that they have to do this ? Sounds like to me that there is something in

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread Mark
@m-tim-smith, comment #85, if none of the fixes/workarounds here are working for you, perhaps you have a different problem with very similar symptoms. For example bug #1779476. @joverstreet1, comment #86, I have an SSD and my system's been running fine with kernel 24 since I installed haveged.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread Gannet
>I have come to the conclusion that the problem with the #24 Linux Kernel is >related to the use of SSD hard drives. Really? Well, how smart! Just try to read a previous posts and you'll understand that you're completely wrong. -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread wpshooter
I have come to the conclusion that the problem with the #24 Linux Kernel is related to the use of SSD hard drives. I just took my SSD out of my computer and replaced it with an old manual / mechanical hard drive and installed Linux Mint 19 on it including the #24 Kernel and it worked/booted

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread Tim
@dimztimz - could you elaborate on what u did specifically? Other solutions above (not the patched kernel) don't work for me. -- 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/1779827 Title:

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-12 Thread Dimitrij Mijoski
I am also affected by this, and it is most likely the issue with entropy for randomness, because if I mash some random keys, I get to boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-11 Thread AlwaysTired
I'm happy to report that I was able to boot normally with gdm now, and it didn't get stuck. Yesterday I removed and reinstalled gdm3 and ubuntu-desktop, as suggested here, rebooted, but it was still the same (i.e. stuck in reboot), so I switched back to lightdm. Today when I turned it on it

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-11 Thread Daniel van Vugt
** Changed in: linux (Ubuntu Bionic) Milestone: None => ubuntu-18.04.1 -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-11 Thread Zakhar
Sorry... my "bug" was PEBCAK! It has nothing to do with entropy. I copied the system from an old HDD to a SDD, and in the process didn't change the resume UID that sits in: /etc/initramfs-tools/conf.d/resume It was still pointing to a partition UID on the old disk. Hence when the old disk was

Re: [Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-10 Thread mocnak
before I wanted reply to your question, I rebooted my laptop, and now I'm stuck on boot screen - so not the same as error described here. Anyway, it helped me just to log-in once and now I'm on OS unable to boot properly again. It took around 3 minutes to show me login screen. On Tue, Jul 10,

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-10 Thread bas bb
Tried mocnak's solution, no effect Regular install 5 weeks old, update snappy breaks, update no more gui. Mocnak solution, zero effect, in syslog gdm complains about wrong parameters. I am running a AMD a12 laptop, 16gbyte ram, 256gbyte ssd, 207gbyte free disk space. All filesystems 90% or

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-10 Thread Mark
@mocnak, re. comment #78. Thanks. I reinstalled gdm3 but didn't think about ubuntu-desktop. Anyway I've reverted to the existing Ubuntu version of plymouth and got my system working again (with haveged). Did you try the fixed Plymouth? -- You received this bug notification because you are a

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-10 Thread mocnak
what helped me, when I was stuck on black boot screen, was to reinstall Gnome: sudo apt purge gdm3 sudo apt install gdm3 ubuntu-desktop systemctl restart gdm after that everything works. - Running Ubuntu 18.04 -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-10 Thread nickkon
Also confirm this bug at my DELL E4310. System boots very slowly. Reverting to *23 kernel fixed this problem. -- 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/1779827 Title: failure to

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-09 Thread Mark
This still looks like the getrandom() hang described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572. This was caused by the fix in the kernel for CVE-2018-1108. Two complementary fixes have been discussed in the Debian bug neither of which modify the kernel. The first is a change to

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Daniel van Vugt
Kurt, If you have an i3-350M then please see bug 1727356 instead. In fact, everyone using an Intel CPU from 2010 or earlier please see bug 1727356 instead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Rodrigo M. R. Avila
#50 : Another workaround besides the 'haveged' is 'rng-tools5'. I've booted through kernel version(4.15.0-23), installed the package 'rng- tools5' (because my processor supports it - intel 3rd generation or newest) and now i'm able to boot kernel 4.15.0-24 again. -- You received this bug

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Kurt Smolderen
The kernel provided in the proposed channel does not solve the issue for me. I also encounter the described boot issue in -23, -24 and -26 kernels. A workaround for me is using lightdm as display manager instead of gmd3. What was proposed in this thread and didn't work for me: * Installing havegd

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Charles Burns
Participating in bug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476 for the last couple of days. Clevo barebook W540 pentium 3805U 1.90G onboard graphics BroadwellGT1 single ssd, intel Wless 3160, only hardware hanging off it is a usb wireless mouse. Had indefinite hang begin with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread AlwaysTired
Mine is a Toshiba Satellite Z30-A-1E9 laptop with a single SSD. I tried booting with the 4.15.0-26-generic kernel now with an external HDD attached, and still couldn't boot - I waited for more than 3.5min and it was still stuck on the "before the ppp link was shut down" message, so I switched to

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Zakhar
** Attachment added: "Boot with SSD + spinning rust HDD plugged to USB2" https://bugs.launchpad.net/ubuntu/+bug/1779827/+attachment/5160961/+files/dmesg3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Zakhar
** Attachment added: "Boot with SSD only + touching trackpad/keyboard" https://bugs.launchpad.net/ubuntu/+bug/1779827/+attachment/5160960/+files/dmesg2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Zakhar
I am also attaching the full 3 dmesg if some other differences I could not spot seem significant for you. ** Attachment added: "Boot with SSD only" https://bugs.launchpad.net/ubuntu/+bug/1779827/+attachment/5160959/+files/dmesg1 -- You received this bug notification because you are a member

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-08 Thread Zakhar
Sorry, but the bug also happens with 4.15.0-23 I upgraded a PC with a SSD replacing a HDD. So this laptop now only has a SSD which obviously has no spinning part to produce entropy to seed the random generator. Here is what happens: -1) not touching anything, there is a "30 seconds gap" (visible

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-07 Thread Wes Newell
I only had the slow boot problem on 2 out of 3 systems with the .24 kernel. Both systems that had problems had single ssd drives in them. One was an ECS GF8200A mb and the other was a jetway GF8200 based mb. The system that didn't have a problem was also an ECS GF8200A mb, but does not have a ssd

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-07 Thread Gannet
Installing *-26-th kernel from a proposed fixes the issue with very slow booting on my system. -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-07 Thread Charles Burns
Booting into the *-26 kernel gave a very quick handover to Gnome, but with some kind of badly painted cursor and progress images apparently bleeding through from the plymouth screens. However the deal breaker is that networking isn't enabled at all. Report then is that *-26 kernel is not a

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread Nataraj
Yep, that's the same version that is installed in my VM. So it looks like the new -26 kernel does not fix the problem for everybody. It worked for me, but doesn't seem to work for you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread AlwaysTired
Yes, the current output of uname -r is 4.15.0-26-generic, and this is the /var/log/dpkg.log output, is it the right one? 2018-07-06 17:44:45 startup archives unpack 2018-07-06 17:44:45 install linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28 2018-07-06 17:44:45 status half-installed

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread Nataraj
@alwaystired - Did you verify that you have installed the new .26 version? -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread Wes Newell
I had already installed everything from the proposed mirror using software updater, but it didn't install the new .26 kernel on the 2 affected machines. So I installed the image, headers, module-extra packages using apt-get install /bioic-proposed. that worked and everything worked fine afterwards

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread AlwaysTired
I updated the kernel through the bionic-proposed channel, but it still got stuck at startup: "Started Dispatcher daemon for systemd-networkd.ce..before the ppp link was shut down" had to revert back to lighdm in order to reboot. -- You received this bug notification because you are a

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread Nataraj
You don't need to install all of the updates from the -proposed repository, only the kernel. When you check the proposed box in the software updater, you are effectively adding the following line to /etc/apt/sources.list (mirror is whatever mirror you have chosen): deb

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread Wes Newell
Don't know why the new kernel didn't install from the software updater, but after manually installing it, it works fine. Now to do the same on other machine. Funny it all installed fine with the software updater on my main machine. -- You received this bug notification because you are a member

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread Øyvind Stegard
Tested linux-image-4.15.0-26-generic-4.15.0-26.28 from bionic-proposed, and with it system boots quickly again (without haveged-workaround in place). Dell E7440-laptop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-06 Thread Nataraj
I have tested 4.15.0-26-generic from the -proposed repository and it runs fine under kvm/qemu. The -24 version did not boot for me under kvm/kemu. Not sure if I am supposed to change the tag to verification- done-bionic or if that is supposed to be done by the person who originally filed the bug

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Wes Newell
After turning on developer options for pre-release upgrades and installing a lot of stuff, I still have the same problem with the slow boot on the 2 machines I updated. uname-a shows same as before.Is that normal? I turned off developer stuff afterwards. Since 4.15.0-23 works fine, should I just

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Daniel van Vugt
I agree, if plymouth turns out to be the real problem then no kernel change is necessary. Changing the kernel would be only a workaround for the plymouth hang. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Mark
This appears to be a duplicate of bug #1779476. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu:

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Kristijan Žic 
Any workaround besides the haveged? haveged didn't work for me. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Mark
Reverting the fix for CVE-2018-1108 to get this to work is not necessary and not a good idea. The root cause has been identified upstream in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 and fixes committed. Turns out it was fontconfig generating a uuid that tripped over the CVE fix.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Vance Morris
The install of package haveged workaround also did not work for me - I was getting boot hangs in my KVM guest installation, waiting for 3 services to start. After installing haveged, I only hang on something called "hold until start processes finish up" for about 15 seconds, then a permanent hang

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Vance Morris
"haveged" Is this a joke? I went to college dammit! ;D -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Kristijan Žic 
How long will it take for that fix to reach the end users? -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Magnus
Thanks for the quick response to this issue -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu:

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic) Status: Fix Released => Fix Committed -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-05 Thread Gannet
My Ubuntu boots 8-11 minutes with 4.15.0-24. With 4.15.0-23 it boots quickly. Please, fix this damn regression! -- 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/1779827 Title: failure to

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Michal Maleszka
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Stefan Bader
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Pablo
How do you install test kernel? I tried dpki -i linux-modules-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb linux-modules-extra-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb but I get error: Preparing to unpack

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Pablo
Same problem with Dell Precision M3800 with Ubunto 18.04 Updated yesterday July 3, when I booted today, July 4, boot process gets stuck Last few lines of /var/log/boot.log: [^[[0;32m OK ^[[0m] Reached target Network. Starting Permit User Sessions... [^[[0;32m OK ^[[0m] Started

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread staedtler-przyborski
Gratulations to Joseph Salisbury the test kernel works like a charm My Lenovo T520 boots rather quick without having haveged installed. Thanks for this quick fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Joseph Salisbury
Can folks affected by this bug test the following kernel: http://kernel.ubuntu.com/~jsalisbury/lp1779827/ Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic)

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread AlwaysTired
Installing haveged didn't work for me (currently using lightdm as a workaround). -- 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/1779827 Title: failure to boot with

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread perry
Happy confirmed as well! sudo apt install haveged fixes the issue. -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Adrian
I can confirm that installing the 'haveged' package solves the issue. If lack of entropy was the issue, it makes sense that tinkering with the the non-graphical terminal caused the boot to proceed where plain waiting didn't. -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread staedtler-przyborski
According to this page https://debianforum.de/forum/viewtopic.php?f=33=169585=entropie This newly introduced fix in 4.15.0-24 is the cause 'random: fix crng_ready() test' when it's reverted (like in debian 4.9.88-1+deb9u1) boot is fine again 'linux (4.9.88-1+deb9u1) stretch-security;

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread staedtler-przyborski
Have a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897631 it seems the kernel update breaks gdm ** Bug watch added: Debian Bug tracker #897631 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897631 -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Krzysztof Kolasa
I confirm stopping the system loading on the "Ubuntu" board on the kernel 4.15.0-24, the problem is probably related to the nvidia graphics card, my hardware: 00:00.0 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a1) 00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Yaroslav
Same issue on the workstation, few hours spent to fix it by reinstalling gnome, gdm3, apparmor, loading previous kernel, switching to lightdm. Nothing helps, complete reinstall. Very frustrating, because need to return to configuration/installing apps for next the few weeks. With Ubuntu you

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Adrian
I'm not sure if my issue is related: I upgraded to 4.15.0-24 yesterday (no other updates) and this morning I get a blank screen on boot that sits there indefinitely (i.e. minutes). To fix this, I CTRL-ALT-F6 to get another tty, which immediately show up. This however seems to trigger some event,

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Frank
CTRL-ALT-F1 and check the boot sequence for what it using 2 minutes for. Might be what I experienced: sudo apt-get install --reinstall apparmor systemctl start nmbd.service There might be several more services like that. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Jindrich Ocenasek
Hi, on my X230 I have run a fresh installation from USB and then update to the 4.10.0-24. Now the computer boots but it takes much more time. It hangs for cca 2 minutes on the Ubuntu dots screen with all 5 dots white and does not react at all. -- You received this bug notification because you

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Frank
Here a screen dump of the packages, as required, that causes my incident, I guess! It is from a T460 and was opened July 4th. Please find dump attached. ** Attachment added: "Screendump of Software Updater and suspecious packages"

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread staedtler-przyborski
As no trick mentioned here worked ... I made a fresh install and updated everything except the kernel (which remains at 4.15.0-20). And my Lenovo T 520 works again. So indeed kernel 4.15.0-24 seems the culprit. No glue why booting to previous installed kernels doesn't work either as soon

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Alessandro
Same problem here with T440s. I found a quick workaround. I put the computer in standby when the 5 dots of ubuntu logo are stuck. Then resume and the login screen appears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-03 Thread Sebastian
The same issue on Lenovo M30-70. I run Linux Mint 19 (cinnamon) parallelly on the same notebook. After upgrade to kernel 4.15.0-24 it hangs too. But here it boots with a prior kernel without problems and I turned off the upgrade to 4.15.0-24. -- You received this bug notification because you

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-03 Thread Frank
Ctrl-Alt-F1 repeatingly if the prompt dies. Updated all third party apps to newest versions. Took a look at the boot.log Made me run these: sudo apt-get install --reinstall apparmor systemctl start nmbd.service It boots on 24 kernel. Very fast suspiciously fast. Boot.log looks good. Until now it

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-03 Thread perry
Interesting thing happening... I tried booting 0-23 success, then did shutdown -r now, and tried booting 0-24, as noted above just hangs. Briefly hit power button tried to boot 0-23 again and now it doesn't boot... Tried turning off power and then booting 0-23, still hangs, got "Started GNOME

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-03 Thread perry
Agreed, I see the same thing. Glad 0-23 boots, but 0-24 still hangs at the Ubuntu logo, five white dots, not animated. -- 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/1779827 Title:

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-03 Thread perry
Me either. The booting to prior kernel does not fix the issue. Glad to help test but need some instructions. Only have non-bootable system at this point. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-03 Thread Alexander Zeitler
For me, booting into previous kernel versions did not fix it. (DELL) -- 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/1779827 Title: failure to boot with linux-image-4.15.0-24-generic

  1   2   >