All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lowell Gilbert <kludge@be-well.ilk.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: crash on accessing /proc/xenomai/sched/Â
Date: Wed, 30 Jan 2019 14:34:43 -0500	[thread overview]
Message-ID: <44va262b3g.fsf@be-well.ilk.org> (raw)
In-Reply-To: <e888a48e-9576-6353-25c1-361ae66a70e6@siemens.com> (Jan Kiszka's message of "Wed, 30 Jan 2019 10:37:39 +0100")

Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 29.01.19 22:06, Lowell Gilbert via Xenomai wrote:
>> I was trying to update to 3.0.8, and looking at stat or acct in the
>> sched branch of the proc tree gives me an instant kernel crash, usually
>> with a null pointer access from a bogus code address, although the
>> locations aren't always the same. This is without even having my kernel
>> module or application loaded.
>>
>> The system is a dual-core Cortex-A9.
>
> Does this patch happen to help?
>
> https://gitlab.denx.de/Xenomai/xenomai/commit/02500efff060c293a74fa4c914c19b8e1504b9a3

No. I didn't expect it to: I only hook interrupts with rtdm_irq_request() 

> Otherwise: Is your I-pipe patch from upstream or self-developed. I
> suspect the latter as your kernel claims to be LTSI-based.

I'm just using the  ipipe-core-4.14.71-arm-4.patch, with a couple of
very minor changes related to handling ARM errata. I compared the
original source tree to the official linux-4.14.71 release, and the
differences were minor. I can't seem to reproduce that now, though, so I
applied the official patch against the official linux-4.14.71 tree, and
still see the same panics. I'm going to try that again to make sure I'm
not crazy.

Be well.


      reply	other threads:[~2019-01-30 19:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 21:06 crash on accessing /proc/xenomai/sched/Â Lowell Gilbert
2019-01-30  9:37 ` Jan Kiszka
2019-01-30 19:34   ` Lowell Gilbert [this message]

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=44va262b3g.fsf@be-well.ilk.org \
    --to=kludge@be-well.ilk.org \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.org \
    /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.