Bug 2222967 - [abrt] intel_modeset_verify_crtc: WARNING: CPU: 4 PID: 293 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_verify_crtc+0x3ae/0x3e0 [i915] [i915]
Summary: [abrt] intel_modeset_verify_crtc: WARNING: CPU: 4 PID: 293 at drivers/gpu/drm...
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:
Whiteboard: abrt_hash:284af31328ddce495ce150ea858...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-14 16:04 UTC by Cullen
Modified: 2023-07-14 16:05 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Cullen 2023-07-14 16:04:18 UTC
Description of problem:
I applied an update and the issue appeared when the laptop restarted.

I'm uncertain how to view exactly what the problematic update was. With help I'd be happy to try to find that info.

For reference, the change happened around 2023-07-14 11:55 Eastern.

Additional info:
reporter:       libreport-2.17.10
WARNING: CPU: 4 PID: 293 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_verify_crtc+0x3ae/0x3e0 [i915]
Modules linked in: i915 i2c_algo_bit drm_buddy drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic cec nvme ghash_clmulni_intel hid_multitouch video ucsi_acpi nvme_core sha512_ssse3 typec_ucsi i2c_hid_acpi ttm typec i2c_hid nvme_common wmi pinctrl_tigerlake serio_raw ip6_tables ip_tables fuse
CPU: 4 PID: 293 Comm: kworker/4:4 Not tainted 6.3.8-200.fc38.x86_64 #1
Hardware name: LENOVO 20XXS3HC00/20XXS3HC00, BIOS N32ET84W (1.60 ) 04/05/2023
Workqueue: events_long drm_dp_mst_link_probe_work [drm_display_helper]
RIP: 0010:intel_modeset_verify_crtc+0x3ae/0x3e0 [i915]
Code: 01 00 00 e9 6e fd ff ff e8 8f f2 79 d9 0f 0b e9 09 fe ff ff e8 83 f2 79 d9 0f 0b 0f b6 44 24 17 e9 cb fd ff ff e8 72 f2 79 d9 <0f> 0b e9 9e fe ff ff e8 66 f2 79 d9 0f 0b 0f b6 85 50 01 00 00 e9
RSP: 0018:ffffb2af40f27bc0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff9a8ace5402a8 RCX: 0000000000000027
RDX: ffff9a91ff721548 RSI: 0000000000000001 RDI: ffff9a91ff721540
RBP: ffff9a8ac4e80000 R08: 0000000000000000 R09: ffffb2af40f27a50
R10: 0000000000000003 R11: ffffffff9c146108 R12: ffff9a8ac4e62000
R13: ffff9a8aca7f9800 R14: ffff9a8aca7f9800 R15: ffff9a8ace5402b0
FS:  0000000000000000(0000) GS:ffff9a91ff700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8de17b7d70 CR3: 000000011d022006 CR4: 0000000000f70ee0
PKRU: 55555554
Call Trace:
 <TASK>
 ? intel_modeset_verify_crtc+0x3ae/0x3e0 [i915]
 ? __warn+0x81/0x130
 ? intel_modeset_verify_crtc+0x3ae/0x3e0 [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_modeset_verify_crtc+0x3ae/0x3e0 [i915]
 ? mutex_lock+0x12/0x30
 intel_atomic_commit_tail+0xa22/0xfa0 [i915]
 intel_atomic_commit+0x340/0x380 [i915]
 drm_atomic_commit+0x97/0xd0
 ? __pfx___drm_printfn_info+0x10/0x10
 drm_client_modeset_commit_atomic+0x203/0x250
 drm_client_modeset_commit_locked+0x5a/0x160
 drm_client_modeset_commit+0x25/0x40
 drm_fb_helper_set_par+0xa2/0x100
 drm_fb_helper_hotplug_event+0xc8/0xe0
 drm_kms_helper_hotplug_event+0x27/0x40
 process_one_work+0x1c4/0x3d0
 worker_thread+0x51/0x390
 ? __pfx_worker_thread+0x10/0x10
 kthread+0xdb/0x110
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x29/0x50
 </TASK>

Potential duplicate: bug 2167095

Comment 1 Cullen 2023-07-14 16:05:13 UTC
Description of problem:
I applied an update and the issue appeared when the laptop restarted.

I'm uncertain how to view exactly what the problematic update was. With help I'd be happy to try to find that info.

For reference, the change happened around 2023-07-14 11:55 Eastern.

Version-Release number of selected component:
kernel-core-6.3.8-200.fc38

Additional info:
reporter:       libreport-2.17.10
kernel:         6.3.8-200.fc38.x86_64
crash_function: intel_modeset_verify_crtc
reason:         WARNING: CPU: 4 PID: 293 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_verify_crtc+0x3ae/0x3e0 [i915] [i915]
type:           Kerneloops
cmdline:        BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.3.8-200.fc38.x86_64 root=UUID=75fbb542-9194-479d-975a-affd2dfa9beb ro rootflags=subvol=root rd.luks.uuid=luks-3718473b-3660-4d2c-a015-558c191bd72d rhgb quiet rd.luks.key=3718473b-3660-4d2c-a015-558c191bd72d=/keyfile:UUID=9da86af5-4430-4bb0-a0fc-6cb36b67bbc7
package:        kernel-core-6.3.8-200.fc38
runlevel:       unknown

Truncated backtrace:
WARNING: CPU: 4 PID: 293 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_verify_crtc+0x3ae/0x3e0 [i915]
Modules linked in: i915 i2c_algo_bit drm_buddy drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic cec nvme ghash_clmulni_intel hid_multitouch video ucsi_acpi nvme_core sha512_ssse3 typec_ucsi i2c_hid_acpi ttm typec i2c_hid nvme_common wmi pinctrl_tigerlake serio_raw ip6_tables ip_tables fuse
CPU: 4 PID: 293 Comm: kworker/4:4 Not tainted 6.3.8-200.fc38.x86_64 #1
Hardware name: LENOVO 20XXS3HC00/20XXS3HC00, BIOS N32ET84W (1.60 ) 04/05/2023
Workqueue: events_long drm_dp_mst_link_probe_work [drm_display_helper]
RIP: 0010:intel_modeset_verify_crtc+0x3ae/0x3e0 [i915]
Code: 01 00 00 e9 6e fd ff ff e8 8f f2 79 d9 0f 0b e9 09 fe ff ff e8 83 f2 79 d9 0f 0b 0f b6 44 24 17 e9 cb fd ff ff e8 72 f2 79 d9 <0f> 0b e9 9e fe ff ff e8 66 f2 79 d9 0f 0b 0f b6 85 50 01 00 00 e9
RSP: 0018:ffffb2af40f27bc0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff9a8ace5402a8 RCX: 0000000000000027
RDX: ffff9a91ff721548 RSI: 0000000000000001 RDI: ffff9a91ff721540
RBP: ffff9a8ac4e80000 R08: 0000000000000000 R09: ffffb2af40f27a50
R10: 0000000000000003 R11: ffffffff9c146108 R12: ffff9a8ac4e62000
R13: ffff9a8aca7f9800 R14: ffff9a8aca7f9800 R15: ffff9a8ace5402b0
FS:  0000000000000000(0000) GS:ffff9a91ff700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8de17b7d70 CR3: 000000011d022006 CR4: 0000000000f70ee0
PKRU: 55555554
Call Trace:
 <TASK>
 ? intel_modeset_verify_crtc+0x3ae/0x3e0 [i915]
 ? __warn+0x81/0x130
 ? intel_modeset_verify_crtc+0x3ae/0x3e0 [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_modeset_verify_crtc+0x3ae/0x3e0 [i915]
 ? mutex_lock+0x12/0x30
 intel_atomic_commit_tail+0xa22/0xfa0 [i915]
 intel_atomic_commit+0x340/0x380 [i915]
 drm_atomic_commit+0x97/0xd0
 ? __pfx___drm_printfn_info+0x10/0x10
 drm_client_modeset_commit_atomic+0x203/0x250
 drm_client_modeset_commit_locked+0x5a/0x160
 drm_client_modeset_commit+0x25/0x40
 drm_fb_helper_set_par+0xa2/0x100
 drm_fb_helper_hotplug_event+0xc8/0xe0
 drm_kms_helper_hotplug_event+0x27/0x40
 process_one_work+0x1c4/0x3d0
 worker_thread+0x51/0x390
 ? __pfx_worker_thread+0x10/0x10
 kthread+0xdb/0x110
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x29/0x50
 </TASK>


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