All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Yxian.Yao <yxianyao@126.com>
Cc: <xenomai@lists.linux.dev>
Subject: Re: some kernel exceptions
Date: Mon, 10 Oct 2022 18:37:04 +0200	[thread overview]
Message-ID: <f4daac37-68d6-7c76-a58b-5d28c4c96978@siemens.com> (raw)
In-Reply-To: <16329230.7168.183c284db3e.Coremail.yxianyao@126.com>

On 10.10.22 17:30, Yxian.Yao wrote:
> 
> Hi Jan,
> 
>> The warnings start with perf, but I might have been too quick to shoot
>> at it. The real issue is definitely the page fault. You don't have a
>> stack backtrace for the first one?
> 
> No, these are the last messages that the kernel outputs. 
> The second exception is the same as the first one?
> The logs are printed with "BUG: unable to handle kernel painting request at 00000000000a22e8"
> 

The issue is that you generally cannot trust succeeding BUG messages
after the first one. They may point into the wrong direction, not to the
root cause.

> 
>> Also note that your kernel is not just old /wrt to its base version
>> (4.19), it's also not using the latest I-pipe patch for that
>> (ipipe-core-4.19.252-cip78-x86-23).
> 
> What is the difference between cip and no cip on ipipe core?
> 

At some point, we moved from 4.19-LTS to 4.19-CIP as baseline for the
I-pipe patches as the latter kernel will live longer (10 instead of 6
years). No further development was done on the 4.19-LTS branch you are
sitting on, which is also missing some bug fixes to I-pipe since then.

> 
>> The key switches are warned about. But that does not exclude that some
>> sleeping bug is only surfaced by turning on or off some feature that
>> others usually do not touch.
> 
> 
> How to further determine what caused it?

Hard to say yet. Please re-try with the latest 4.19-ipipe release if
possible and also check if something changes positively when you use the
config from xenomai-images.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2022-10-10 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 13:31 some kernel exceptions Yxian.Yao
2022-10-10 13:41 ` Jan Kiszka
2022-10-10 14:09   ` Yxian.Yao
2022-10-10 14:13     ` Jan Kiszka
2022-10-10 14:37       ` Yxian.Yao
2022-10-10 14:54         ` Jan Kiszka
2022-10-10 15:30           ` Yxian.Yao
2022-10-10 16:37             ` Jan Kiszka [this message]
2022-12-26  7:37 Yxian.Yao
2022-12-27  9:36 ` Florian Bezdeka
2022-12-27  9:48   ` Bezdeka, Florian
2022-12-27 10:07   ` Bezdeka, Florian

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=f4daac37-68d6-7c76-a58b-5d28c4c96978@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    --cc=yxianyao@126.com \
    /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.