Bug 2080777
| Summary: | [abrt] intel_atomic_commit: WARNING: CPU: 5 PID: 1136 at drivers/gpu/drm/i915/display/intel_display.c:7007 intel_atomic_commit_tail+0x188c/0x1930 [i915] [i915] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Carlos Gomez <carlosegomez> | ||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 36 | CC: | ajax, jglisse, kernel-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/722e6f934c390237cd772a4db111143ce009ae04 | ||||||
| Whiteboard: | abrt_hash:b6a7d47829fe66f3c9fd1a97a24b8270b8ddbf16;VARIANT_ID=workstation; | ||||||
| Fixed In Version: | Doc Type: | --- | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-05-25 15:22:53 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Carlos Gomez
2022-05-01 19:28:00 UTC
Created attachment 1876383 [details]
File: dmesg
Description of problem: I tried to connect my DisplayPort monitor (LG's 27GN850) to my DP expansion card on my Framework laptop running Gnome 42.1 and Fedora 36, and got this error. I don't have any information on the cause though, I've done this before with no errors. Version-Release number of selected component: kernel-core-5.17.6-300.fc36 Additional info: reporter: libreport-2.17.1 cmdline: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-5.17.6-300.fc36.x86_64 root=UUID=171ac727-adbf-4270-87ea-f02ecc3a5fc4 ro rootflags=subvol=root rd.luks.uuid=luks-2217ccec-e402-41da-ba05-5faf2eda6732 rhgb quiet crash_function: intel_atomic_commit kernel: 5.17.6-300.fc36.x86_64 runlevel: N 5 type: Kerneloops Truncated backtrace: #1 [TASK] intel_atomic_commit in i915 #2 [TASK] drm_mode_atomic_ioctl #3 [TASK] ? drm_plane_get_damage_clips #4 [TASK] ? drm_atomic_set_property #5 [TASK] drm_ioctl_kernel #6 [TASK] drm_ioctl #7 [TASK] ? drm_atomic_set_property #8 [TASK] __x64_sys_ioctl #9 [TASK] do_syscall_64 #10 [TASK] entry_SYSCALL_64_after_hwframe 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. 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. |