This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Issue 1001033] New: Cannot create threads with numerical priorityvalues higher than 14.
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Fri, 17 Sep 2010 18:35:32 +0100
- Subject: [Issue 1001033] New: Cannot create threads with numerical priorityvalues higher than 14.
- Auto-submitted: auto-generated
Please do not reply to this email. Use the web interface provided at:
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1001033
Summary: Cannot create threads with numerical priority values
higher than 14.
Product: eCos
Version: 3.0
Platform: All
OS/Version: ARM
Status: UNCONFIRMED
Severity: critical
Priority: normal
Component: Kernel
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: lawrence.lo@emerson.com
QAContact: ecos-bugs@ecos.sourceware.org
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
eCos version is 3.0.3.
Hardware platform is arm9/fa5xx/harley.
It failed to create and run a thread with numerical priority values higher than
14. For example, we tried to create an idle thread with the following
instructions:
cyg_thread_create(15, (cyg_thread_entry_t *)&idleHandler, NULL, NULL,
&idleThreadStack, sizeof(idleThreadStack),
&idleThreadHandle, &idleThread);
cyg_thread_resume(idleThreadHandle);
The idle thread would fail to run (a print statement at the beginning of the
idle thread was not seen) and the system would hang as soon as all other
threads (with lower numerical priority values) blocked (which also indicated
the idle thread was not running.)
I performed the test with priority values from 15 to 31 and they all failed.
Everything appeared normal when I used priority values from 0 to 14.
I have verified CYG_THREAD_MAX_PRIORITY is defined to 31 and
CYG_THREAD_MIN_PRIORITY defined to 0 in eCos sources.
In our tests, the bitmap scheduler was configured.
--
Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.
You are on the CC list for the issue.