All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: JerryJun <jerryjun123@163.com>
Cc: xenomai <xenomai@lists.linux.dev>
Subject: Re: NX-protected page
Date: Thu, 25 Jan 2024 10:50:17 +0100	[thread overview]
Message-ID: <87ca0f83-bb2f-49fd-8e30-8873778cd8a9@web.de> (raw)
In-Reply-To: <3ce13f2b.183be.18d2f264758.Coremail.jerryjun123@163.com>

On 22.01.24 04:10, JerryJun wrote:
> hi, xenomai:
>
> we use a small xenomai application reproduct NX-protected page question , it will appear within 12 hours. please give me a hint; 
>
> the application is implemented to create multiple RT task which set affinity of the 2 cpu, prio 90 and manual bootstrap , perform FFT only occuiped CPU with rt_sleep, which be killed a few seconds later. 
>
> the kernel oops appear when kill the application.
>

What exactly needs to be done to reproduce the issue with your code?

Also, does the hardware play a role, or can you reproduce it in a
qemu-amd64 instance as well?

Already checked if there are differences when using [1] from xenomai-images?

Thanks,
Jan

[1]
https://source.denx.de/Xenomai/xenomai-images/-/blob/master/recipes-kernel/linux/files/amd64_defconfig?ref_type=heads

  reply	other threads:[~2024-01-25  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  3:10 NX-protected page JerryJun
2024-01-25  9:50 ` Jan Kiszka [this message]
2024-01-31  7:25   ` JerryJun
2024-02-01  7:09     ` Jan Kiszka
2024-02-02  6:49       ` Jan Kiszka
2024-02-02  7:49         ` JerryJun
2024-02-02  8:37           ` Jan Kiszka
2024-02-02 10:03             ` JerryJun
2024-02-26 14:34             ` JerryJun
2024-04-10  7:46               ` Kowalsky, Clara
2024-04-15 23:37                 ` JerryJun

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=87ca0f83-bb2f-49fd-8e30-8873778cd8a9@web.de \
    --to=jan.kiszka@web.de \
    --cc=jerryjun123@163.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.