From: Jan Kiszka <jan.kiszka@domain.hid>
To: Andreas Glatz <AndreasGlatz@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Kernel oops when reading /proc/xenomai/stats
Date: Wed, 10 Feb 2010 19:22:22 +0100 [thread overview]
Message-ID: <4B72F95E.3080402@domain.hid> (raw)
In-Reply-To: <245373446233674495BCA5CA2FC1EB173713B4D0CD@RCexchangeSVR1.ruggedcom.local>
Andreas Glatz wrote:
> Hi,
>
> I consistently get a Kernel oops when I do a 'cat /proc/xenomai/stats' after killing the Xenomai user-space application which registers for several interrupts.
>
> It's definitely Xenomai related as we are trying to allocate -784bytes of memory (~4GBytes) in nucleus/module.c:stat_seq_open() and we just hv 512MBytes :)
>
> It seems that xnintr_count gets decremented twice when killing the application. The application itself doesn't delete the RT_INTR. We rely on the cleanup which
> is done by the xenomai library (?) before exiting the application.
>
> Best regards,
> Andreas
>
>
> That's the kernel oops with additional debugging info (starts with 'HUHU' - see code below the oops):
>
> HUHU count=1 xnintr_count=-12
That's not good. What is your Xenomai version?
Does everything work fine if you application terminates normally and
deletes the rt_intr objects explicitly?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-02-10 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 18:11 [Xenomai-help] Kernel oops when reading /proc/xenomai/stats Andreas Glatz
2010-02-10 18:22 ` Jan Kiszka [this message]
2010-02-10 18:23 ` Andreas Glatz
2010-02-10 18:33 ` Jan Kiszka
2010-02-10 22:52 ` Andreas Glatz
2010-02-11 8:11 ` Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2010-02-12 23:36 Andreas Glatz
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=4B72F95E.3080402@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=AndreasGlatz@domain.hid \
--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.