Latest Upgrade bricked Zen Kernel

Issues & Assistance
1 
System:
Kernel: 6.0.0-rc7-1-mainline arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-mainline
root=UUID=4f3937b5-6c07-4580-8883-8cef1f42d4f5 rw [email protected] quiet
cryptdevice=UUID=3d769afd-2828-481c-8e36-8aba99397d5a:luks-3d769afd-2828-481c-8e36-8aba99397d5a
root=/dev/mapper/luks-3d769afd-2828-481c-8e36-8aba99397d5a quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0
resume=/dev/mapper/luks-a59fcb28-cd12-4a13-abcf-1ad9ee0585a5 loglevel=3
Console: pty pts/1 DM: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: Framework product: Laptop v: AB serial: <filter>
Mobo: Framework model: FRANBMCP0B v: AB serial: <filter> UEFI: INSYDE v: 03.07
date: 12/14/2021
Battery:
ID-1: BAT1 charge: 53.3 Wh (100.0%) condition: 53.3/55.0 Wh (96.9%) volts: 17.6 min: 15.4
model: NVT Framewo type: Li-ion serial: <filter> status: discharging
CPU:
Info: model: 11th Gen Intel Core i7-1165G7 socket: U3E1 bits: 64 type: MT MCP arch: Tiger Lake
gen: core 11 level: v4 built: 2020 process: Intel 10nm family: 6 model-id: 0x8C (140)
stepping: 1 microcode: 0xA4
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 320 KiB desc: d-4x48
KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 2581 high: 2800 min/max: 400/4700 base/boost: 2800/4700 scaling:
driver: intel_pstate governor: powersave volts: 0.8 V ext-clock: 100 MHz cores: 1: 2800 2: 2800
3: 1050 4: 2800 5: 2800 6: 2800 7: 2800 8: 2800 bogomips: 44864
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW
sequence
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel arch: Gen-12.1
process: Intel 10nm built: 2020-21 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4
bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
Display: x11 server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 compositor: kwin_x11 driver:
X: loaded: modesetting alternate: fbdev,intel,vesa gpu: i915 tty: 297x85
Monitor-1: eDP-1 model: BOE Display 0x095f built: 2019 res: 2256x1504 dpi: 201 gamma: 1.2
size: 285x190mm (11.22x7.48") diag: 343mm (13.5") ratio: 3:2 modes: 2256x1504
Message: GL data unavailable in console for root.
Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel v: kernel
alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:a0c8 class-ID: 0403
Sound Server-1: ALSA v: k6.0.0-rc7-1-mainline running: yes
Sound Server-2: PulseAudio v: 16.1 running: no
Sound Server-3: PipeWire v: 0.3.58 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: aa:00.0 chip-ID: 8086:2725 class-ID: 0280
IF: wlp170s0 state: up mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-10:4
chip-ID: 8087:0032 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address: <filter>
Drives:
Local Storage: total: 931.51 GiB used: 105.73 GiB (11.4%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B2QGXA7 temp: 41.9 C scheme: GPT
SMART: yes health: PASSED on: 20 hrs cycles: 67 read-units: 1,533,527 [785 GB]
written-units: 1,188,112 [608 GB]
Partition:
ID-1: / raw-size: 896.96 GiB size: 896.96 GiB (100.00%) used: 105.73 GiB (11.8%) fs: btrfs
block-size: 4096 B dev: /dev/dm-0 maj-min: 254:0
mapped: luks-3d769afd-2828-481c-8e36-8aba99397d5a
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 720 KiB (0.2%) fs: vfat
block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 896.96 GiB size: 896.96 GiB (100.00%) used: 105.73 GiB (11.8%)
fs: btrfs block-size: 4096 B dev: /dev/dm-0 maj-min: 254:0
mapped: luks-3d769afd-2828-481c-8e36-8aba99397d5a
ID-4: /var/log raw-size: 896.96 GiB size: 896.96 GiB (100.00%) used: 105.73 GiB (11.8%)
fs: btrfs block-size: 4096 B dev: /dev/dm-0 maj-min: 254:0
mapped: luks-3d769afd-2828-481c-8e36-8aba99397d5a
ID-5: /var/tmp raw-size: 896.96 GiB size: 896.96 GiB (100.00%) used: 105.73 GiB (11.8%)
fs: btrfs block-size: 4096 B dev: /dev/dm-0 maj-min: 254:0
mapped: luks-3d769afd-2828-481c-8e36-8aba99397d5a
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.14 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.25 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-1
maj-min: 254:1 mapped: luks-a59fcb28-cd12-4a13-abcf-1ad9ee0585a5
Sensors:
System Temperatures: cpu: 41.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 341 Uptime: 16m wakeups: 2465 Memory: 31.14 GiB used: 7.33 GiB (23.5%) Init: systemd
v: 251 default: graphical tool: systemctl Compilers: gcc: 12.2.0 Packages: pm: pacman
pkgs: 1612 libs: 359 tools: octopi,pamac,paru,yay Shell: Bash v: 5.1.16 running-in: pty pts/1
inxi: 3.3.21
Garuda (2.6.8-1):
System install date:     2022-05-10
Last full system update: 2022-10-04
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:
  1. good news I could restore the snapshot, still awesome feature and one my favorites
  2. I did the garuda-update again to see if it was only a temporary issue, but same issue
  3. Good news is that the 6.0.0-rc7-1-mainline Kernel is working as intended

Should I restore the snapshot and simply wait for a Zen update or is this not connected to each other?

Right now I am glad I have two option Mainline Kernel or Restore snapshot.
But what would be recommended?

2 Likes
2

Unless you encounter bugginess or broken features on the RC kernel, I would just stick with that (that's what is on my FW laptop at the moment as well). That way you can keep up with your updates.

If you have any problems on the RC kernel, another option is running LTS for the next few days until the Zen kernel takes 6.0. This would also enable you to keep your packages up to date, etc.

There isn't a tremendous amount of risk in rolling back to the snapshot and just not updating your packages for a while, but it you want to keep updating just use a different kernel.

3 Likes
3

This combination is known to be broken with latest 5.19 kernel. Stay on 6.0

5 Likes
4

Thanks for the information! @mrvictory and @BluishHumility
But kinda strange, I was running the Zen Kernel all the time on my Framework.
Ah the wording, the latest 5.19, gotcha.
:man_shrugging: Mainline it is then :slight_smile:

5

It's not specifically the Zen kernel, it is the 5.19.12 kernel. Other 5.19.12 kernels like linux will break the display in the same way.

If you feel like hacking around a bit, this thread has a few interesting workarounds. Some folks have been able to get back into their systems on the 5.19.12 kernel by blacklisting the i915 module for example. It also appears certain kinds of externally connected displays may still allow for login.

4 Likes
6

No time for tinkering, gotta work :wink: I will stay on the 6.0 kernel.
But thanks for the information, will check it out anyway.

1 Like
7
3 Likes
8

This should be fixed now in 5.19.13!

"This release is to resolve a regression on some Intel graphics systems that had problems with 5.19.12. If you do not have this problem with 5.19.12, there is no need to upgrade."

https://lwn.net/Articles/910314/

4 Likes
9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.