Hi,
I'm seeing the following unit test hanging on multiple boards, while it passes
on one board:
27: test atomic operations
Before I invest time debugging, has anyone seen similar issues with this test?
Regards,
Stephen Finucane
---
PS: The boards are on different kernels (failing: 3.16.6-200.fc20.x86_64,
3.17.2-200.fc20.x86_64, 3.17.6-200.fc20.x86_64; working:
3.14.7-200.default.fc20.x86_64). However, OVS should support all of these
kernels. I've included diffs between the kernel configs for these below in case
it's a config issue:
$ diff -u ./config-working ./config-broken | grep '^-[^-]' | grep -i 'mutex'
-# CONFIG_RT_MUTEX_TESTER is not set
$ diff -u ./config-working ./config-broken | grep '^-[^-]' | grep -i 'lock'
-CONFIG_PTP_1588_CLOCK_PCH=m
$ diff -u ./config-working ./config-broken | grep '^-[^-]' | grep -i 'atom'
$
$ diff -u ./config-working ./config-broken | grep '^+[^+]' | grep -i 'lock'
+CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
+CONFIG_ARCH_USE_QUEUE_RWLOCK=y
+CONFIG_QUEUE_RWLOCK=y
+# CONFIG_MTD_UBI_BLOCK is not set
+# Clock Source drivers
+# CONFIG_LOCK_TORTURE_TEST is not set
$ diff -u ./config-working ./config-broken | grep '^+[^+]' | grep -i 'atom'
+CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
+CONFIG_PMC_ATOM=y
$ diff -u ./config-working ./config-broken | grep '^+[^+]' | grep -i 'mutex'
$
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
