This looks like a known issue to be fixed in the next release.

-----Original Message-----
From: Matthias Ecker [mailto:community-noreply@qnx.com] 
Sent: December-09-11 3:24 AM
To: ostech-core_os
Subject: x86 procnto-smp / bmp scheduling error

Hi,

I wonder if anybody else saw problems like that before: 

high priority processes are attached to an interrupt and forwarding the events using another mechnism (condvars). low 
priority processes are executing systemcalls like creating new processes (fork). 
In some situations a high priority process is scheduled ready, though is not allowed to run and another process with 
lower priority is still running (sometimes this is the idle thread). 
The error occurs fairly often in a bound multicore environment. 

Anyone saw that before? Or is using smp / bmp in a way like that? 

Cheers!
Matthias




_______________________________________________

OSTech
http://community.qnx.com/sf/go/post90495