source: rtems/testsuites/PROBLEMS @ 8c27637

4.104.114.84.9
Last change on this file since 8c27637 was 711a2a1, checked in by Joel Sherrill <joel.sherrill@…>, on Oct 5, 1998 at 9:26:07 PM

New file based on information from Eric Norum <eric@…>.

  • Property mode set to 100644
File size: 1.4 KB
Line 
1#
2#  $Id$
3#
4
5The tests were designed to operate in a very controlled environment.  If
6one uses interrupt-driven console output, then tasks will block unexpectedly
7when a buffer filles and interrupts will perturb with the task execution order.
8
9The tmtests should only be run with all interrupt sources disabled using
10polled IO.
11
12The following is a list of reported failures from running the tests on
13a board with interrupt driven console IO.  These problems do not
14occur when using polled IO.
15
16tm03, tm04, tm05, tm07, tm11, tm12, tm13, tm14, tm15, tm16, tm17, 
17tm19, tm22, tm23, tm24 - All hit my breakpoint at 
18_Internal_error_Occurred.
19
20tm20, tm27 - hang in middle of tests.
21tm26 - hangs at end of tests.
22
23sp02 - Gets through some tests, then attempts to execute code at 
24location 0.
25sp04 - hangs at end of tests.
26sp06 - rtems_task_restart of TA3 FAILED -- expected (0) got (4)
27sp07, sp14 - hang in middle of tests
28sp13, sp15 - terminate properly, but output at end is missing.
29sp16 - _Internal_error_Occurred.
30sp19 - rtems_clock_get FAILED -- expected (0) got (11), and hangs in 
31middle of test.
32
33cpuuse - hangs in middle of tests
34malloctest - prints nothing
35
36psx05 - Init: pthread_mutex_init - EINVAL (bad protocol)
37../../../../../../../src/rtems-981001/c/src/tests/psxtests/psx05/../../../../../
38../../src/rtems-981001/c/src/tests/psxtests/psx05/task.c:35: 
39failed assertion `status == EBUSY'
40N\: pthread_mutex_init - EINVAL (bad priority ceiling)
41
42
Note: See TracBrowser for help on using the repository browser.