Bug 1984749
| Summary: | [abrt] intel_pps_on: WARNING: CPU: 7 PID: 149 at drivers/gpu/drm/i915/display/intel_pps.c:769 intel_pps_on_unlocked+0x1ef/0x200 [i915] [i915] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | duk.bekema | ||||
| 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: | 34 | CC: | ajax, jglisse, k.a.szmit, kernel-maint, ttaylor, xgl-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/90f40f695a75419ccef6cf0a3502109ce79174ad | ||||||
| Whiteboard: | abrt_hash:240c5439cab21a0e0e106eb75533934bd00881ac;VARIANT_ID=workstation; | ||||||
| Fixed In Version: | Doc Type: | --- | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-06-07 20:01:00 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
duk.bekema
2021-07-22 06:49:48 UTC
Created attachment 1804362 [details]
File: dmesg
Description of problem: I had just logged into the system using gnome desktop. I had the slack desktop app running, and maybe chrome. The system was otherwise idle. I was not using the mouse or keyboard because I was checking email on my other computer. Suddenly the screen went black and it presented the graphical login display again. Version-Release number of selected component: kernel-core-5.13.10-200.fc34 Additional info: reporter: libreport-2.15.2 cmdline: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-5.13.10-200.fc34.x86_64 root=UUID=afc54803-2507-4b86-b88a-fe9bde26c7b9 ro resume=/dev/mapper/luks-092b9c1f-4c7c-48a7-b70e-124fcea8de14 rd.lvm.lv=fedora_mm248056/root rd.luks.uuid=luks-9d1a5513-a460-427b-aa37-5f003da0d692 rd.md.uuid=0a9cec7f:9a3e1683:9397e5a7:46024945 rd.lvm.lv=fedora_mm248056/swap rd.luks.uuid=luks-092b9c1f-4c7c-48a7-b70e-124fcea8de14 rhgb quiet dis_ucode_ldr crash_function: intel_pps_on kernel: 5.13.10-200.fc34.x86_64 runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 6 PID: 303 at drivers/gpu/drm/i915/display/intel_pps.c:771 intel_pps_on_unlocked+0x1e3/0x1f0 [i915] Modules linked in: raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx hid_multitouch i915 rtsx_pci_sdmmc nouveau mmc_core drm_ttm_helper ttm i2c_algo_bit mxm_wmi drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel cec ghash_clmulni_intel e1000e drm serio_raw rtsx_pci nvme nvme_core i2c_hid_acpi i2c_hid video pinctrl_cannonlake wmi r8152 mii target_core_mod fuse CPU: 6 PID: 303 Comm: kworker/6:2 Not tainted 5.13.10-200.fc34.x86_64 #1 Hardware name: Dell Inc. Precision 7530/0425K7, BIOS 1.13.1 04/28/2020 Workqueue: events output_poll_execute [drm_kms_helper] RIP: 0010:intel_pps_on_unlocked+0x1e3/0x1f0 [i915] Code: ff 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 35 e8 d7 ca 49 89 e8 44 89 f1 4c 89 e2 48 89 c6 48 c7 c7 80 85 b0 c0 e8 d8 8d 13 cb <0f> 0b e9 3c fe ff ff 66 0f 1f 44 00 00 0f 1f 44 00 00 41 54 55 53 RSP: 0018:ffffb672c0463a28 EFLAGS: 00010292 RAX: 0000000000000042 RBX: ffff9fb390800160 RCX: 0000000000000027 RDX: ffff9fbafc598a08 RSI: 0000000000000001 RDI: ffff9fbafc598a00 RBP: ffff9fb39032f0b0 R08: 0000000000000000 R09: ffffb672c0463860 R10: ffffb672c0463858 R11: ffffffff8cd468c8 R12: ffff9fb381e2e9a0 R13: ffff9fb38fa60000 R14: 000000000000005e R15: ffff9fb390800000 FS: 0000000000000000(0000) GS:ffff9fbafc580000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdaf3c49000 CR3: 0000000325c10002 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: intel_pps_on+0x47/0x70 [i915] intel_ddi_pre_enable+0x4ab/0xa10 [i915] intel_encoders_pre_enable+0x7e/0x90 [i915] hsw_crtc_enable+0x86/0x680 [i915] intel_enable_crtc+0x59/0x70 [i915] skl_commit_modeset_enables+0x272/0x560 [i915] intel_atomic_commit_tail+0x469/0x1350 [i915] intel_atomic_commit+0x323/0x3a0 [i915] drm_client_modeset_commit_atomic+0x1c4/0x200 [drm] drm_client_modeset_commit_locked+0x56/0x150 [drm] drm_client_modeset_commit+0x24/0x40 [drm] drm_fb_helper_set_par+0xa5/0xd0 [drm_kms_helper] drm_fb_helper_hotplug_event.part.0+0xa3/0xc0 [drm_kms_helper] output_poll_execute+0x8b/0x1e0 [drm_kms_helper] process_one_work+0x1ec/0x380 worker_thread+0x53/0x3e0 ? process_one_work+0x380/0x380 kthread+0x127/0x150 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed. |