path: root/testsuites/PROBLEMS
diff options
authorJoel Sherrill <>1998-10-05 21:26:07 +0000
committerJoel Sherrill <>1998-10-05 21:26:07 +0000
commit711a2a113395e4801cf82adbcb70990e5eeddc65 (patch)
treee9575dc524bdc6645ff07ae33f193d035dd2200c /testsuites/PROBLEMS
parent41a890a381cec2a275ec5b7f9b3d4e1a34f47624 (diff)
New file based on information from Eric Norum <>.
Diffstat (limited to 'testsuites/PROBLEMS')
1 files changed, 42 insertions, 0 deletions
diff --git a/testsuites/PROBLEMS b/testsuites/PROBLEMS
new file mode 100644
index 0000000000..6f3e2920be
--- /dev/null
+++ b/testsuites/PROBLEMS
@@ -0,0 +1,42 @@
+# $Id$
+The tests were designed to operate in a very controlled environment. If
+one uses interrupt-driven console output, then tasks will block unexpectedly
+when a buffer filles and interrupts will perturb with the task execution order.
+The tmtests should only be run with all interrupt sources disabled using
+polled IO.
+The following is a list of reported failures from running the tests on
+a board with interrupt driven console IO. These problems do not
+occur when using polled IO.
+tm03, tm04, tm05, tm07, tm11, tm12, tm13, tm14, tm15, tm16, tm17,
+tm19, tm22, tm23, tm24 - All hit my breakpoint at
+tm20, tm27 - hang in middle of tests.
+tm26 - hangs at end of tests.
+sp02 - Gets through some tests, then attempts to execute code at
+location 0.
+sp04 - hangs at end of tests.
+sp06 - rtems_task_restart of TA3 FAILED -- expected (0) got (4)
+sp07, sp14 - hang in middle of tests
+sp13, sp15 - terminate properly, but output at end is missing.
+sp16 - _Internal_error_Occurred.
+sp19 - rtems_clock_get FAILED -- expected (0) got (11), and hangs in
+middle of test.
+cpuuse - hangs in middle of tests
+malloctest - prints nothing
+psx05 - Init: pthread_mutex_init - EINVAL (bad protocol)
+failed assertion `status == EBUSY'
+N\: pthread_mutex_init - EINVAL (bad priority ceiling)