Bug 2227439 - [abrt] default_idle: watchdog: BUG: soft lockup - CPU#0 stuck for 25s! [swapper/0:0]
Summary: [abrt] default_idle: watchdog: BUG: soft lockup - CPU#0 stuck for 25s! [swapp...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 37
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:5718cccbefdc36cc05129e4339e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-29 17:21 UTC by Sylvain Arth
Modified: 2024-01-15 12:20 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-01-15 12:20:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (267.02 KB, text/plain)
2023-07-29 17:21 UTC, Sylvain Arth
no flags Details

Description Sylvain Arth 2023-07-29 17:21:26 UTC
Additional info:
reporter:       libreport-2.17.11
watchdog: BUG: soft lockup - CPU#0 stuck for 25s! [swapper/0:0]
RSP: 0018:ffffffff85003e88 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffffff85010900 RCX: ffffffffffffffff
RDX: 4000000000000000 RSI: 0000000000000082 RDI: 00000000b8cd41b4
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000030 R12: 0000000000000000
R13: 0000000000000000 R14: ffffffff85010038 R15: 0000000000000000
 default_idle+0x9/0x20
 default_idle_call+0x2c/0xe0
 do_idle+0x1e9/0x260
 cpu_startup_entry+0x1d/0x20
 rest_init+0xce/0xd0
 arch_call_rest_init+0xe/0x30
 start_kernel+0x78a/0xb90
 secondary_startup_64_no_verify+0xe5/0xeb
 </TASK>
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 	0-...!: (459 ticks this GP) idle=41cc/1/0x4000000000000000 softirq=86500048/86500048 fqs=0
rcu: 	(t=60122 jiffies g=98552257 q=64 ncpus=1)
rcu: rcu_preempt kthread timer wakeup didn't happen for 60119 jiffies! g98552257 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: 	Possible timer handling issue on cpu=0 timer-softirq=681411965
rcu: rcu_preempt kthread starved for 60122 jiffies! g98552257 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
rcu: 	Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt     state:I stack:0     pid:16    ppid:2      flags:0x00004000
Call Trace:

Comment 1 Sylvain Arth 2023-07-29 17:21:32 UTC
Created attachment 1980617 [details]
File: dmesg

Comment 2 Aoife Moloney 2023-11-23 01:48:27 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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 '37'.

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 37 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 3 Aoife Moloney 2024-01-15 12:20:00 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 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.