|
5.0.0-8.1 (and 5.0.0-9.1) won't boot, 5.0.0-7.1 and earlier work fine
After updating to 5.0.0-8.1-liquorix-amd64 I entirely cannot boot the system with this kernel (and also with 5.0.0-9.1-liquorix-amd64)
It hangs after loading the kernel ramdisk: :: Code :: Loading Linux 5.0.0-8.1-liquorix-amd64 ...
Loading initial ramdisk ... I have the same problem with the next 5.0.0-9.1-liquorix-amd64 kermel. 5.0.0-7.1-liquorix-amd64 and all previous releases work absolutely fine. The problem occurs only on my main PC (inxi -b below). 5.0.0-8.1 and 5.0.0-9.1 work fine on my laptop and other (quite old) PC. All running Ubuntu 18.10 and configured the same way (GRUB config and kernel parameters are identical). inxi -b: :: Code :: System: Host: phd Kernel: 5.0.0-7.1-liquorix-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.15.3
Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Desktop Mobo: MSI model: Z170A-G43 PLUS (MS-7970) v: 1.0 serial: F916624488 UEFI [Legacy]: American Megatrends v: 3.20 date: 11/03/2015 CPU: Quad Core: Intel Core i5-6600K type: MCP speed: 1547 MHz min/max: 800/3900 MHz Graphics: Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 418.56 Display: x11 server: X.Org 1.20.1 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 418.56 Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Drives: Local Storage: total: 2.63 TiB used: 836.38 GiB (31.1%) Info: Processes: 270 Uptime: 12h 58m Memory: 15.63 GiB used: 2.51 GiB (16.1%) Shell: bash inxi: 3.0.24 Back to top |
|||||
|
Seeing the same...kinda..
Well at first I thought it was stuck too, but today after updating to 5.0.0-9.1 I saw that I've rebooted the machine and forgot about the issue, but it was working. Basically it will take about 45seconds after loading the kernel to light up the keyboard then another 15 to continue. @phd: If you wait 2 mins, it will not start?[/code] Back to top |
|||||
|
@Licaon_kter
I just tested it (using 5.0.0-9.1). I waited 4 minutes and gave up. Neither the keyboard lighted up nor it continued. I'm stuck with 5.0.0-7.1 for now. Back to top |
|||||
|
Hmm, this is definitely unusual, because the change that appears to exhibiting these symptoms is using the default configuration of MuQSS (multicore sibling runqueue sharing), where 5.0.7 and previous releases used SMT queue sharing (one queue per core).
I'll revert the change tonight and hopefully that'll fix your boot problems. If not, then we have something that got into 5.0.8 that's affecting some system configurations. Back to top |
|||||
|
Thank you. I will test the reverted version as soon as it is available and report the results here.
Also I forgot one difference between my computers that possibly may matter. My main PC uses nVidia proprietary drivers (418.56), while the other PC and laptop also have nVidia GPUs, but they use the nouveau driver. Back to top |
|||||
|
|
|||||
|
:: Quote :: I'm on nVIdia too, 430.09I'm curious what MuQSS vs SMT has to do with it. I will install 5.0.0-9.2 later today and let know here if it fixed the problem for me. Back to top |
|||||
|
|
|||||
|
That's good news! I'll give this feedback to Con, hopefully he might have an idea what might cause boot issues on shared runqueues.
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||