Exactly like in the subject. Slackware64 15.0 Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Exactly just like in the case of 4.19.304/305 the kernel file (when compiled for 64 bit) gained large „bss” section: size: vmlinuz-4.14.336-i7: warning: ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss text data bss dec hex filename 7745760 0 23092512 30838272 1d68e00 vmlinuz-4.14.336-i7
4.14 is EOL so I'm not sure how much support you'll get for it. Can you confirm that if you jump back into 4.19 it will boot? You might also want to check your bootloader cfg and kernel params. There's also a chance it might be an issue with Slackware user space. It might be worth trying an older image of Slackware (or another distro) that natively uses 4.14 (live USB should make this easy). That way we can isolate the problem to the kernel itself rather than any sort of cfg/user space issue.
1. No problem; here are a few lines from my past 'messages' log: May 15 16:07:49 Gigacyan kernel: usb usb1: Product: EHCI Host Controller May 15 16:07:49 Gigacyan kernel: usb usb1: Manufacturer: Linux 4.19.282-i7 ehci_hcd May 15 16:07:49 Gigacyan kernel: usb usb1: SerialNumber: 0000:00:1a.0 May 15 16:07:49 Gigacyan kernel: hub 1-0:1.0: USB hub found May 15 16:07:49 Gigacyan kernel: hub 1-0:1.0: 2 ports detected May 15 16:07:49 Gigacyan kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller May 15 16:07:49 Gigacyan kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 May 15 16:07:49 Gigacyan kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000000009810 May 15 16:07:49 Gigacyan kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 May 15 16:07:49 Gigacyan kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 May 15 16:07:49 Gigacyan kernel: usb usb2: Product: xHCI Host Controller May 15 16:07:49 Gigacyan kernel: usb usb2: Manufacturer: Linux 4.19.282-i7 xhci-hcd May 15 16:07:49 Gigacyan kernel: usb usb2: SerialNumber: 0000:00:14.0 May 15 16:07:49 Gigacyan kernel: hub 2-0:1.0: USB hub found May 15 16:07:49 Gigacyan kernel: hub 2-0:1.0: 14 ports detected May 15 16:07:50 Gigacyan kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller May 15 16:07:50 Gigacyan kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 3 May 15 16:07:50 Gigacyan kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller May 15 16:07:50 Gigacyan kernel: ehci-pci 0000:00:1d.0: debug port 2 May 15 16:07:50 Gigacyan kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4 May 15 16:07:50 Gigacyan kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed May 15 16:07:50 Gigacyan kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 May 15 16:07:50 Gigacyan kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 May 15 16:07:50 Gigacyan kernel: usb usb4: Product: xHCI Host Controller May 15 16:07:50 Gigacyan kernel: usb usb4: Manufacturer: Linux 4.19.282-i7 xhci-hcd May 15 16:07:50 Gigacyan kernel: usb usb4: SerialNumber: 0000:00:14.0 May 15 16:07:50 Gigacyan kernel: hub 4-0:1.0: USB hub found May 15 16:07:50 Gigacyan kernel: hub 4-0:1.0: 6 ports detected May 15 16:07:50 Gigacyan kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7f16000 May 15 16:07:50 Gigacyan kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00 May 15 16:07:50 Gigacyan kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 May 15 16:07:50 Gigacyan kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 May 15 16:07:50 Gigacyan kernel: usb usb3: Product: EHCI Host Controller May 15 16:07:50 Gigacyan kernel: usb usb3: Manufacturer: Linux 4.19.282-i7 ehci_hcd May 15 16:07:50 Gigacyan kernel: usb usb3: SerialNumber: 0000:00:1d.0 May 15 16:07:50 Gigacyan kernel: hub 3-0:1.0: USB hub found May 15 16:07:50 Gigacyan kernel: hub 3-0:1.0: 2 ports detected May 15 16:07:50 Gigacyan kernel: AVX2 version of gcm_enc/dec engaged. 4.19.282 was bootable; somewhere later some smart guy screwed up (probably) the SATA driver, also in 4.14 and 5.4 lines. And what about that BSS? Why it appeared in 64-bit kernels out of the blue? „Note that the BSS segment is not stored in the kernel image because it can be synthesized at boot time by filling a block of memory with zeros.” — don't you know? 2. 4.14.x is a „longterm” kernel, not EOL, from what I see on kernel.org page: longterm: 5.4.267 2024-01-15 [tarball] [pgp] [patch] [inc. patch] [view diff] [browse] [changelog] longterm: 4.19.305 2024-01-15 [tarball] [pgp] [patch] [inc. patch] [view diff] [browse] [changelog] longterm: 4.14.336 [EOL] 2024-01-10 [tarball] [pgp] [patch] [inc. patch] [view diff] [browse] [changelog] linux-next: next-20240122 2024-01-22 [browse] Anyway that smart man, who was talented enough to screw up these 3 kernel lines, should now fix them back IMHO. 3. …and no, it's not about just me; it's about whole Linux users' society.
There's no need for duplicates. *** This bug has been marked as a duplicate of bug 218380 ***
Created attachment 305757 [details] kernel config file Attaching the kernel config file