bartk
April 18, 2024, 8:49am
1
I recently updated kernel to kernel-default-6.8.6-1.1
on my openSUSE Tumbleweed KDE 6 [Wayland] and had to revert previous one snapshot .
The system hangs during the boot process. After selecting the OS in the GRUB menu and removing “splash=silent quiet” from GRUB_CMDLINE_LINUX_DEFAULT
, it still stalls at a specific point, which I’ve captured in an attached photo.
openSUSE Paste - results of the inxi -Faz
command after reverting snapshot.
I would greatly appreciate any advice or suggestions on what might be causing this issue and how to resolve it. If anyone has encountered a similar problem or knows any potential fixes, please share your insights.
Thank you in advance for your help!
mburge
April 18, 2024, 10:03am
2
Looks like a recently introduced bug
Likely introduced in 6.8.5 by one or more of the following (3) commits
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-6.8.y&qt=grep&q=e1000e
On the Internet:
https://bbs.archlinux.org/viewtopic.php?id=294828
Hi all, Been a happy Manjaro user for many years now - running on a Thinkpad X1 Carbon Gen6. Many thanks to all those who work on this distro! However, since the most recent kernel updates (I have tried both 6.8.5-1 and 6.6.26-1 LTS), I have been...
Reading time: 5 mins 🕑
Likes: 1 ❤
I would recommend filing an issue here:
https://bugzilla.suse.com/
I suggest https://bugzilla.opensuse.org/ if a bug report is needed for filing an openSUSE Tumbleweed bug.
I have the exact same GPU, and no apparent trouble with LT kernel:
# inxi -SGaz --vs --zl --hostname
inxi 3.3.34-00 (2024-04-13)
System:
Host: p5bse Kernel: 6.6.27-1-longterm arch: x86_64 bits: 64 compiler: gcc
v: 13.2.1 clocksource: tsc avail: hpet,acpi_pm
parameters: root=LABEL=<filter> ipv6.disable=1 net.ifnames=0 noresume
consoleblank=0 mitigations=off
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 info: frameworks
v: 5.114.0 wm: kwin_x11 vt: 7 dm: SDDM Distro: openSUSE Tumbleweed 20240416
Graphics:
Device-1: NVIDIA GF119 [NVS 310] vendor: Hewlett-Packard driver: nouveau
v: kernel non-free: series: 390.xx+ status: legacy (EOL~2022-11-22) last:
release: 390.157 kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx
process: 40/28nm built: 2010-2016 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
ports: active: DP-1,DP-2 empty: none bus-ID: 01:00.0 chip-ID: 10de:107d
class-ID: 0300 temp: 48.0 C
Display: x11 server: X.Org v: 21.1.12 compositor: kwin_x11 driver: X:
loaded: modesetting dri: nouveau gpu: nouveau display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x2490 s-dpi: 120 s-size: 541x527mm (21.30x20.75")
s-diag: 755mm (29.73")
Monitor-1: DP-1 pos: primary,bottom model: Acer K272HUL serial: <filter>
built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
Monitor-2: DP-2 pos: top model: Dell P2213 serial: <filter> built: 2012
res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
drv: nouveau inactive: wayland
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.0.3 glx-v: 1.4
direct-render: yes renderer: NVD9 device-ID: 10de:107d memory: 474.6 MiB
unified: no
API: Vulkan v: 1.3.280 layers: 2 device: 0 type: cpu name: llvmpipe (LLVM
18.1.3 128 bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
# inxi -Cnz
CPU:
Info: dual core model: Intel Core2 Duo E7500 bits: 64 type: MCP cache:
L2: 3 MiB
Speed (MHz): avg: 1596 min/max: 1596/2926 cores: 1: 1596 2: 1596
Network:
Device-1: Qualcomm Atheros Attansic L1 Gigabit Ethernet driver: atl1
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
#
bartk
April 19, 2024, 7:08am
4
Thank you, I’ve filed the issue on openSUSE’s BugZilla
bartk
April 20, 2024, 11:40am
6
Thanks
So it seems that I need to wait for the problem to be resolved and for a patch to appear in Factory?
Yes, you should wait for a kernel update upstream. Meanwhile you may temporarily lock the 6.8.4 kernel so you can receive system updates (less the kernel) until the problem is solved.