You are not logged in.
Hi, I have the laptop:
inxi --cpu --gpu
CPU:
Info: model: 12th Gen Intel Core i7-1255U bits: 64 type: MST AMCP
arch: Alder Lake level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
microcode: 0x423
Topology: cpus: 1x cores: 10 mt: 2 tpc: 2 st: 8 threads: 12 smt: enabled
cache: L1: 928 KiB desc: d-8x32 KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB
L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 416 high: 592 min/max: 400/4700:3500 scaling:
driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 592 4: 400
5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 bogomips: 62688
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
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_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: Enhanced / Automatic 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 Alder Lake-UP3 GT2 [Iris Xe Graphics] vendor: Micro-Star MSI
driver: i915 v: kernel arch: Gen-12.2 process: Intel 10nm built: 2021-22+
ports: active: HDMI-A-1,eDP-1 empty: none bus-ID: 00:02.0
chip-ID: 8086:46a8 class-ID: 0300
Display: x11 server: X.Org v: 21.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1013x285mm (39.88x11.22")
s-diag: 1052mm (41.43")
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: left model: Gigabyte M27F A
serial: 22123B000378 built: 2022 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
Monitor-2: eDP-1 pos: primary,right model: ChiMei InnoLux 0x15e7
built: 2020 res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2
size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9
modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
device-ID: 8086:46a8 memory: 14.97 GiB unified: yes
API: Vulkan Message: No Vulkan data available.
The kernel version:
uname -r
6.6.2-arch1-1
All packages are up-to-date.
Several times a day the laptop unexpectedly freezes. No keyboard/mouse/tty available. The only thing you can do - is to hold the poweroff button.
The last things in the kernel log are:
journalctl -b -1 -k
...
Dec 03 12:36:00 MSI2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out
Dec 03 12:36:18 MSI2 kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Dec 03 12:36:18 MSI2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out
Dec 03 12:36:28 MSI2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out
Any ideas?
Last edited by winac (2023-12-03 10:13:12)
Offline
The kernel version:
uname -r 6.6.2-arch1-1
All packages are up-to-date.
Those two statements are not compatible. Does upgrading your kernel version to the current package help?
And do you have the CPU µcode installed and loaded?
Para todos todo, para nosotros nada
Offline
Changing the kernel gives no positive effect.
However, I figured out the answer. A discussion has been posted at https://gitlab.freedesktop.org/drm/intel/-/issues/8685 on Freedesktop.
Where a large number of people complain, they all have the exact same issue with the same symptoms.
The Intel i915 video diver is the root of the problem that affects all of us. The solution is to add
i915.dmc_firmware_path=
kernel parameter at startup, which resolves the problem.
Last edited by winac (2023-12-07 07:13:48)
Offline
Please edit the title of the thread and prepend [SOLVED] to help others who encounter this issue. Thanks.
Para todos todo, para nosotros nada
Offline