xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: ivan@rtxi.org
To: xenomai@lists.linux.dev
Subject: Troubleshooting x86_64 evl bootup
Date: Thu, 04 Jan 2024 13:34:58 -0500	[thread overview]
Message-ID: <37d6d286847eb0126c938a1c5826ed13@rtxi.org> (raw)

Hello all!

I have been trying to upgrade a desktop that used to have Xenomai 3 + 
IPIPE to the new EVL system. Compilation is successful but the kernel 
hangs during boot with an rcu error message followed by a stack dump:

rcu: unless rcu_preempt kthread gets sufficient CPU time, OOM is now 
expected behavior.
...
Call Trace:
<TASK>
__schedule+0xd76/0x1950
? sched_clock+0x9/0x10
? sched_clock_local+0x17/0x90
? inband_irq_save+0xe/Ux30
schedule+0x69/0x110
schedule_timeout+0x19a/8x2f0
? del_timer_sync+0x50/0x50
rcu_gp_fqs_loop+0xf9/0x470
rcu_gp_kthread+0x15a/0x210
? rcu_gp_init+0x640/0x640
kthread+0x12a/0x150
? set_kthread_struct+0x50/0×50
ret_fron_fork+0x22/0x30
</TASK>

After some digging, the evl page references possible issue as "loosing 
the tick device" but don't know how to confirm whether that is the case 
here. This computer uses an AMD Phenom II X6 1035T processor and The 
kernel branch used from linux-evl repo is "v5.15.y-evl-rebase". Any 
suggestions on how to track down the issue?

Regards,
-Ivan F. Valerio

             reply	other threads:[~2024-01-04 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 18:34 ivan [this message]
2024-01-17 23:22 ` Troubleshooting x86_64 evl bootup ivan
2024-01-18  6:51   ` Jan Kiszka
2024-01-19 21:06     ` ivan
2024-01-22 13:43       ` Philippe Gerum
2024-01-22 19:40       ` ivan
2024-01-25  9:41         ` Jan Kiszka
2024-01-25 23:35         ` ivan
2024-01-26  5:50           ` Chen, Hongzhan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37d6d286847eb0126c938a1c5826ed13@rtxi.org \
    --to=ivan@rtxi.org \
    --cc=xenomai@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).