Kernel crashes on ARM64

Bug #2076388 reported by JHolder
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

Since I transitioned to apple silicon, I had to switch all my Linux VMs to ARM64 (using Parallels). Generally Linux has run well as you would expect, but I am seeing one persistent issue that followed me from 23.10 to 24.04:

About once a month there will be a kernel crash. After this crash, the date resets to around Sat Sep 30 05:43:15 PM CDT 2119

After this, it is not possible to reset the date, it results in an error. The only choice is to reboot. I can log in and make an orderly job of shutting everything down and rebooting. I haven't properly reported it yet, as I am usually in the middle of deadlines. I am hoping next time it happens, I have some downtime. The crash is this:

[3024774.492566] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[3024774.492586] rcu: 0-...!: (42 ticks this GP) idle=46dc/1/0x4000000000000002 softirq=16814401/16814403 fqs=0
[3024774.492595] rcu: (detected by 1, t=3001942682709 jiffies, g=24837729, q=204 ncpus=2)
[3024774.492603] Sending NMI from CPU 1 to CPUs 0:
[3024774.495842] NMI backtrace for cpu 0 skipped: idling at default_idle_call+0x68/0x1b8
[3024774.496609] rcu: rcu_preempt kthread timer wakeup didn't happen for 3002404477593 jiffies! g24837729 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
[3024774.496631] rcu: Possible timer handling issue on cpu=1 timer-softirq=34811404
[3024774.496638] rcu: rcu_preempt kthread starved for 3002404477596 jiffies! g24837729 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[3024774.496649] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
[3024774.496657] rcu: RCU grace-period kthread stack dump:
[3024774.496663] task:rcu_preempt state:I stack:0 pid:17 tgid:17 ppid:2 flags:0x00000008
[3024774.496667] Call trace:
[3024774.496668] __switch_to+0xbc/0xf0
[3024774.496672] __schedule+0x2a8/0x7b0
[3024774.496674] schedule+0x40/0x168
[3024774.496675] schedule_timeout+0xac/0x1e0
[3024774.496676] rcu_gp_fqs_loop+0x128/0x508
[3024774.496679] rcu_gp_kthread+0x150/0x188
[3024774.496680] kthread+0xf8/0x110
[3024774.496681] ret_from_fork+0x10/0x20
[3024774.496683] rcu: Stack dump where RCU GP kthread last ran:
[3024774.496690] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.8.0-36-generic #36-Ubuntu
[3024774.496691] Hardware name: Parallels International GmbH. Parallels ARM Virtual Machine/Parallels ARM Virtual Platform, BIOS 19.3.1 (54941) Thu, 25 Apr 202
[3024774.496692] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
[3024774.496693] pc : cpuidle_idle_call+0xb8/0x210
[3024774.496696] lr : cpuidle_idle_call+0x1a0/0x210
[3024774.496697] sp : ffff800083973e00
[3024774.496697] x29: ffff800083973e10 x28: 0000000000000000 x27: 0000000000000000
[3024774.496699] x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000
[3024774.496700] x23: 0000000000000000 x22: ffff0000c04da240 x21: ffff0000c04da240
[3024774.496701] x20: 0000000000000000 x19: 0000000000000000 x18: ffff800083935020
[3024774.496702] x17: 0000000000000000 x16: 0000000000000000 x15: 0000edc89995e7a0
[3024774.496703] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[3024774.496704] x11: 0000000000000000 x10: 865b25db6086752f x9 : ffff8000801fb6b4
[3024774.496705] x8 : ffff0000c04dc448 x7 : 0000000000000000 x6 : 0000000000000000
[3024774.496706] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
[3024774.496707] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
[3024774.496708] Call trace:
[3024774.496708] cpuidle_idle_call+0xb8/0x210
[3024774.496710] do_idle+0xb0/0x130
[3024774.496712] cpu_startup_entry+0x40/0x50
[3024774.496713] secondary_start_kernel+0xec/0x130
[3024774.496714] __secondary_switched+0xc0/0xc8

I have quite a bit of development experience, so I can run any tasks you need to further troubleshoot this.

Tags: bot-comment
JHolder (ubbugs11)
description: updated
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2076388/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.