Bug 2089818 - [abrt] intel_atomic_commit: WARNING: CPU: 0 PID: 8 at drivers/gpu/drm/i915/display/intel_display.c:7007 intel_atomic_commit_tail+0x188c/0x1930 [i915] [i915]
Summary: [abrt] intel_atomic_commit: WARNING: CPU: 0 PID: 8 at drivers/gpu/drm/i915/di...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 36
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:f01a296d50005fff14c25fff847...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 13:48 UTC by Bryan Kearney
Modified: 2023-05-25 15:23 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-05-25 15:23:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (104.47 KB, text/plain)
2022-05-24 13:48 UTC, Bryan Kearney
no flags Details

Description Bryan Kearney 2022-05-24 13:48:23 UTC
Description of problem:
dnf upgrade and a sudo reboot. Running on a thikpad x1, gen 9.

Additional info:
reporter:       libreport-2.17.1
WARNING: CPU: 0 PID: 8 at drivers/gpu/drm/i915/display/intel_display.c:7007 intel_atomic_commit_tail+0x188c/0x1930 [i915]
Modules linked in: acpi_cpufreq(-) intel_uncore iwlmei snd_seq_device pcspkr snd_pcm uvcvideo btusb think_lmi(+) videobuf2_vmalloc i2c_i801 videobuf2_memops firmware_attributes_class wmi_bmof btrtl cfg80211 videobuf2_v4l2 snd_timer i2c_smbus btbcm btintel mei_me videobuf2_common btmtk joydev videodev idma64 bluetooth mei mc processor_thermal_device_pci_legacy processor_thermal_device hid_logitech_hidpp thunderbolt(+) ecdh_generic processor_thermal_rfim processor_thermal_mbox processor_thermal_rapl intel_rapl_common intel_vsec intel_soc_dts_iosf igen6_edac thinkpad_acpi ledtrig_audio platform_profile rfkill snd soundcore int3403_thermal int340x_thermal_zone soc_button_array intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_tad zram i915 crct10dif_pclmul nvme crc32_pclmul crc32c_intel ucsi_acpi hid_multitouch ghash_clmulni_intel hid_logitech_dj nvme_core typec_ucsi serio_raw ttm typec wmi i2c_hid_acpi i2c_hid video pinctrl_tigerlake ip6_tables ip_tables
 ipmi_devintf ipmi_msghandler fuse
CPU: 0 PID: 8 Comm: kworker/0:1 Not tainted 5.17.9-300.fc36.x86_64 #1
Hardware name: LENOVO 20XXS3HC00/20XXS3HC00, BIOS N32ET75W (1.51 ) 12/02/2021
Workqueue: events output_poll_execute
RIP: 0010:intel_atomic_commit_tail+0x188c/0x1930 [i915]
Code: ff 80 3d f7 a6 1e 00 00 0f b6 d0 8d 71 41 48 c7 c7 c8 59 55 c0 0f 85 9a 00 00 00 e8 ae b8 44 ea e9 58 f9 ff ff e8 cd c6 85 ea <0f> 0b e9 cd f5 ff ff e8 c1 c6 85 ea 0f 0b 0f b6 44 24 20 e9 12 f5
RSP: 0018:ffffbcac000e3c10 EFLAGS: 00010282
RAX: 0000000000000019 RBX: ffff9cbd4121f000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffffab665b1d RDI: 00000000ffffffff
RBP: ffff9cbd4d7a0000 R08: 0000000000000000 R09: ffffbcac000e3a50
R10: ffffbcac000e3a48 R11: 0000000000000003 R12: ffff9cbd4d7a02a0
R13: ffff9cbd4d7a02a8 R14: ffff9cbd46c46000 R15: ffff9cbd4121f000
FS:  0000000000000000(0000) GS:ffff9cc47f600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f96d9e563d8 CR3: 00000001047a6005 CR4: 0000000000770ef0
PKRU: 55555554
Call Trace:
 <TASK>
 intel_atomic_commit+0x339/0x390 [i915]
 drm_client_modeset_commit_atomic+0x1c4/0x200
 drm_client_modeset_commit_locked+0x56/0x150
 drm_client_modeset_commit+0x21/0x40
 drm_fb_helper_set_par+0x98/0xd0
 drm_fb_helper_hotplug_event+0xb9/0xd0
 output_poll_execute+0x8b/0x1e0
 process_one_work+0x1c4/0x380
 worker_thread+0x4d/0x380
 ? _raw_spin_lock_irqsave+0x25/0x50
 ? process_one_work+0x380/0x380
 kthread+0xe6/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x1f/0x30
 </TASK>

Comment 1 Bryan Kearney 2022-05-24 13:48:28 UTC
Created attachment 1882677 [details]
File: dmesg

Comment 2 Bryan Kearney 2022-06-14 16:18:23 UTC
Description of problem:
rebooted my mahcine after an upgrade

Version-Release number of selected component:
kernel-core-5.17.13-300.fc36

Additional info:
reporter:       libreport-2.17.1
cmdline:        BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.17.13-300.fc36.x86_64 root=UUID=a9af848d-1a4f-4a05-9ba9-ec0307b57089 ro rootflags=subvol=root rhgb quiet
crash_function: intel_atomic_commit
kernel:         5.17.13-300.fc36.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 3 PID: 31 at drivers/gpu/drm/i915/display/intel_display.c:7007 intel_atomic_commit_tail+0x188c/0x1930 [i915]
Modules linked in: i915 nvme hid_multitouch ucsi_acpi crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel typec_ucsi serio_raw nvme_core ttm typec wmi i2c_hid_acpi i2c_hid video pinctrl_tigerlake ip6_tables ip_tables ipmi_devintf ipmi_msghandler fuse
CPU: 3 PID: 31 Comm: kworker/3:0 Not tainted 5.17.13-300.fc36.x86_64 #1
Hardware name: LENOVO 20XXS3HC00/20XXS3HC00, BIOS N32ET75W (1.51 ) 12/02/2021
Workqueue: events_long drm_dp_mst_link_probe_work
RIP: 0010:intel_atomic_commit_tail+0x188c/0x1930 [i915]
Code: ff 80 3d f7 a6 1e 00 00 0f b6 d0 8d 71 41 48 c7 c7 c8 09 59 c0 0f 85 9a 00 00 00 e8 de ed 40 c3 e9 58 f9 ff ff e8 de f6 81 c3 <0f> 0b e9 cd f5 ff ff e8 d2 f6 81 c3 0f 0b 0f b6 44 24 20 e9 12 f5
RSP: 0018:ffffac6d801dbc58 EFLAGS: 00010292
RAX: 0000000000000019 RBX: ffffa0c1cc0a7800 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff84664c55 RDI: 00000000ffffffff
RBP: ffffa0c1d0ba0000 R08: 0000000000000000 R09: ffffac6d801dba98
R10: ffffac6d801dba90 R11: 0000000000000003 R12: ffffa0c1d0ba02a0
R13: ffffa0c1d0ba02a8 R14: ffffa0c1c3870000 R15: ffffa0c1cc0a7800
FS:  0000000000000000(0000) GS:ffffa0c8fd6c0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f901c11fa50 CR3: 000000010ee10001 CR4: 0000000000770ee0
PKRU: 55555554
Call Trace:
 <TASK>
 intel_atomic_commit+0x339/0x390 [i915]
 drm_client_modeset_commit_atomic+0x1c4/0x200
 drm_client_modeset_commit_locked+0x56/0x150
 drm_client_modeset_commit+0x21/0x40
 drm_fb_helper_set_par+0x98/0xd0
 drm_fb_helper_hotplug_event+0xb9/0xd0
 drm_kms_helper_hotplug_event+0x23/0x30
 process_one_work+0x1c4/0x380
 worker_thread+0x4d/0x380
 ? process_one_work+0x380/0x380
 kthread+0xe6/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x1f/0x30
 </TASK>

Comment 3 Sander 2022-08-22 07:01:58 UTC
Description of problem:
Cold booted laptop, logged in.

Version-Release number of selected component:
kernel-core-5.18.17-200.fc36

Additional info:
reporter:       libreport-2.17.1
cmdline:        BOOT_IMAGE=(hd0,gpt4)/vmlinuz-5.18.17-200.fc36.x86_64 root=/dev/mapper/vg00-root ro rd.luks.uuid=luks-e7a46be0-2941-42b6-9404-61ee61cf7de3 rd.lvm.lv=vg00/root rhgb quiet
crash_function: intel_atomic_commit
kernel:         5.18.17-200.fc36.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 4 PID: 453 at drivers/gpu/drm/i915/display/intel_display.c:6677 intel_atomic_commit_tail+0x1822/0x18c0 [i915]
Modules linked in: r8152 mii hid_sensor_hub intel_ishtp_hid hid_jabra i915 drm_buddy drm_dp_helper nvme intel_ish_ipc hid_multitouch ucsi_acpi crct10dif_pclmul crc32_pclmul crc32c_intel nvme_core ghash_clmulni_intel typec_ucsi serio_raw typec ttm intel_ishtp vmd wmi i2c_hid_acpi i2c_hid video pinctrl_tigerlake ip6_tables ip_tables fuse
CPU: 4 PID: 453 Comm: kworker/4:2 Not tainted 5.18.17-200.fc36.x86_64 #1
Hardware name: HP HP EliteBook 850 G8 Notebook PC/8846, BIOS T76 Ver. 01.09.01 05/05/2022
Workqueue: events_long drm_dp_mst_link_probe_work [drm_dp_helper]
RIP: 0010:intel_atomic_commit_tail+0x1822/0x18c0 [i915]
Code: ff 80 3d 49 61 1e 00 00 0f b6 d0 8d 71 41 48 c7 c7 a0 9e 70 c0 0f 85 9a 00 00 00 e8 58 91 2d ca e9 77 f9 ff ff e8 73 31 70 ca <0f> 0b e9 f8 f5 ff ff e8 67 31 70 ca 0f 0b 0f b6 44 24 20 e9 3f f5
RSP: 0018:ffffb78a40687c58 EFLAGS: 00010292
RAX: 0000000000000019 RBX: ffff9e3381597000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff8b66f80c RDI: 00000000ffffffff
RBP: ffff9e338fc402a8 R08: 0000000000000000 R09: ffffb78a40687a90
R10: 0000000000000003 R11: ffffffff8bf453e8 R12: ffff9e338fc40000
R13: ffff9e338fc402a0 R14: ffff9e338e038000 R15: ffff9e3381597000
FS:  0000000000000000(0000) GS:ffff9e3b0f900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055af18b732e8 CR3: 00000004efe10002 CR4: 0000000000770ee0
PKRU: 55555554
Call Trace:
 <TASK>
 intel_atomic_commit+0x33f/0x390 [i915]
 drm_client_modeset_commit_atomic+0x1c7/0x200
 drm_client_modeset_commit_locked+0x56/0x160
 drm_client_modeset_commit+0x21/0x40
 drm_fb_helper_set_par+0x9e/0xe0
 drm_fb_helper_hotplug_event+0xbf/0xe0
 drm_kms_helper_hotplug_event+0x23/0x30
 process_one_work+0x1c4/0x380
 worker_thread+0x4d/0x380
 ? _raw_spin_lock_irqsave+0x23/0x50
 ? process_one_work+0x380/0x380
 kthread+0xe6/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x1f/0x30
 </TASK>

Comment 4 Ben Cotton 2023-04-25 17:14:14 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Ludek Smid 2023-05-25 15:23:28 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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