Bug 2231982 - [abrt] intel_plane_atomic_check_with_state: WARNING: CPU: 7 PID: 86 at drivers/gpu/drm/i915/display/intel_atomic_plane.c:493 intel_plane_atomic_check_with_state+0x656/0x890 [i915] [i915]
Summary: [abrt] intel_plane_atomic_check_with_state: WARNING: CPU: 7 PID: 86 at driver...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b1d737815aab917f0803853bfe3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-14 22:40 UTC by nordek2000
Modified: 2023-08-14 22:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (92.29 KB, text/plain)
2023-08-14 22:40 UTC, nordek2000
no flags Details

Description nordek2000 2023-08-14 22:40:38 UTC
Description of problem:
I turned on my laptop, logged in and the notification about an error was there. The only thing different was that the lid was closed during the boot process (I closed it right after clicking the power button) and opened to see the login screen. My system is configured to turn off the screen when the lid is closed and the error is related to x11 and the intel driver? I have an integrated intel GPU. This might be the root of the problem or it might not, I don't know.

Additional info:
reporter:       libreport-2.17.11
WARNING: CPU: 7 PID: 86 at drivers/gpu/drm/i915/display/intel_atomic_plane.c:493 intel_plane_atomic_check_with_state+0x656/0x890 [i915]
Modules linked in: amdgpu i915 rtsx_usb_sdmmc nvme mmc_core i2c_algo_bit drm_ttm_helper nvme_core crct10dif_pclmul crc32_pclmul drm_suballoc_helper crc32c_intel ttm iommu_v2 polyval_clmulni hid_multitouch gpu_sched drm_buddy ucsi_acpi polyval_generic drm_display_helper typec_ucsi ghash_clmulni_intel sha512_ssse3 r8169 nvme_common typec i2c_hid_acpi rtsx_usb cec i2c_hid video wmi pinctrl_sunrisepoint serio_raw fuse
CPU: 7 PID: 86 Comm: kworker/7:1 Not tainted 6.4.9-200.fc38.x86_64 #1
Hardware name: Dell Inc. Inspiron 5570/0YDF7T, BIOS 1.14.0 04/06/2023
Workqueue: events output_poll_execute
RIP: 0010:intel_plane_atomic_check_with_state+0x656/0x890 [i915]
Code: 4c 89 44 24 08 48 89 54 24 18 e8 a5 0f 30 cd 48 8b 54 24 18 48 c7 c1 7b fe a0 c0 48 c7 c7 71 fe a0 c0 48 89 c6 e8 2a 69 95 cc <0f> 0b 44 0f b6 5c 24 20 4c 8b 44 24 08 4c 8b 54 24 10 44 0f b6 4c
RSP: 0018:ffff9dc200427b50 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff92a8444e6000 RCX: 0000000000000027
RDX: ffff92abaf5e1548 RSI: 0000000000000001 RDI: ffff92abaf5e1540
RBP: ffff92a852503000 R08: 0000000000000000 R09: ffff9dc2004279e0
R10: 0000000000000003 R11: ffffffff8f146508 R12: 0000000000000000
R13: ffff92a8524e9800 R14: 0000000000000001 R15: ffff92a84137fc00
FS:  0000000000000000(0000) GS:ffff92abaf5c0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1796a07d70 CR3: 000000010d022001 CR4: 00000000003706e0
Call Trace:
 <TASK>
 ? intel_plane_atomic_check_with_state+0x656/0x890 [i915]
 ? __warn+0x81/0x130
 ? intel_plane_atomic_check_with_state+0x656/0x890 [i915]
 ? report_bug+0x171/0x1a0
 ? prb_read_valid+0x1b/0x30
 ? handle_bug+0x3c/0x80
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? intel_plane_atomic_check_with_state+0x656/0x890 [i915]
 intel_atomic_check+0x1404/0x2b10 [i915]
 ? __ww_mutex_lock.constprop.0+0x5d/0x940
 drm_atomic_check_only+0x5c2/0xa40
 drm_atomic_commit+0x5a/0xd0
 ? __pfx___drm_printfn_info+0x10/0x10
 drm_client_modeset_commit_atomic+0x203/0x250
 drm_client_modeset_commit_locked+0x5a/0x160
 ? drm_connector_list_iter_end+0x3c/0x60
 drm_client_modeset_commit+0x25/0x40
 __drm_fb_helper_restore_fbdev_mode_unlocked+0x85/0xd0
 drm_fb_helper_hotplug_event+0xe5/0x100
 output_poll_execute+0x1fa/0x240
 process_one_work+0x1c4/0x3d0
 worker_thread+0x51/0x390
 ? __pfx_worker_thread+0x10/0x10
 kthread+0xe5/0x120
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x29/0x50
 </TASK>

Potential duplicate: bug 1883968

Comment 1 nordek2000 2023-08-14 22:40:45 UTC
Created attachment 1983328 [details]
File: dmesg


Note You need to log in before you can comment on or make changes to this bug.