Image location: http://autobuilder03.jf.intel.com/nightly/20110305-3/machines/qemu/qemux86_64/ Tree/Branch: Distro/Bernard Commit: c192fefd868be53c20dfd8bc44e3e815cf53a10a The case did not fail in v1.0 M2 testing. With v1.0 M4 RC1 and RC2, it always get failure on both sato-sdk and lsb-sdk image. The error log is as below: ######### tag=clock_nanosleep01 stime=1299827524 cmdline="clock_nanosleep01" contacts="" analysis=exit <<<test_output>>> EXPECT: return value(ret)=0 errno=0 (Success) RESULT: return value(ret)=0 errno=0 (Success) EXPECT: return value(ret)=0 errno=0 (Success) RESULT: return value(ret)=0 errno=0 (Success) EXPECT: return value(ret)=22 errno=0 (Success) RESULT: return value(ret)=22 errno=0 (Success) EXPECT: return value(ret)=22 errno=0 (Success) RESULT: return value(ret)=22 errno=0 (Success) EXPECT: return value(ret)=4 errno=0 (Success) RESULT: return value(ret)=4 errno=0 (Success) clock_nanosleep01 0 TINFO : (case00) START clock_nanosleep01 0 TINFO : check sleep time: (min:480) < 501 < (max:520) (msec) clock_nanosleep01 0 TINFO : remain time: 0 0 clock_nanosleep01 0 TINFO : (case00) END => OK clock_nanosleep01 0 TINFO : (case01) START clock_nanosleep01 0 TINFO : check sleep time: (min:480) < 500 < (max:520) (msec) clock_nanosleep01 0 TINFO : remain time: 0 0 clock_nanosleep01 0 TINFO : (case01) END => OK clock_nanosleep01 0 TINFO : (case02) START clock_nanosleep01 0 TINFO : remain time: 0 0 clock_nanosleep01 0 TINFO : (case02) END => OK clock_nanosleep01 0 TINFO : (case03) START clock_nanosleep01 0 TINFO : remain time: 0 0 clock_nanosleep01 0 TINFO : (case03) END => OK clock_nanosleep01 0 TINFO : (case04) START clock_nanosleep01 1 TFAIL : iclock_gettime failed: TEST_ERRNO=EINVAL(22): Invalid argument clock_nanosleep01 0 TINFO : (case04) END => NG clock_nanosleep01 0 TINFO : (case05) START clock_nanosleep01 0 TINFO : remain time: 9 494470608 clock_nanosleep01 0 TINFO : (case05) END => OK clock_nanosleep01 2 TFAIL : clock_nanosleep failed clock_nanosleep01 0 TINFO : NG <<<execution_status>>> initiation_status="ok" duration=2 termination_type=exited termination_id=1 corefile=no cutime=4 cstime=4 #########
Created attachment 119 [details] the source file of clock_nanosleep01
There's no real changes outside of the stable update to the kernel in this timeframe. I'm not seeing anything that would trigger this. Do the h/w targets exhibit this same failure ?
(In reply to comment #2) > There's no real changes outside of the stable update to the > kernel in this timeframe. I'm not seeing anything that would > trigger this. > Do the h/w targets exhibit this same failure ? Yes, the case also fails on real hardware -- jasperforest and sugarbay, which use x86_64 kernel.
ok. thanks for the clarification. This means more people can debug/look into this when it bubbles up the list.
The issue still exists on Yocto 1.1 M1 testing on real hardware, like sugarbay. Tree/Branch: Poky/1.1_M1 Poky Commit: 4ff7af11ef69849ef9c16f585eae58ac920b222b Meta Branch: 1.1_M1 Meta Commit: fc719f0cd6530ce15148b4aa274f1644b461b298
sending to Liming for a 2nd level triage.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f5cddf955d7f8a2bf3a3fadf26219a4ddcdf6279
Verify the bug as fixed with 1.1 M4 branch. tree/branch: poky/1.1_M4 commit: 6462c158fc482e495c1171ffc7747e2ad650a292