0

I am running Ubuntu 20.04 on Virtual Box. Host machine is windows 10. It is Dell G3 15 machine. Now when I leave the system idle for 15-20 minutes, I see following message on VirtualBox Ubuntu

“echo O > Y/proc’sys/’kernel/hung_task_timeout_secs'' disables this message.
ata3.o00: exception Emask Oxo SAct OxO SErr OxO action Ox6 frozen
ata3.00: failed command: FLUSH CACHE EXT
ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 31
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask Ox4 (timeout)
ata3.o00: status: {£ DRDY }
rcu: INFO: rcu_sched self-detected stall on CPU
rou: $2-...!: €1 GPs behind) idle=ab2/0/0x1 soft irq=100716/100718 fqs=0
rcu: rcu_sched kthread starved for 349603 jiffies! 2438153 fOx0O0 RCU_GP_WAIT_FQS(S) ->
cpu=1
rcu: $Unless rcu_sched kKthread gets sufficient CPU time, OOM is now expected behavior
rcu: RCU grace-period kthread stack dump:
rcu: INFO: rcu_sched self-detected stall on CPU
rou: $2-...!: €1 GPs behind) idle=ab2/0/0x1 soft irq=100716/100718 fqs=1
rcu: INFO: rcu_sched self—-detected stall on CPU
rou: $2-...!: €S GPs behind) idle=6S2/0/0x1 soft irq=101241/101242 faqs=o
rcu: rcu_sched kthread starved for 399886 jiffies! 2439361 fOx0O0 RCU_GP_WAIT_FQS(S) ->
oa a] Om I
rcu: INFO: rcu_sched self-detected stall on CPU
rcu: $Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior
rcu: RCU grace-period kthread stack dump:
rou: $4-...0: (€1 GPs behind) idle=76a/0/0x1 soft irq=91288/91289 faqs=2
ata3.00: exception Emask Oxo SAct OxO SErr OxO action Ox6 frozen
ata3.00: failed command: FLUSH CACHE EXT
ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 15
res 40/00: ff :00:00:00/00:00:00:00:00/00 Emask Ox4d (timeout)
ata3.o00: status: {£ DRDY 3}
rcu: INFO: rcu_sched self-detected stall on CPU
rou: $1-...!: (€6 GPs behind) idle=7f6/0/0x1 soft irq=103922/103923 fqs=Oo
rcu: rcu_sched kKthread starved for 899650 jiffies! 2439697 fOx0O0 RCU_GP_WAIT_FQS(S) ->
cpu=S
rcu: $Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior
rcu: RCU grace-period kthread stack dump:

Also adding the image here: self-detected stall on cpu and the only way to solve is to close the virtual box and start again. Saw information about this issue: https://helpful.knobs-dials.com/index.php/INFO:_task_blocked_for_more_than_120_seconds.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.