Description of problem: In RHEL 5 processes are added to the appropriate cpuset when created, but are running on a CPU not allowed by that cpuset. When tested on RHEL 6 all processes are Version-Release number of selected component (if applicable): kernel 2.6.18-194.32.1.el5 RHEL 5.5 How reproducible: Not certain if this is every process, or only on certain ones. It has been noticed to occur on java threads. Steps to Reproduce: 1. Define a cpuset with parameters seen in attached 'cpuset.tar' on the version indicated above. 2. Start a task for use with this cpuset, and examine the current running processor. Actual results: Task is started with processor 0 instead of one in the defined set. Expected results: Task is started with a processor in the same cpuset. Additional info: This works as expected in RHEL 6 when using the cpuset filesystem (and not cgroups). Attaching the cpuset from RHEL 5, and the /proc/<PID>/status from a process running in both RHEL 5 and RHEL 6.
Created attachment 602800 [details] Result of /proc/<pid>/status on RHEL5. Result of /proc/<pid>/status on RHEL5.
Created attachment 602801 [details] Result of /proc/<pid>/status on RHEL6. Result of /proc/<pid>/status on RHEL6.
Created attachment 602802 [details] Cpuset on RHEL5 Cpuset on RHEL5
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Could not reproduce the error mentioned. It is attached to a closed customer issue.