Bug 1989204 - [abrt] __hrtimer_run_queues: WARNING: CPU: 13 PID: 0 at kernel/time/timer.c:1740 __run_timers.part.0+0xb8/0x220
Summary: [abrt] __hrtimer_run_queues: WARNING: CPU: 13 PID: 0 at kernel/time/timer.c:1...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7fa12206b0026f7ffd4d0db2895...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-02 16:22 UTC by hx
Modified: 2021-11-30 19:03 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 19:03:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (115.79 KB, text/plain)
2021-08-02 16:23 UTC, hx
no flags Details

Description hx 2021-08-02 16:22:58 UTC
Additional info:
reporter:       libreport-2.15.2
WARNING: CPU: 13 PID: 0 at kernel/time/timer.c:1740 __run_timers.part.0+0xb8/0x220
Modules linked in: sunrpc squashfs loop snd_usb_audio iwlmvm snd_hda_codec_hdmi snd_usbmidi_lib snd_hda_intel snd_rawmidi mc snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec mac80211 snd_hda_core intel_rapl_msr intel_rapl_common joydev btusb intel_tcc_cooling snd_hwdep x86_pkg_temp_thermal btrtl libarc4 intel_powerclamp snd_seq btbcm snd_seq_device snd_pcm btintel iwlwifi ee1004 coretemp mei_hdcp iTCO_wdt intel_pmc_bxt iTCO_vendor_support cfg80211 snd_timer snd kvm_intel bluetooth rfkill kvm soundcore mei_me thunderbolt i2c_i801 i2c_smbus mei irqbypass rapl pcspkr intel_cstate intel_uncore wmi_bmof mxm_wmi acpi_pad acpi_tad binfmt_misc zram ip_tables usb_storage amdgpu drm_ttm_helper ttm iommu_v2 gpu_sched i2c_algo_bit drm_kms_helper atlantic cec crct10dif_pclmul crc32_pclmul crc32c_intel drm igc ghash_clmulni_intel macsec video wmi pinctrl_tigerlake fuse
CPU: 13 PID: 0 Comm: swapper/13 Not tainted 5.13.5-100.fc33.x86_64 #1
Hardware name: Micro-Star International Co., Ltd. MS-7D03/MEG Z590 GODLIKE (MS-7D03), BIOS A.20 06/22/2021
RIP: 0010:__run_timers.part.0+0xb8/0x220
Code: 41 83 c6 01 4c 89 d6 a8 07 75 0f 83 c2 40 48 c1 e8 03 81 fa 40 02 00 00 75 b7 49 8b 47 10 45 85 f6 75 51 41 80 7f 24 00 75 02 <0f> 0b 48 83 c0 01 4c 89 ff 49 89 47 10 e8 76 eb ff ff 49 89 47 18
RSP: 0018:ffffb183803f4f08 EFLAGS: 00010046
RAX: 00000000fffc3380 RBX: 0000000000000001 RCX: 000000000000008e
RDX: 0000000000000080 RSI: ffffb183803f4f10 RDI: ffff98728bb5ae00
RBP: 0000000000000100 R08: 0000000be9c41fee R09: ffff98728bb5ae28
R10: 0000000000000282 R11: ffffffff90c060c0 R12: 0000000000000002
R13: dead000000000122 R14: 0000000000000000 R15: ffff98728bb5ae00
FS:  0000000000000000(0000) GS:ffff98728bb40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000562c98154020 CR3: 00000005f3c10005 CR4: 00000000007706e0
PKRU: 55555554
Call Trace:
 <IRQ>
 ? __hrtimer_run_queues+0x129/0x250
 ? ktime_get+0x35/0xa0
 ? lapic_next_deadline+0x28/0x30
 run_timer_softirq+0x26/0x50
 __do_softirq+0xcc/0x28f
 __irq_exit_rcu+0xcc/0x100
 sysvec_apic_timer_interrupt+0x72/0x90
 </IRQ>
 asm_sysvec_apic_timer_interrupt+0x12/0x20
RIP: 0010:cpuidle_enter_state+0xc7/0x350
Code: 8b 3d a5 3d 69 70 e8 98 68 79 ff 49 89 c5 0f 1f 44 00 00 31 ff e8 c9 80 79 ff 45 84 ff 0f 85 fa 00 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 06 01 00 00 49 63 c6 4c 2b 2c 24 48 8d 14 40 48 8d
RSP: 0018:ffffb18380183eb0 EFLAGS: 00000246
RAX: ffff98728bb6ac80 RBX: 0000000000000002 RCX: 000000000000001f
RDX: 0000000000000000 RSI: 0000000022a1cd05 RDI: 0000000000000000
RBP: ffffd1837fb40000 R08: 0000000be9c41b1f R09: 0000000000000018
R10: 000000000000833e R11: 0000000000002b9e R12: ffffffff90e5c500
R13: 0000000be9c41b1f R14: 0000000000000002 R15: 0000000000000000
 cpuidle_enter+0x29/0x40
 do_idle+0x1d7/0x280
 cpu_startup_entry+0x19/0x20
 secondary_startup_64_no_verify+0xc2/0xcb

Comment 1 hx 2021-08-02 16:23:04 UTC
Created attachment 1810218 [details]
File: dmesg

Comment 2 Ben Cotton 2021-11-04 13:49:08 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2021-11-04 14:18:31 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2021-11-04 15:16:14 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2021-11-30 19:03:08 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. If you experience problems, please add a comment to this
bug.

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.