Bug 2212346
| Summary: | [abrt] tb_ring_start: WARNING: CPU: 7 PID: 654 at drivers/thunderbolt/nhi.c:137 ring_interrupt_active+0x243/0x2d0 [thunderbolt] [thunderbolt] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | clobrano | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 38 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, clobrano, hdegoede, hpa, jarodwilson, josef, kernel-maint, lgoncalv, linville, lszubowi, masami256, mchehab, michael.kalisz, omosnacek, ptalbert, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/029817ec2aec60073b3a3d9bd05631ca6ced590 | ||||||
| Whiteboard: | abrt_hash:bfcf14539e31cb7767d0d0af3a7a7497a4fd5327;VARIANT_ID=workstation; | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2024-05-22 11:18:04 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
clobrano
2023-06-05 11:11:38 UTC
Created attachment 1969038 [details]
File: dmesg
Possibly a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2211983 Description of problem: Walked away from the laptop for a couple of minutes, it was idle for the most part. Came back to a blank screen, and sysmem was locked. 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: ring_interrupt_active reason: WARNING: CPU: 6 PID: 87512 at drivers/thunderbolt/nhi.c:137 ring_interrupt_active+0x243/0x2d0 [thunderbolt] [thunderbolt] type: Kerneloops cmdline: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.3.8-200.fc38.x86_64 root=UUID=4dedf75c-0a55-4a62-b479-13211f76d7c8 ro rootflags=subvol=root rd.luks.uuid=luks-5625b966-a12c-4738-b0a8-462c2ea694f4 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 package: kernel-core-6.3.8-200.fc38 runlevel: N 5 comment: Walked away from the laptop for a couple of minutes, it was idle for the most part. Came back to a blank screen, and sysmem was locked. Truncated backtrace: #1 [TASK] ? ring_interrupt_active in thunderbolt #2 [TASK] ? __warn #3 [TASK] ? ring_interrupt_active in thunderbolt #4 [TASK] ? report_bug #5 [TASK] ? prb_read_valid #6 [TASK] ? handle_bug #7 [TASK] ? exc_invalid_op #8 [TASK] ? asm_exc_invalid_op #9 [TASK] ? ring_interrupt_active in thunderbolt #10 [TASK] ? ring_interrupt_active in thunderbolt #11 [TASK] tb_ring_start in thunderbolt #12 [TASK] tb_ctl_start in thunderbolt #13 [TASK] ? __pfx_pci_pm_runtime_resume #14 [TASK] tb_domain_runtime_resume in thunderbolt #15 [TASK] __rpm_callback #16 [TASK] ? __pfx_pci_pm_runtime_resume #17 [TASK] rpm_callback #18 [TASK] ? __pfx_pci_pm_runtime_resume #19 [TASK] rpm_resume #20 [TASK] ? pcie_pme_work_fn #21 [TASK] pm_runtime_work #22 [TASK] ? __pfx_worker_thread #23 [TASK] ? __pfx_kthread #24 [TASK] ret_from_fork Description of problem: Happened upon waking up from suspend. Lenovo Thinkpad T14s (was connected to a Lenovo Thunderbolt 4 dock while suspended). Version-Release number of selected component: kernel-core-6.3.8-200.fc38 Additional info: reporter: libreport-2.17.11 kernel: 6.3.8-200.fc38.x86_64 comment: Happened upon waking up from suspend. Lenovo Thinkpad T14s (was connected to a Lenovo Thunderbolt 4 dock while suspended). cmdline: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.3.8-200.fc38.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.luks.uuid=luks-ada046ca-51fb-46cb-9336-298c2ba43d94 rd.lvm.lv=fedora/swap rhgb quiet reason: WARNING: CPU: 0 PID: 7 at drivers/thunderbolt/nhi.c:137 ring_interrupt_active+0x243/0x2d0 [thunderbolt] [thunderbolt] package: kernel-core-6.3.8-200.fc38 runlevel: N 5 type: Kerneloops crash_function: ring_interrupt_active Truncated backtrace: #1 [TASK] ? ring_interrupt_active in thunderbolt #2 [TASK] ? __warn #3 [TASK] ? ring_interrupt_active in thunderbolt #4 [TASK] ? report_bug #5 [TASK] ? prb_read_valid #6 [TASK] ? handle_bug #7 [TASK] ? exc_invalid_op #8 [TASK] ? asm_exc_invalid_op #9 [TASK] ? ring_interrupt_active in thunderbolt #10 [TASK] ? ring_interrupt_active in thunderbolt #11 [TASK] tb_ring_start in thunderbolt #12 [TASK] tb_ctl_start in thunderbolt #13 [TASK] ? __pfx_pci_pm_runtime_resume #14 [TASK] tb_domain_runtime_resume in thunderbolt #15 [TASK] __rpm_callback #16 [TASK] ? __pfx_pci_pm_runtime_resume #17 [TASK] rpm_callback #18 [TASK] ? __pfx_pci_pm_runtime_resume #19 [TASK] rpm_resume #20 [TASK] ? __pm_runtime_resume #21 [TASK] pm_runtime_work #22 [TASK] ? __pfx_worker_thread #23 [TASK] ? __pfx_kthread #24 [TASK] ret_from_fork (In reply to Ondrej Mosnáček from comment #4) > Description of problem: > Happened upon waking up from suspend. Lenovo Thinkpad T14s (was connected to > a Lenovo Thunderbolt 4 dock while suspended). Never mind... this was probably a different bug. (Laptop crashed while waking up from suspend, but actually nothing was written into logs. This backtrace is likely not related to that.) Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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. |