_dunce
20 November 2024 00:40
1
Been struggling to diagnose and fix kernel panic on an X1 Carbon 6th gen for over 6 months. Difficult to reproduce consistently, however symptoms tend to involve the system going to sleep or the power being unplugged. On several occasions I have unplugged the machine from power (whilst fully charged) and it has instantly gone into panic (flashing capslock light). On other occasions Iβve left the machine on without closing the lid for long periods (overnight) and have been unable to get back in (completely frozen and stuck on login screen). REISUB only seems to work if I catch it whilst the panic is happening - whenever Iβve come back to a frozen machine (e.g. closed the lid with power plugged) there is no response to REISUB.
Iβll add that the machine is capable to run for several hours without being plugged in so I donβt suspect the battery of being completely shot.
I did follow through this semi-recent post from another user with the same 6th gen carbon model: X1 Carbon 6th Gen - Kernel Panics and Lock-ups . Some of the issues described there are similar to mine, but not exactly. This thread also seems to have had no conclusion.
There is also mention of βsystem freeze on suspendβ in the announcements: [Stable Update] 2024-10-10 - Kernels, Pacman 7.0, KDE Frameworks 6.6, Virtualbox 7.1.2, Mesa - #2 by philm . But the symptom of βSystem freezes for 60 seconds and then wakes back up or hangs after waking upβ is really not related.
Output of inxi -xG
:
Graphics:
Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel
arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Bison Integrated Camera driver: uvcvideo type: USB bus-ID: 1-8:3
Display: x11 server: X.Org v: 21.1.14 driver: X: loaded: modesetting
dri: iris gpu: i915 resolution: 2560x1440~60Hz
API: EGL v: 1.5 drivers: iris,swrast platforms:
active: gbm,x11,surfaceless,device inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.4-arch1.0.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 620 (KBL
GT2)
Output of journalctl -b0 -p4 --no-pager
immediately after hard rebooting from a freeze/panic:
kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
kernel: hpet_acpi_add: no address or irqs in _CRS
kernel: systemd[1]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
kernel: kauditd_printk_skb: 34 callbacks suppressed
systemd-journald[301]: File /var/log/journal/50e1c05924bc4a11a1c7a0373b036708/system.journal corrupted or uncleanly shut down, renaming and replacing.
kernel: resource: resource sanity check: requesting [mem 0x00000000fed10000-0x00000000fed15fff], which spans more than pnp 00:07 [mem 0xfed10000-0xfed13fff]
kernel: caller snb_uncore_imc_init_box+0x87/0xe0 [intel_uncore] mapping multiple BARs
systemd-vconsole-setup[600]: /usr/bin/loadkeys failed with exit status 1.
systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Virtual Console Setup.
kernel: thermal thermal_zone5: failed to read out thermal zone (-61)
avahi-daemon[724]: Failed to parse address '', ignoring.
(uetoothd)[1083]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support bap plugin
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support bass plugin
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support mcp plugin
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support vcp plugin
bluetoothd[1083]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support micp plugin
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support ccp plugin
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support csip plugin
bluetoothd[1083]: src/plugin.c:init_plugin() System does not support asha plugin
kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
kernel: Bluetooth: hci0: Reading supported features failed (-16)
kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
dbus-broker-launch[681]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
dbus-broker-launch[1449]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
dbus-broker-launch[1449]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
dbus-broker-launch[1449]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service'
dbus-broker-launch[1449]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifyd.service' is not named after the D-Bus name 'org.xfce.Notifyd'.
dbus-broker-launch[681]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.
lightdm[1503]: gkr-pam: unable to locate daemon control file
dbus-broker-launch[1561]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
dbus-broker-launch[1561]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
dbus-broker-launch[1561]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service'
dbus-broker-launch[1561]: Service file '/usr/share//dbus-1/services/org.xfce.xfce4-notifyd.Notifyd.service' is not named after the D-Bus name 'org.xfce.Notifyd'.
Currently using linux66
kernel. Have tried 515 and others without any change.
cscs
20 November 2024 01:12
2
_dunce:
Output of inxi -xG
:
This is insufficient.
Please provide
inxi -Farz
_dunce:
sleep
Have you checked the sleep mode set in BIOS?
We cant see it currently (better inxi would show) but your BIOS should be up to date, and if it is, there should be a βLinuxβ sleep state option available in BIOS. This should be selected over other options like βWindows 10β.
For more information, including how to upgrade your BIOS and other troubleshooting, see the dedicated Archwiki page:
https://wiki.archlinux.org/title/Lenovo_ThinkPad_X1_Carbon_(Gen_6)
_dunce
20 November 2024 02:15
3
Rightβ¦ Thatβd probably do the trick. Unfortunately, after installing and running fwupdmgr update
(fwupd - ArchWiki ) I land here: System and ME firmware fail to update on Lenovo t480s Β· Issue #201 Β· fwupd/firmware-lenovo Β· GitHub . That issue is seemingly solved by a manual install of a .cab file that was privately shared?? As per the manual update instructions (Lenovo ThinkPad X1 Carbon (Gen 6) - ArchWiki ) the Lenovo website (laptops and netbooks :: thinkpad x series laptops :: thinkpad x1 carbon 6th gen type 20kh 20kgcontentdetail - Lenovo Support FR ) offers various drivers - what am I aiming for here? BIOS/UEFI?
Thanks!
inxi -Farz
:
System:
Kernel: 6.6.54-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
root=UUID=d7a34cd6-b506-4046-8f87-2f88ba3da3f7 rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: i3 v: 4.23 with: i3bar tools: xautolock avail: i3lock vt: 7
dm: LightDM v: 1.32.0 Distro: Manjaro base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 20KHA01CAU v: ThinkPad X1 Carbon 6th
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20KHA01CAU v: SDK0J40697 WIN
serial: <superuser required> part-nu: LENOVO_MT_20KH_BU_Think_FM_ThinkPad
X1 Carbon 6th uuid: <superuser required> UEFI: LENOVO v: N23ET50W (1.25 )
date: 06/25/2018
Battery:
ID-1: BAT0 charge: 20.1 Wh (96.6%) condition: 20.8/57.0 Wh (36.4%)
volts: 12.4 min: 11.6 model: LGC 01AV494 type: Li-poly serial: <filter>
status: not charging cycles: 584
CPU:
Info: model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Coffee Lake
gen: core 8 level: v3 note: check built: 2017 process: Intel 14nm family: 6
model-id: 0x8E (142) stepping: 0xA (10) microcode: 0xF6
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 400/3400 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 bogomips: 28808
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow 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: IBRS; IBPB: conditional; STIBP: conditional;
RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5917
class-ID: 0300
Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 5986:2115
class-ID: 0e02
Display: x11 server: X.Org v: 21.1.14 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
s-diag: 777mm (30.58")
Monitor-1: eDP-1 model: LG Display 0x058b built: 2016 res: 2560x1440
hz: 60 dpi: 210 gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14")
ratio: 16:9 modes: 2560x1440
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.4-arch1.0.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 620 (KBL
GT2) device-ID: 8086:5917 memory: 3.67 GiB unified: yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_soc_avs
bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
API: ALSA v: k6.6.54-2-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.2.5 status: off tools: pw-cli
Server-3: PulseAudio v: 17.0 status: active with: 1: pulseaudio-alsa
type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl,pavucontrol
Network:
Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 class-ID: 0200
IF: enp0s31f6 state: down mac: <filter>
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24fd
class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
IF-ID-1: wwan0 state: down mac: N/A
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:2 chip-ID: 8087:0a2b
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 4.2
lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 238.47 GiB used: 109.43 GiB (45.9%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLB256HAHQ-000L7 size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 1L2QEXD7 temp: 36.9 C scheme: GPT
Partition:
ID-1: / raw-size: 238.17 GiB size: 233.38 GiB (97.99%)
used: 109.42 GiB (46.9%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 11.5 MiB (3.8%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 46.0 C pch: 47.0 C mobo: N/A
Fan Speeds (rpm): fan-1: 0
Repos:
Packages: pm: pacman pkgs: 1728 libs: 459 tools: pamac,yay
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
2: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
3: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
4: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
5: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
6: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
7: https://mirror.zetup.net/manjaro/stable/$repo/$arch
8: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
Info:
Memory: total: 8 GiB note: est. available: 7.52 GiB used: 5.1 GiB (67.8%)
Processes: 228 Power: uptime: 30m states: freeze,mem,disk suspend: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 3 GiB services: upowerd,xfce4-power-manager Init: systemd v: 256
default: graphical tool: systemctl
Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Bash v: 5.2.37 running-in: st
inxi: 3.3.36
cscs
20 November 2024 02:41
4
Can you please reference this related issue/post;
opened 09:41PM - 09 Nov 22 UTC
closed 09:35PM - 23 Jan 23 UTC
bug
**Describe the bug**
I got two updates to be applied: Embedded Controller and U⦠EFI dbx. Updates are downloaded and after reboot of the machine I get an error that ends with: "ERROR 105 - command line error!".
**Steps to Reproduce**
1. Run `sudo fwupdmgr update`
2. Accept all questions with Yes.
3. Reboot
4. First got:
```
fwupd-efi version 1.3
```
5. After few seconds followed by:
```
SCT Flash Utility for Lenovo
for Shell V1.0.3.9
Copyright (c) 2011-2017 Phoenix Technologies Ltd.
Copyright (c) 2011-2017 Lenovo Group Limited.
Usage: ShellFlash64 [COMMAND]...
Try 'ShellFlash64 -help' for more commands.
ERROR 105 - Command line error!
Reset System
```
6. And system is reset.
7. Another run of the command from first point gives me same pending updates.
8. Additionally I ran `sudo fwupdmgr get-updates` and got following output:
```
Devices with no available firmware updates:
β’ MZVLW256HEHP-000L7
β’ UEFI Device Firmware
Devices with the latest available firmware version:
β’ Embedded Controller
β’ UEFI dbx
________________________________________________
Devices that were not updated correctly:
β’ Intel Management Engine (184.83.3874 β 184.92.4222)
β’ System Firmware (0.1.41 β 0.1.46)
```
**Expected behavior**
No error, after a reboot change in pending updates or no pending updates.
**fwupd version information**
Please provide the version of the daemon and client.
```shell
fwupdmgr --version
runtime org.freedesktop.fwupd 1.8.6
runtime org.freedesktop.fwupd-efi 1.3
compile org.freedesktop.gusb 0.3.10
runtime com.hughsie.libjcat 0.1.12
compile com.hughsie.libjcat 0.1.12
runtime com.dell.libsmbios 2.4
runtime org.kernel 6.0.5-200.fc36.x86_64
compile org.freedesktop.fwupd 1.8.6
runtime org.freedesktop.gusb 0.3.10
```
Please note how you installed it (`apt`, `dnf`, `pacman`, source, etc):
<details>
`dnf`
<summary>**fwupd device information**</summary>
Please provide the output of the fwupd devices recognized in your system.
```shell
fwupdmgr get-devices --show-all-devices
LENOVO 20HMS1FC02
β
ββCoreβ’ i5-7300U CPU @ 2.60GHz:
β Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
β Current version: 0x000000f0
β Vendor: Intel
β GUIDs: b9a2dd81-159e-5537-a7db-e7101d164d3f β cpu
β 30249f37-d140-5d3e-9319-186b1bd5cac3 β CPUID\PRO_0&FAM_06
β 561403e8-143a-5071-ab09-bf5e4c146983 β CPUID\PRO_0&FAM_06&MOD_8E
β 9ca69899-3716-5857-9fd3-882a5c73236f β CPUID\PRO_0&FAM_06&MOD_8E&STP_9
β Device Flags: β’ Internal device
β
ββEmbedded Controller:
β Device ID: 2292ae5236790b47884e37cf162dcf23bfcd1c60
β Summary: UEFI ESRT device
β Current version: 0.1.18
β Minimum Version: 0.0.1
β Vendor: Lenovo (DMI:LENOVO)
β Update State: Success
β GUID: 18dfeb28-b8a4-4cec-97ce-b0599416a13e
β Device Flags: β’ Internal device
β β’ Updatable
β β’ System requires external power source
β β’ Supported on remote server
β β’ Needs a reboot after installation
β β’ Device is usable for the duration of the update
β
ββHD Graphics 620:
β Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a
β Current version: 02
β Vendor: Intel Corporation (PCI:0x8086)
β GUIDs: 38f6c009-a25c-5b50-b3b5-fef4f9c6b846 β PCI\VEN_8086&DEV_5916
β 2886e312-afd8-5510-8993-12d568a85e00 β PCI\VEN_8086&DEV_5916&REV_02
β e2ca3845-d5e6-5f0e-ac28-742089fd2826 β PCI\VEN_8086&DEV_5916&SUBSYS_17AA5062
β ff970320-b0e8-5948-9ee7-4420857dc4f5 β PCI\VEN_8086&DEV_5916&SUBSYS_17AA5062&REV_02
β 52754615-939c-53cf-86f9-3b9ef9be0c25 β PCI\VEN_8086&DEV_5916&REV_00
β 41ecf469-c522-5334-8136-d64fbc0b0cc0 β PCI\VEN_8086&DEV_5916&SUBSYS_17AA5062&REV_00
β Device Flags: β’ Internal device
β β’ Cryptographic hash verification is available
β
ββIntel Management Engine:
β Device ID: 349bb341230b1a86e5effe7dfe4337e1590227bd
β Summary: UEFI ESRT device
β Current version: 184.83.3874
β Minimum Version: 184.83.3874
β Vendor: Lenovo (DMI:LENOVO)
β Update State: Success
β GUID: 9a7f2771-7ce4-4ff1-892b-c2ed700b77de
β Device Flags: β’ Internal device
β β’ Updatable
β β’ System requires external power source
β β’ Supported on remote server
β β’ Needs a reboot after installation
β β’ Device is usable for the duration of the update
β
ββMZVLW256HEHP-000L7:
β Device ID: 04e17fcf7d3de91da49a163ffe4907855c3648be
β Summary: NVM Express solid state drive
β Current version: 4L7QCXB7
β Vendor: Samsung (NVME:0x144D)
β Serial Number: 8<REDACTED>8
β GUIDs: 5b3df2da-f745-5fd0-81de-5dafd7f0bf8c β NVME\VEN_144D&DEV_A804
β f87b9ac8-1cb3-5c0a-ae57-7144f211fe5e β NVME\VEN_144D&DEV_A804&REV_00
β aed4d3c0-fd97-5e46-a32f-ff35e0692f6d β NVME\VEN_144D&DEV_A804&SUBSYS_144DA801
β 030c853f-259a-57a0-b3fb-1c66100db94b β NVME\VEN_144D&DEV_A804&SUBSYS_144DA801&REV_00
β 257d6faa-82f3-53e2-afa4-f6b9adc9595d β SAMSUNG MZVLW256HEHP-000L7
β Device Flags: β’ Internal device
β β’ Updatable
β β’ System requires external power source
β β’ Needs a reboot after installation
β β’ Device is usable for the duration of the update
β β’ Signed Payload
β
ββSystem Firmware:
β β Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f
β β Summary: UEFI ESRT device
β β Current version: 0.1.41
β β Minimum Version: 0.1.10
β β Vendor: Lenovo (DMI:LENOVO)
β β Update State: Success
β β GUIDs: 14cc970e-c105-4eba-a704-448dde9de64d
β β 230c8b18-8d9b-53ec-838b-6cfc0383493a β main-system-firmware
β β Device Flags: β’ Internal device
β β β’ Updatable
β β β’ System requires external power source
β β β’ Supported on remote server
β β β’ Needs a reboot after installation
β β β’ Cryptographic hash verification is available
β β β’ Device is usable for the duration of the update
β β β’ Full disk encryption secrets may be invalidated when updating
β β
β ββAMT [unprovisioned]:
β β Device ID: 5fed1486be004d67ea79838d2e83aaa11bb72645
β β Summary: Hardware and firmware technology for remote out-of-band management
β β Current version: 11.8.92.4222
β β Bootloader Version:11.8.92.4222
β β Vendor: Intel Corporation (MEI:0x8086)
β β GUIDs: 2800f812-b7b4-2d4b-aca8-46e0ff65814c
β β 73873541-e967-5a4f-aeb4-22d1901fc940 β MEI\VEN_8086&DEV_9D3A
β β a2ca5cb3-f89c-53a6-93eb-bc03acbd17e0 β MEI\VEN_8086&DEV_9D3A&REV_21
β β 9987c7e8-0e61-53a9-9577-7384ce069f8f β MEI\VEN_8086&DEV_9D3A&SUBSYS_17AA5062
β β 0696c82c-d15e-5484-803e-23ea363e1d4c β MEI\VEN_8086&DEV_9D3A&SUBSYS_17AA5062&REV_21
β β Device Flags: β’ Internal device
β β
β ββUEFI dbx:
β Device ID: 362301da643102b9f38477387e2193e57abaa590
β Summary: UEFI revocation database
β Current version: 217
β Minimum Version: 217
β Vendor: UEFI:Linux Foundation
β Install Duration: 1 second
β GUIDs: 14503b3d-73ce-5d06-8137-77c68972a341 β UEFI\CRT_A9087D1044AD18F7A94916D284CBC01827CF23CD8F60B79072C9CAA1FEF4D649
β 5971a208-da00-5fce-b5f5-1234342f9cf7 β UEFI\CRT_A9087D1044AD18F7A94916D284CBC01827CF23CD8F60B79072C9CAA1FEF4D649&ARCH_X64
β c6682ade-b5ec-57c4-b687-676351208742 β UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503
β f8ba2887-9411-5c36-9cee-88995bb39731 β UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
β Device Flags: β’ Internal device
β β’ Updatable
β β’ Supported on remote server
β β’ Needs a reboot after installation
β β’ Device is usable for the duration of the update
β β’ Only version upgrades are allowed
β β’ Signed Payload
β
ββTPM:
β Device ID: c6a80ac3a22083423992a3cb15018989f37834d6
β Current version: 71.12.17568.4100
β Vendor: ST Microelectronics (TPM:STM)
β GUIDs: ff71992e-52f7-5eea-94ef-883e56e034c6 β system-tpm
β 84df3581-f896-54d2-bd1a-372602f04c32 β TPM\VEN_STM&DEV_0001
β bfaed10a-bbc1-525b-a329-35da2f63e918 β TPM\VEN_STM&MOD_
β 70b7b833-7e1a-550a-a291-b94a12d0f319 β TPM\VEN_STM&DEV_0001&VER_2.0
β 06f005e9-cb62-5d1a-82d9-13c534c53c48 β TPM\VEN_STM&MOD_&VER_2.0
β Device Flags: β’ Internal device
β
ββUEFI Device Firmware:
Device ID: f95c9218acd12697af946874bfe4239587209232
Summary: UEFI ESRT device
Current version: 4653068
Minimum Version: 4653068
Vendor: DMI:LENOVO
Update State: Success
GUID: c6dcc084-522b-45ff-a294-6d660bb228fc
Device Flags: β’ Internal device
β’ Updatable
β’ System requires external power source
β’ Needs a reboot after installation
β’ Device is usable for the duration of the update
```
</details>
**System UEFI configuration**
Please provide the output of the following commands:
```shell
efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0017,0018,001A,001B,001C,001D,0019,0001
Boot0000* Fedora HD(1,GPT,ae17a681-33c0-4384-838f-6358c26959bd,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
Boot0001* Linux-Firmware-Updater HD(1,GPT,ae17a681-33c0-4384-838f-6358c26959bd,0x800,0x12c000)/File(\EFI\fedora\fwupdx64.efi)
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0015 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0016 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0017 USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018 USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019 NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot001B ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001C USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001D PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001E* IDER BOOT CDROM PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
Boot001F* IDER BOOT Floppy PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
Boot0020* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0021* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
```
```shell
efivar -l | grep fw
0abba7dc-e516-4167-bbf5-4d9d1c739416-fwupd-14cc970e-c105-4eba-a704-448dde9de64d-0
0abba7dc-e516-4167-bbf5-4d9d1c739416-fwupd-9a7f2771-7ce4-4ff1-892b-c2ed700b77de-0
```
```shell
tree /boot
/boot
βββ config-5.19.15-201.fc36.x86_64
βββ config-5.19.16-200.fc36.x86_64
βββ config-6.0.5-200.fc36.x86_64
βββ efi
β βββ EFI
β β βββ BOOT
β β β βββ BOOTIA32.EFI
β β β βββ BOOTX64.EFI
β β β βββ fbia32.efi
β β β βββ fbx64.efi
β β βββ fedora
β β β βββ BOOTIA32.CSV
β β β βββ BOOTX64.CSV
β β β βββ fw
β β β β βββ fwupd-14cc970e-c105-4eba-a704-448dde9de64d.cap
β β β β βββ fwupd-9a7f2771-7ce4-4ff1-892b-c2ed700b77de.cap
β β β βββ fwupdx64.efi
β β β βββ gcdia32.efi
β β β βββ gcdx64.efi
β β β βββ grub.cfg
β β β βββ grub.cfg.rpmsave
β β β βββ grubenv.rpmsave
β β β βββ grubia32.efi
β β β βββ grubx64.efi
β β β βββ mmia32.efi
β β β βββ mmx64.efi
β β β βββ shim.efi
β β β βββ shimia32.efi
β β β βββ shimx64.efi
β β βββ Microsoft
β β βββ Boot
β β β βββ BCD
β β β βββ BCD.LOG
β β β βββ BCD.LOG1
β β β βββ BCD.LOG2
β β β βββ bg-BG
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ bootmgfw.efi
β β β βββ bootmgr.efi
β β β βββ BOOTSTAT.DAT
β β β βββ boot.stl
β β β βββ cs-CZ
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ da-DK
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ de-DE
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ el-GR
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ en-GB
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ en-US
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ es-ES
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ es-MX
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ et-EE
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ fi-FI
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ Fonts
β β β β βββ chs_boot.ttf
β β β β βββ cht_boot.ttf
β β β β βββ jpn_boot.ttf
β β β β βββ kor_boot.ttf
β β β β βββ malgun_boot.ttf
β β β β βββ malgunn_boot.ttf
β β β β βββ meiryo_boot.ttf
β β β β βββ meiryon_boot.ttf
β β β β βββ msjh_boot.ttf
β β β β βββ msjhn_boot.ttf
β β β β βββ msyh_boot.ttf
β β β β βββ msyhn_boot.ttf
β β β β βββ segmono_boot.ttf
β β β β βββ segoen_slboot.ttf
β β β β βββ segoe_slboot.ttf
β β β β βββ wgl4_boot.ttf
β β β βββ fr-CA
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ fr-FR
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ hr-HR
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ hu-HU
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ it-IT
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ ja-JP
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ kd_02_10df.dll
β β β βββ kd_02_10ec.dll
β β β βββ kd_02_1137.dll
β β β βββ kd_02_14e4.dll
β β β βββ kd_02_15b3.dll
β β β βββ kd_02_1969.dll
β β β βββ kd_02_19a2.dll
β β β βββ kd_02_1af4.dll
β β β βββ kd_02_8086.dll
β β β βββ kd_07_1415.dll
β β β βββ kd_0C_8086.dll
β β β βββ kdnet_uart16550.dll
β β β βββ kdstub.dll
β β β βββ ko-KR
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ lt-LT
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ lv-LV
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ memtest.efi
β β β βββ nb-NO
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ nl-NL
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ pl-PL
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ pt-BR
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ pt-PT
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ qps-ploc
β β β β βββ memtest.efi.mui
β β β βββ Resources
β β β β βββ bootres.dll
β β β β βββ en-US
β β β β βββ bootres.dll.mui
β β β βββ ro-RO
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ ru-RU
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ sk-SK
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ sl-SI
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ sr-Latn-RS
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ sv-SE
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ tr-TR
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ uk-UA
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β βββ winsipolicy.p7b
β β β βββ zh-CN
β β β β βββ bootmgfw.efi.mui
β β β β βββ bootmgr.efi.mui
β β β β βββ memtest.efi.mui
β β β βββ zh-TW
β β β βββ bootmgfw.efi.mui
β β β βββ bootmgr.efi.mui
β β β βββ memtest.efi.mui
β β βββ Recovery
β β βββ BCD
β β βββ BCD.LOG
β β βββ BCD.LOG1
β β βββ BCD.LOG2
β βββ mach_kernel
β βββ System
β β βββ Library
β β βββ CoreServices
β β βββ SystemVersion.plist
β βββ System Volume Information
βββ elf-memtest86+-5.31
βββ extlinux
β βββ cat.c32
β βββ chain.c32
β βββ cmd.c32
β βββ cmenu.c32
β βββ config.c32
β βββ cptime.c32
β βββ cpu.c32
β βββ cpuid.c32
β βββ cpuidtest.c32
β βββ debug.c32
β βββ dhcp.c32
β βββ dir.c32
β βββ disk.c32
β βββ dmi.c32
β βββ dmitest.c32
β βββ elf.c32
β βββ ethersel.c32
β βββ gfxboot.c32
β βββ gpxecmd.c32
β βββ hdt.c32
β βββ hexdump.c32
β βββ host.c32
β βββ ifcpu64.c32
β βββ ifcpu.c32
β βββ ifmemdsk.c32
β βββ ifplop.c32
β βββ kbdmap.c32
β βββ kontron_wdt.c32
β βββ ldlinux.c32
β βββ lfs.c32
β βββ libcom32.c32
β βββ libgpl.c32
β βββ liblua.c32
β βββ libmenu.c32
β βββ libutil.c32
β βββ linux.c32
β βββ ls.c32
β βββ lua.c32
β βββ mboot.c32
β βββ memdisk
β βββ meminfo.c32
β βββ menu.c32
β βββ pci.c32
β βββ pcitest.c32
β βββ pmload.c32
β βββ poweroff.c32
β βββ prdhcp.c32
β βββ pwd.c32
β βββ pxechn.c32
β βββ reboot.c32
β βββ rosh.c32
β βββ sanboot.c32
β βββ sdi.c32
β βββ sysdump.c32
β βββ syslinux.c32
β βββ vesa.c32
β βββ vesainfo.c32
β βββ vesamenu.c32
β βββ vpdtest.c32
β βββ whichsys.c32
β βββ zzjson.c32
βββ grub2
β βββ fonts
β β βββ unicode.pf2
β βββ grub.cfg
β βββ grubenv
β βββ themes
β βββ system
βββ initramfs-0-rescue-f3ad94e852e24c3a9478027050fb91f1.img
βββ initramfs-5.19.15-201.fc36.x86_64.img
βββ initramfs-5.19.16-200.fc36.x86_64.img
βββ initramfs-6.0.5-200.fc36.x86_64.img
βββ loader
β βββ entries
β βββ f3ad94e852e24c3a9478027050fb91f1-0-rescue.conf
β βββ f3ad94e852e24c3a9478027050fb91f1-5.19.15-201.fc36.x86_64.conf
β βββ f3ad94e852e24c3a9478027050fb91f1-5.19.16-200.fc36.x86_64.conf
β βββ f3ad94e852e24c3a9478027050fb91f1-6.0.5-200.fc36.x86_64.conf
βββ lost+found
βββ memtest86+-5.31
βββ symvers-5.19.15-201.fc36.x86_64.gz -> /lib/modules/5.19.15-201.fc36.x86_64/symvers.gz
βββ symvers-5.19.16-200.fc36.x86_64.gz -> /lib/modules/5.19.16-200.fc36.x86_64/symvers.gz
βββ symvers-6.0.5-200.fc36.x86_64.gz -> /lib/modules/6.0.5-200.fc36.x86_64/symvers.gz
βββ System.map-5.19.15-201.fc36.x86_64
βββ System.map-5.19.16-200.fc36.x86_64
βββ System.map-6.0.5-200.fc36.x86_64
βββ vmlinuz-0-rescue-f3ad94e852e24c3a9478027050fb91f1
βββ vmlinuz-5.19.15-201.fc36.x86_64
βββ vmlinuz-5.19.16-200.fc36.x86_64
βββ vmlinuz-6.0.5-200.fc36.x86_64
59 directories, 248 files
```
**Additional questions**
- Operating system and version: Fedora release 36 (Thirty Six)
- Have you tried rebooting? Yes
- Is this a regression? I'm not sure.
- Are you using an NVMe disk? Yes, Samsung model: MZVLW256HEHP-000L7
- Is secure boot enabled? Not anymore (After I read https://github.com/fwupd/fwupd/wiki/LVFS-Triaged-Issue:-Failed-to-run-update-on-reboot I disabled secure boot and reproduced this issue)
- Is this a Lenovo system with 'Boot Order Lock' turned on in the BIOS? No.
(It appears you may need to selectively update the βSystem Firmwareβ before the rest.)
This is very out of date - I believe this also matches the other reports of the system firmware being βtoo oldβ for the update to easily be applied.
It would appear that a bootable ISO is available.
This is good, and can be used instead of or before fwupd
.
The iso
file is this one at the link;
https://download.lenovo.com/pccbbs/mobiles/n23ur42w.iso
2 Likes
_dunce
23 November 2024 08:33
5
Thank you . So I managed to follow steps suggested in the first link to upgrade from 1.25->1.30
inxi -Farz | grep UEFI
uuid: <superuser required> UEFI: LENOVO v: N23ET55W (1.30 )
Specifically,
fwupdmgr get-devices | grep -A 17 'System Firmware'
fwupdmgr update d169f51617850d36bdc7c22c7fd512bc9680c95a
this rebooted my machine into what I think was the Lenovo firmware updater (BIOS looking fonts etc) - took a few minutes with lots of beeping. Update was successful.
Then fumbled around trying to boot with the .iso file - followed the usual steps using dd
etc. but was unable to boot.
I then did the exact same as the above again:
fwupdmgr update d169f51617850d36bdc7c22c7fd512bc9680c95a
This time there was no BIOS-looking update displayed on reboot, just the text
fwupd-efi version 1.6
Reset system
followed by a generic βLenovoβ screen that persisted for a few minutes. Scary! System rebooted normally and I then did a fwupdmgr update
which resulted in the same as the above + several loops through the BIOS splash screen and now I have uuid: <superuser required> UEFI: LENOVO v: N23ET89W (1.64 )
and additionally
>> fwupdmgr get-updates
Devices with no available firmware updates:
β’ UEFI Device Firmware
Devices with the latest available firmware version:
β’ Embedded Controller
β’ Intel Management Engine
β’ MZVLB256HAHQ-000L7
β’ System Firmware
β’ Thunderbolt host controller
No updates available
Unfortunately after the above I unplugged the power and instantly went into another kernel panic. How do I determine if firmware is at the latest version? Iβm guessing βno available firmware updatesβ doesnβt imply βup to dateββ¦
cscs
23 November 2024 10:12
6
This would indicate to me that you have the latest BIOS.
(As 1.64 is the latest version provided by the lenovo website.)
Now, rebooting into the BIOS settings can you find a setting for sleep ?
Recall that we want to change the sleep state option to βLinuxβ mode.
The following should reboot you into BIOS directly;
systemctl reboot --firmware-setup
_dunce
23 November 2024 12:18
7
Recall that we want to change the sleep state option to βLinuxβ mode.
Quite right! Forgot to look for it⦠Set the sleep state to Linux - will play around with things over the next few days before marking as solved.
1 Like
Hey @_dunce ,
Itβs always nice to see a post you created get bumped up. Like a proud father I got the notification, and came to check out whatβs going on. Apologies for the delay.
Kernel Panics:
So, I did resolve this issue and I still have my X1C6 running Manjaro without any issues today. What I did to finally resolve the issue was to adjust some intel graphics kernel parameters.
Check out the wiki page here:
https://wiki.archlinux.org/title/Intel_graphics
Specifically, look at: β6.15 Crash/freeze on low power Intel CPUsβ section. If I recall correctly, someone pointed me to this step due to some odd behavior with the integrated Intel GPU and the Kaby Lake CPUs that come with the X1C6 Thinkpads. Iβd start with adding all 3 Kernel parameters to see if it fixes your panic issues first. If it does, then follow the Wiki and see which ones you can remove to keep the laptop working properly.
BIOS and Firmware Updates:
Also, I read you did a lot of extra work to get the BIOS and other system updates and firmware done. Word of advice (at least what I do), is always dual-boot and keep a small Windows partition around for system updates. The βLenovo Vantageβ software that is used for updating all the major components (Thunderbolt Controller, BIOS, Firmware updates, etc.) is solid and super easy to update BIOS and other components. Basically, this is the only reason I dual-boot and still use Windows occasionally.
Good luck with the troubleshooting. Hopefully, this gets things working properly for you!
Thanks,
Asif
1 Like
_dunce
23 November 2024 23:31
9
So unfortunately the firmware update / setting linux sleep state did not resolve the issue (but this needed to be done anyway).
So, I did resolve this issue and I still have my X1C6 running Manjaro without any issues today. What I did to finally resolve the issue was to adjust some intel graphics kernel parameters.
Interesting. Thanks for this. Iβve stuck all three in the GRUB_CMDLINE_LINUX_DEFAULT=
line and updated grub. Will see how it goes.
I am curious why this issue has only popped up in the last year or so.
cscs
23 November 2024 23:36
10
https://wiki.archlinux.org/title/Intel_graphics#Crash/freeze_on_low_power_Intel_CPUs
Low-powered Intel processors and/or laptop processors have a tendency to randomly hang or crash due to the problems with the power management features found in low-power Intel chips. If such a crash happens, you will not see any logs reporting this problem. Adding the following Kernel parameters may help to resolve the problem.
Note: It is not advised to use all three of the below kernel parameters together.
intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1
[β¦]
Some emphasis added by me. ^
I would shoot for ahci.mobile_lpm_policy=1
alone first, as it is the least disruptive.
1 Like
_dunce
24 November 2024 10:54
11
Thanks. I did note the note about using all three but there is also apparently βcontentionβ about the disruptiveness of enable_dc=0
β¦ Iβve followed your suggestion for now - reverting to just the third flag.
_dunce
27 November 2024 22:43
13
Hi,
I had about 1-2 days of moderate/heavy use without any panics with just the ahci.mobile_lpm_policy=1
flag. Unfortunately it didnβt last - after opening laptop from sleep and logging in (~2 days ago), I started an application and then panic. Iβve now got the enable_dc=0
flag by itself. Will give it a couple more days. About ready to launch the machine out the window and buy a new one .
1 Like