From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: Cortex-M3 kernel failing certain kernel tests.
Date: Thu, 19 Sep 2013 19:30:00 -0000 [thread overview]
Message-ID: <l1fjb3$bl0$1@ger.gmane.org> (raw)
In-Reply-To: <l1cnbm$2q7$1@ger.gmane.org>
On 2013-09-18, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> I'm testing an eCos port to an NXP Cortex-M3 part (very similar to the
> existing LPC17xx port), and I'm stuck with some failing kernel tests:
>
> mutex3
> kmutex3
> stress_threads
> dhrystone
[...]
> These tests are run using a very minimal build with the mlqueue
> scheduler (no io device drivers, no network, no file support, no
> timeslicing).
It turns out that stress_threads and dhrystone both require "printf"
stdio support to work.
Unfortunately, the CDL for the kernel tests doesn't seem to catch this
missing dependancy. They both compile and link fine, but end up
calling cyg_io_write() with a NULL io handle. After adding a couple
#define's to make them use diag_printf and diag_sprintf,
stress_threads and dhrystone both pass.
Even though it passes, I think there's still a problem with the
stress_threads test. It prints out a series of state dumps with
messages claiming they're one minute intervals, but they're only a few
seconds. I'm guessing that stress_threads contains a hidden
assumption that the clock tick is 10ms and mine is actually 1ms.
The mutex3 and kmutex3 tests still both fail the same as they did
before...
> * mutex3 and kmutex3 both fail test number 24 and then hang:
>
> ----- [24] New Cycle: 0x60, Threads 1a inactive, 2a run late, 3a run late -----
> INFO:<Thread 1 running>
> INFO:<Thread 2 running>
> INFO:<Extra thread 2a running>
> INFO:<Thread 3 running>
> INFO:<Extra thread 3a running>
> INFO:<Thread 1 exit>
> INFO:<Checking priority scheme: dynamic-default-inherit>
> INFO:<Extra thread 2a resumed>
> INFO:<Extra thread 2a locked>
> INFO:<Extra thread 2a unlocked>
> INFO:<Extra thread 2a exiting>
> INFO:<Thread 3 exit>
> INFO:<Extra thread 3a resumed>
> INFO:<Extra thread 3a locked>
> INFO:<EFAIL:<Extra thread did not run> Line: 346, File: [...]kernel/current/tests/mutex3.cxx
> <hang>
>
> ----- [24] New Cycle: 0x60, Threads 1a inactive, 2a run late, 3a run late -----
> INFO:<Thread 1 running>
> INFO:<Thread 2 running>
> INFO:<Extra thread 2a running>
> INFO:<Thread 3 running>
> INFO:<Extra thread 3a running>
> INFO:<Thread 1 exit>
> INFO:<Checking priority scheme: dynamic-default-inherit>
> INFO:<Extra thread 2a resumed>
> INFO:<Extra thread 2a locked>
> INFO:<Extra thread 2a unlocked>
> INFO:<Extra thread 2a exiting>
> INFO:<Thread 3 exit>
> INFO:<Extra thread 3a resumed>
> INFO:<Extra thread 3a locked>
> INFO:<EFAIL:<Extra thread did not run> Line: 353, File: [...]kernel/current/tests/kmutex3.c
> <hang>
--
Grant Edwards grant.b.edwards Yow! I'm GLAD I
at remembered to XEROX all
gmail.com my UNDERSHIRTS!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-09-19 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 17:20 [ECOS] " Grant Edwards
2013-09-19 19:30 ` Grant Edwards [this message]
2013-09-19 20:37 ` [ECOS] " Grant Edwards
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='l1fjb3$bl0$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=ecos-discuss@ecos.sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).