Hi! > > > Ok, so we ran some tests. > > > > > > And they failed: > > > > > > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/1075959449 > > > > > > [ 26.785861] > > > Received signal: TEST_CASE_ID=CVE-2018-3639 RESULT=fail > > > > > > Testcase name is spectre-meltdown-checker... Failing on qemu? Somehow > > > strange, but it looks like real test failure. This is pointer to the pipeline: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/265992696 > First let me try 7d472e4a11d6a2fb1c492b02c7d7dacd3297bbf4 -- > v4.4.257-cip54. That is > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/266532179 > ... Qemu is OKAY. > > add3ff3730919447a7519fede0b8554132e0f8d5 Merge remote-tracking branch > 'stable/queue/4.4' in to v4.4.260-bisect. Results will be at > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/266534478 > ... ... still pending. Qemu is okay here, too. > test 266539168 8c461bb103f89696576945ad9cb376df34fa9d28 xen-netback: respect gnttab_map_refs()'s return value Qemu is ok. > test 266538760 1efe86b456816c95485c65cf9ba46a5bff8a241e staging: fwserial: Fix error handling in fwserial_create Qemu is ok. > test 266539768 8b4bc0f97fdd13b08c2436aad01bd4515d07f93a iwlwifi: pcie: fix to correct null check Pavel Qemu is ok. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/266539768 So... failure apparently went away when trying to bisect. That's.... strange? Aha, except that it looks like the same "suceeded" tests still have failures in them: https://lava.ciplatform.org/scheduler/job/173186 [ 26.224557] Received signal: TEST_CASE_ID=CVE-2017-5715 RESULT=fail ...I guess those fails are expected, then? And qemu tests on -stable-rc are really failing on timeouts. ... Hmm, let's just re-run the tests. I'm still not sure, but it looks like a test failure now. Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany