STATUS: FAILED BUILD: 2.1_M3.RC2: 21823cb466e79540567ad1a43ae6f93d850e4057 ENVIRONMENT: genericx86 - on MMAX32bit BUILD_SYS: X86_64-LINUX NATIVELSBSTRING: "universal" MACHINE: "genericx86" DISTRO: "poky-lsb" DISTRO_VERSION: "2.0+snapshot-20160405" STEPS TO REPRODUCE: Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc. Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored.
Created attachment 3092 [details] log_dotestimage
There are 3 failing tests at this log: test_parselogs, test_syslog_startup_config and test_xorg_running. Looking at the test_parselogs which is the first failure seems like something went wrong at boot time. Many errors like this are shown: ----------- Central error: Apr 4 23:22:15 genericx86 kernel: usb 1-1.4: device descriptor read/64, error -32 ----------- did you connect any new usb device to the target you were testing? Paco, you can also check the errors.yoctoproject.org similar errors: http://errors.yoctoproject.org/Errors/Search/?query=Test+log+string+not+found.+Output%3A+grep%3A+%2Fvar%2Flog%2Ftest%3A+No+such+file+or+directory I also did a grep of the Xorg error and I checked the first ones and they seem to be related to 'central errors' like the one that the test_parselogs is showing. Summarizing, this looks like a bad image burn or a bad image creation. Is this a reproducible error?
(In reply to comment #2) > There are 3 failing tests at this log: test_parselogs, > test_syslog_startup_config and test_xorg_running. > > Looking at the test_parselogs which is the first failure seems like > something went wrong at boot time. Many errors like this are shown: > > ----------- > Central error: Apr 4 23:22:15 genericx86 kernel: usb 1-1.4: device > descriptor read/64, error -32 > ----------- > > did you connect any new usb device to the target you were testing? > > Paco, you can also check the errors.yoctoproject.org similar errors: > > http://errors.yoctoproject.org/Errors/Search/ > ?query=Test+log+string+not+found. > +Output%3A+grep%3A+%2Fvar%2Flog%2Ftest%3A+No+such+file+or+directory > > I also did a grep of the Xorg error and I checked the first ones and they > seem to be related to 'central errors' like the one that the test_parselogs > is showing. > > Summarizing, this looks like a bad image burn or a bad image creation. Is > this a reproducible error? Hi, I will reproduce more times, just to check what you are suggesting. Thanks.
moving back to Francisco for getting the reproducibility of the error.
Created attachment 3434 [details] logs_retest_failed_ Failed
Retested and Failed getting the next error message: Central error: Sep 9 14:45:33 genericx86 kernel: amd_nb: Cannot enumerate AMD northbridges Logs are attached as well.
not a Minnow specific bug, punting back to PC
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=bb744b82c7df3ce3bda9a1b85fc075a20169eca9