All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Zimmermann <s.zimmermann@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] fata: removing non-linked element...
Date: Thu, 22 Feb 2007 16:49:26 +0100	[thread overview]
Message-ID: <45DDBB86.2080105@domain.hid> (raw)
In-Reply-To: <45DD9F8E.6070708@domain.hid>

Jan Kiszka schrieb:
> Stephan Zimmermann wrote:
>> Hm, updated my machines to 2.6.20 and 2.3.0 rev 2222. I still see ( less
>> frequent?) some backtraces occuring on my console, either during reboot
>> or sometimes when running the testprogram and reloading the modules.(see
>> dmesg snippet below) The Celeron M still crashes often totally.
>>
>> My main-application still freezes the SMP mashines if I have 'priority
>> coupling' enabled in kernel-config. Using trunk makes things even worse.
>> The pc will crash during startup of my app, the testapp I sendt you
>> works, but i can not shutdown the pc afterwards, because it freezes
>> completely when terminating kdm.
>>
>> Stephan
>>
>>
>>
>> dmesg tells me the following (2.3.0.2222, 2.6.20, SMP):
> 
> Latest I-pipe version?

Kernel was freshly patched with:

./ksrc/arch/i386/patches/adeos-ipipe-2.6.20-i386-1.7-02.patch

the one from svn rev. 2222

> 
>> --snip--
>> Bad page state in process 'kswapd0'
>> page:c17f3060 flags:0x80010408 mapping:00000000 mapcount:0 count:0
>> Trying to fix it up, but a reboot is needed
> 
> Something is corrupting kernel memory.
> 
> I did some remark on your test, let's get back to it: You are running
> the test at 100 kHz. That /may/ have side-effects like overload, or it
> might actually trigger some stack overrun. Did you enable the stack
> checks? Can you confirm the problem occurs also at slower tick rates?

Test was run at 10KHz, but stack-debugging wasn't on, I will repeat it 
and post again...

> Jan
> 



  reply	other threads:[~2007-02-22 15:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 12:12 [Xenomai-help] fata: removing non-linked element Stephan Zimmermann
2007-02-09 12:28 ` Jan Kiszka
2007-02-09 14:04   ` Stephan Zimmermann
2007-02-13 13:36   ` Stephan Zimmermann
2007-02-13 13:42   ` Stephan Zimmermann
2007-02-13 14:07     ` Jan Kiszka
2007-02-13 14:25       ` Philippe Gerum
2007-02-13 14:28         ` Jan Kiszka
2007-02-13 14:47           ` Philippe Gerum
2007-02-13 16:55           ` Philippe Gerum
2007-02-13 18:17             ` Jan Kiszka
2007-02-13 18:58               ` Philippe Gerum
2007-02-16 12:12                 ` Stephan Zimmermann
2007-02-16 17:06                   ` Jan Kiszka
2007-02-16 17:58                     ` Jan Kiszka
2007-02-16 18:15                       ` Philippe Gerum
2007-02-16 18:25                         ` Jan Kiszka
2007-02-16 18:34                           ` Philippe Gerum
2007-02-16 18:38                             ` Jan Kiszka
2007-02-16 18:47                               ` Philippe Gerum
2007-02-22 13:27                                 ` Stephan Zimmermann
2007-02-22 13:50                                   ` Jan Kiszka
2007-02-22 15:49                                     ` Stephan Zimmermann [this message]
2007-02-16 17:11                   ` Jan Kiszka
2007-02-09 13:44 ` Gilles Chanteperdrix
2007-02-09 14:08   ` Stephan Zimmermann

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=45DDBB86.2080105@domain.hid \
    --to=s.zimmermann@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.