Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 822246

Summary: clocktest use of CPUSET_S not completely correct.
Product: [Retired] Red Hat Hardware Certification Program Reporter: George Beshers <gbeshers>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.5CC: bbrock, czhang, rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: clocktest part of CORE test is not completely correct Consequence: CORE test will fail on very large systems (e.g.: 2048cpus) Fix: clocktest is fixed Result: CORE test will not fail anymore
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-01 18:20:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 813533    
Attachments:
Description Flags
Fix sched_setaffinity error none

Description George Beshers 2012-05-16 19:47:43 UTC 
Description of problem:
   It is a minor problem; I will have a patch ready tomorrow.
   Apparently we got lucky on the 1280cpu system, but 2048
   tickles the bug.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 George Beshers 2012-05-21 14:37:22 UTC 
Created attachment 585832 [details]
Fix sched_setaffinity error
Comment 2 George Beshers 2012-05-21 14:41:41 UTC 
To work with more than __CPU_SETSIZE
(set to 1024) the clocktest must be compiled
with  -DCPU_ALLOC.
Comment 10 errata-xmlrpc 2013-02-01 18:20:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0222.html