All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Karch <JKarch@domain.hid>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai scheduling while atomic bug--debugging parameters
Date: Thu, 10 Dec 2009 08:30:07 -0800	[thread overview]
Message-ID: <843773D242212C4882D4EDFFBF665F7F0155A93AAD@FW-SBS.fw.local> (raw)
In-Reply-To: <4B20C5DE.2040606@domain.hid>

Jan,

Our program ran without interruption last night with no bug, except it appears one still exists possibly regarding either ethernet (Intel e100), sshd, nfsd, or as a result of running top.  It seems excessive network requests and calls to top and dmesg can trigger it.

Today I will recompile the kernel with all debugging options enabled,  make the system run until the bug occurs, send you that .config file as well as the current .config that still crashes on occasion (though the xenomai application runs rock solid in spite of the linux scheduling while atomic bugs). since the logs may be big, is there an ftp I can send them to or should I email those directly?

Thank you,

Joshua Karch


________________________________________
From: Jan Kiszka [jan.kiszka@domain.hid]
Sent: Thursday, December 10, 2009 1:56 AM
To: Josh Karch
Cc: xenomai@xenomai.org
Subject: Re: Xenomai scheduling while atomic bug--debugging   parameters

Josh Karch wrote:
> Hi Jan,
>
> I did a complete make mrproper on the system and recompiled without debugging parameters,

mrproper is not required, the kernel is supposed to detect what needs to
be rebuild based on the .config changes.

> which took a few hours on the machine because the modules take up a lot. I probably should prune all unused modules (eg video, pcmcia, sound, etc) that I'm not using.

Yep.

>
> I guess I will have to back up my current /lib/modules/2.6.30.8 when I recompile with all debug support for that experiment, grab the data, and then get that to you once my testing (hopefully) is successful on this change without kernel debugging options.
>

Gilles already said this: We also need your .config to check if you are
stressing an uncommon configuration or if we are even able to reproduce
it locally.

Jan

--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-12-10 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 16:56 [Xenomai-help] Xenomai scheduling while atomic bug--debugging parameters Josh Karch
2009-12-09 17:45 ` Gilles Chanteperdrix
2009-12-09 18:04   ` Josh Karch
2009-12-09 18:42     ` Jan Kiszka
2009-12-09 20:34       ` Josh Karch
2009-12-10  9:56         ` Jan Kiszka
2009-12-10 16:30           ` Josh Karch [this message]
2009-12-11  9:43             ` Jan Kiszka
2009-12-11 16:45               ` Josh Karch
2009-12-14 16:33               ` Josh Karch

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=843773D242212C4882D4EDFFBF665F7F0155A93AAD@FW-SBS.fw.local \
    --to=jkarch@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.