Bug 814695
| Summary: | Red Hat v7 Hardware Test Suite Beta (v7-1.5-18) Core test clock jitter failed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Akash Kodenkiri <akodenkiri> | ||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0 | CC: | akodenkiri, czhang, emasyk, jsavanyo, rlandry | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-10-05 18:01:18 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: | |||||||
| Attachments: |
|
||||||
|
Description
Akash Kodenkiri
2012-04-20 12:45:11 UTC
Could you attach the core test results? Created attachment 579039 [details]
Core test result
Attached Core test result. -Akash The clock jitter test failed: Testing for clock jitter on 64 cpus using CPU_CALLOC ERROR, jitter = 0.223508 iter = 2691, cpus = 0,63 ERROR, jitter = 0.243354 iter = 9136, cpus = 0,63 FAILED, 2 iterations failed The jitter test did not change as I recall. I would suspect 1.4 to fail in a similar manner if tested on the same environment. If this is reproduced, it may be worth verifying with a different clock source. The results show the tsc clock is being used. I am not familiar with with vmware to say if this is expected or desired. Passing the kernel parameter "notsc" would likely have an effect but I'm not certain if the next default is any more appropriate than tsc. Using clock= would allow the appropriate one to be forced; again presuming tsc is not the accurate choice. If tsc is correct something else need to be looked at. Though in any case it seem unlikely to a core change between 1.4 and 1.5 that causes this to appear. (In reply to comment #5) > The jitter test did not change as I recall. I would suspect 1.4 to fail in a > similar manner if tested on the same environment. > > If this is reproduced, it may be worth verifying with a different clock source. > The results show the tsc clock is being used. I am not familiar with with > vmware to say if this is expected or desired. Passing the kernel parameter > "notsc" would likely have an effect but I'm not certain if the next default is > any more appropriate than tsc. Using clock= would allow the appropriate one to > be forced; again presuming tsc is not the accurate choice. If tsc is correct > something else need to be looked at. Though in any case it seem unlikely to a > core change between 1.4 and 1.5 that causes this to appear. I have executed these tests few more times. With 1.5 Core test Passed few times and Pass ratio is 5/10. With 1.4 Core test passed all the time and pass ratio is 10/10. -Akash Hi Akash, Is this still an issue with v7 1.5-32? ...with RHEL6.3? This is not an issue now, you can close the ticket. -Akash |