You are not logged in.

#1 2022-09-30 23:56:42

tummychow
Member
Registered: 2014-08-03
Posts: 10

linux 5.19.12 + i915 + alder lake issue

Anyone else having peculiarities with intel graphics on 5.19.12? I'm on a laptop (Lenovo Legion 5 Gen7 15IAH7H, Alder Lake i7-12700H) and when I boot this kernel, the laptop internal screen seems to flicker between "on but completely black" and "off" every second or so without actually displaying anything. Trying to bring up X11 doesn't change the issue. An external monitor connected to the internal GPU does work but takes 30+ seconds to actually get to an X11 desktop. Basically lots of strangeness, difficult to describe. This reproduces consistently on my machine with 5.19.12 and disappears immediately after downgrading to 5.19.11.

Here's the relevant chunk of kernel logs in case someone is trying to google the issue:

Sep 30 16:39:46 archaism kernel: i915 0000:00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref)
Sep 30 16:39:46 archaism kernel: WARNING: CPU: 4 PID: 1099 at drivers/gpu/drm/i915/display/intel_pps.c:594 intel_pps_vdd_on_unlocked+0x2a0/0x2b0 [i915]
Sep 30 16:39:46 archaism kernel: Modules linked in: snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pc>
Sep 30 16:39:46 archaism kernel:  ideapad_laptop sparse_keymap platform_profile int3403_thermal int340x_thermal_zone ccm int3400_thermal acpi_thermal_rel algif_aead des_generic bridge libdes>
Sep 30 16:39:46 archaism kernel: Unloaded tainted modules: pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1>
Sep 30 16:39:46 archaism kernel:  acpi_cpufreq():1
Sep 30 16:39:46 archaism kernel: CPU: 4 PID: 1099 Comm: systemd-udevd Not tainted 5.19.12-arch1-1 #1 2183db5e2ff49b915549bc42a3e56ec968f6996b
Sep 30 16:39:46 archaism kernel: Hardware name: LENOVO 82RB/LNVNB161216, BIOS J2CN40WW 04/15/2022
Sep 30 16:39:46 archaism kernel: RIP: 0010:intel_pps_vdd_on_unlocked+0x2a0/0x2b0 [i915]
Sep 30 16:39:46 archaism kernel: Code: 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 69 4a 5c f6 48 c7 c1 d8 f4 28 c1 4c 89 e2 48 c7 c7 60 f2 29 c1 48 89 c6 e8 af c4 98 f6 <0f> 0b e9 f3 fd ff ff e8>
Sep 30 16:39:46 archaism kernel: RSP: 0018:ffffb2e6c1997620 EFLAGS: 00010286
Sep 30 16:39:46 archaism kernel: RAX: 0000000000000000 RBX: ffff8b6088de2170 RCX: 0000000000000027
Sep 30 16:39:46 archaism kernel: RDX: ffff8b680f721668 RSI: 0000000000000001 RDI: ffff8b680f721660
Sep 30 16:39:46 archaism kernel: RBP: ffff8b60c3b60000 R08: 0000000000000000 R09: ffffb2e6c19974a8
Sep 30 16:39:46 archaism kernel: R10: 0000000000000003 R11: ffff8b682fbac328 R12: ffff8b6082fa13f0
Sep 30 16:39:46 archaism kernel: R13: 0000000000000005 R14: ffff8b60c3b607e0 R15: 0000000000000000
Sep 30 16:39:46 archaism kernel: FS:  00007f2701cec200(0000) GS:ffff8b680f700000(0000) knlGS:0000000000000000
Sep 30 16:39:46 archaism kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 30 16:39:46 archaism kernel: CR2: 00007ffc045d7080 CR3: 000000013ce28004 CR4: 0000000000f70ee0
Sep 30 16:39:46 archaism kernel: PKRU: 55555554
Sep 30 16:39:46 archaism kernel: Call Trace:
Sep 30 16:39:46 archaism kernel:  <TASK>
Sep 30 16:39:46 archaism kernel:  ? __intel_display_power_get_domain.part.0+0x52/0x70 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  ? intel_display_power_get+0x52/0x60 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  intel_dp_aux_xfer+0x127/0x7a0 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  ? clockevents_program_event+0x97/0x100
Sep 30 16:39:46 archaism kernel:  ? hrtimer_try_to_cancel+0x19/0x100
Sep 30 16:39:46 archaism kernel:  intel_dp_aux_transfer+0x205/0x320 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  drm_dp_dpcd_access+0xaa/0x130 [drm_display_helper 3265fc5a08ef92bdf2cb67c2e59c3aa8c56b9ab4]
Sep 30 16:39:46 archaism kernel:  drm_dp_dpcd_write+0x8d/0xe0 [drm_display_helper 3265fc5a08ef92bdf2cb67c2e59c3aa8c56b9ab4]
Sep 30 16:39:46 archaism kernel:  intel_dp_set_power+0x67/0x190 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  intel_ddi_post_disable+0x44e/0x4a0 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  intel_encoders_post_disable+0x7b/0x90 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  intel_old_crtc_state_disables+0x38/0xa0 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  intel_atomic_commit_tail+0x3df/0x1aa0 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  ? complete+0x1c/0x80
Sep 30 16:39:46 archaism kernel:  ? __flush_workqueue+0x1a0/0x420
Sep 30 16:39:46 archaism kernel:  ? intel_atomic_commit+0x350/0x390 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  intel_atomic_commit+0x350/0x390 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  drm_atomic_commit+0x95/0xd0
Sep 30 16:39:46 archaism kernel:  ? drm_plane_get_damage_clips.cold+0x1c/0x1c
Sep 30 16:39:46 archaism kernel:  intel_modeset_init+0x1a0/0x280 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  i915_driver_probe+0x4c0/0xd60 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  ? intel_modeset_probe_defer+0x4f/0x60 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  ? i915_pci_probe+0x43/0x160 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  local_pci_probe+0x42/0x80
Sep 30 16:39:46 archaism kernel:  pci_device_probe+0xc1/0x220
Sep 30 16:39:46 archaism kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Sep 30 16:39:46 archaism kernel:  really_probe+0x1bf/0x390
Sep 30 16:39:46 archaism kernel:  __driver_probe_device+0xff/0x170
Sep 30 16:39:46 archaism kernel:  driver_probe_device+0x1f/0x90
Sep 30 16:39:46 archaism kernel:  __driver_attach+0xd3/0x1d0
Sep 30 16:39:46 archaism kernel:  ? __device_attach_driver+0x110/0x110
Sep 30 16:39:46 archaism kernel:  bus_for_each_dev+0x88/0xd0
Sep 30 16:39:46 archaism kernel:  bus_add_driver+0x164/0x220
Sep 30 16:39:46 archaism kernel:  driver_register+0x8d/0xe0
Sep 30 16:39:46 archaism kernel:  i915_init+0x23/0x83 [i915 bb3ac8ac02e0a838fd4d1310a49fd165c756a21e]
Sep 30 16:39:46 archaism kernel:  ? 0xffffffffc139e000
Sep 30 16:39:46 archaism kernel:  do_one_initcall+0x5a/0x220
Sep 30 16:39:46 archaism kernel:  do_init_module+0x4a/0x1e0
Sep 30 16:39:46 archaism kernel:  __do_sys_init_module+0x138/0x1b0
Sep 30 16:39:46 archaism kernel:  do_syscall_64+0x5c/0x90
Sep 30 16:39:46 archaism kernel:  ? exc_page_fault+0x74/0x170
Sep 30 16:39:46 archaism kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Sep 30 16:39:46 archaism kernel: RIP: 0033:0x7f27020adb4e
Sep 30 16:39:46 archaism kernel: Code: 48 8b 0d 3d f2 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01>
Sep 30 16:39:46 archaism kernel: RSP: 002b:00007ffc484c2968 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Sep 30 16:39:46 archaism kernel: RAX: ffffffffffffffda RBX: 0000557e65f62270 RCX: 00007f27020adb4e
Sep 30 16:39:46 archaism kernel: RDX: 00007f27021f9343 RSI: 000000000069c18e RDI: 00007f26ff993010
Sep 30 16:39:46 archaism kernel: RBP: 00007f27021f9343 R08: 0000000000261000 R09: 85ebca77c2b2ae63
Sep 30 16:39:46 archaism kernel: R10: 0000000000012931 R11: 0000000000000246 R12: 0000000000020000
Sep 30 16:39:46 archaism kernel: R13: 0000557e65faaca0 R14: 0000557e65f62270 R15: 0000557e65fae640
Sep 30 16:39:46 archaism kernel:  </TASK>

Offline

#2 2022-10-01 00:08:28

loqs
Member
Registered: 2014-03-06
Posts: 17,198

Re: linux 5.19.12 + i915 + alder lake issue

Online

#3 2022-10-01 00:09:38

tummychow
Member
Registered: 2014-08-03
Posts: 10

Re: linux 5.19.12 + i915 + alder lake issue

Doh, that's me alright. Should have looked more closely.

Offline

Board footer

Powered by FluxBB