9125 2016-02-16 21:12:38 +0000 arm64 dmesg test fails show dmi Firmware registration failed 2017-08-17 03:11:50 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 2.0 x86 Multiple RESOLVED NOTABUG http://errors.yoctoproject.org/Errors/Details/34557/ Medium normal 2.4 M4 1 anibal.limon bruce.ashfield alejandro.hernandez dvhart sgw tom.zanussi --- --- No (bug/feature does not impact docs) oldest_to_newest 59125 0 anibal.limon 2016-02-16 21:12:38 +0000 AB testing on master fails when runs dmesg test it founds [1][2]: Central error: [ 2.015897] dmi: Firmware registration failed. | *********************** | [ 1.579988] raid6: neonx1 xor() 81 MB/s | [ 1.651385] raid6: neonx2 gen() 156 MB/s | [ 1.722430] raid6: neonx2 xor() 62 MB/s | [ 1.793460] raid6: neonx4 gen() 160 MB/s | [ 1.864489] raid6: neonx4 xor() 83 MB/s | [ 1.935760] raid6: neonx8 gen() 157 MB/s | [ 2.006986] raid6: neonx8 xor() 69 MB/s | [ 2.007645] raid6: using algorithm int64x2 gen() 824 MB/s | [ 2.008329] raid6: .... xor() 377 MB/s, rmw enabled | [ 2.009045] raid6: using intx1 recovery algorithm | [ 2.015897] dmi: Firmware registration failed. | [ 2.037728] clocksource: Switched to clocksource arch_sys_counter | [ 2.338334] NET: Registered protocol family 2 | [ 2.345384] TCP established hash table entries: 4096 (order: 3, 32768 bytes) | [ 2.346015] TCP bind hash table entries: 4096 (order: 4, 65536 bytes) | [ 2.346608] TCP: Hash tables configured (established 4096 bind 4096) | [ 2.347926] UDP hash table entries: 256 (order: 1, 8192 bytes) | [ 2.348404] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) | [ 2.350902] NET: Registered protocol family 1 | [ 2.359005] RPC: Registered named UNIX socket transport module. | [ 2.359396] RPC: Registered udp transport module. | | *********************** [1] http://errors.yoctoproject.org/Errors/Details/34557/ [2] https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/290/steps/Running%20Sanity%20Tests/logs/stdio 59207 1 richard.purdie 2016-02-18 15:45:39 +0000 We whitelisted the error in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=152914f2983c5d69001de1d46ce99547fa1e75fe 60235 2 bruce.ashfield 2016-03-21 23:16:37 +0000 I put this in 2.2, since this is as expected in the current configuration and 4.4 kernel. Unless we can find someone with dedicated cycles to look into this for 2.1, my hands are full with other issues. 75855 3 bruce.ashfield 2017-08-15 14:16:42 +0000 Moving to m4 and it can be checked against the 4.12 kernel, which arrives in M3. 75938 4 bruce.ashfield 2017-08-17 03:11:50 +0000 Looking at 4.12, this is expected for the qemu runs of the machine type we use for arm64. I'm resolving this as "not a bug". The whitelist we are using is the right thing to do.