Bug 685 - ring_autotest consistently crashes with SIGBUS on armhf/armv7
Summary: ring_autotest consistently crashes with SIGBUS on armhf/armv7
Status: UNCONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: other (show other bugs)
Version: 20.11
Hardware: ARM Linux
: Normal normal
Target Milestone: ---
Assignee: Aaron
URL:
Depends on:
Blocks:
 
Reported: 2021-04-22 15:49 CEST by Luca Boccassi
Modified: 2021-07-16 09:04 CEST (History)
2 users (show)



Attachments

Description Luca Boccassi 2021-04-22 15:49:46 CEST
ring_autotest consistently crashes with SIGBUS when running on Debian armhf (armv7). This is running in a container, without root privileges, and without hugepages - as part of the fast suite.

There is no useful log message with verbose debugging.

Example:

https://ci.debian.net/data/autopkgtest/testing/armhf/d/dpdk/11831498/log.gz
Comment 1 Ajit Khaparde 2021-04-23 20:37:40 CEST
Aaron, Can you take a look? Thanks
Comment 2 Christian Ehrhardt 2021-07-16 09:04:36 CEST
FYI - this still is the same.
Here a text about a bug I wanted to file until I realized it is here already.

---

Hi,
as part of the CI we are running the fast-tests after every build in Debian and Ubuntu [1][2][3]. As part of this we happened to see that in this environment some issues occur.

This issue is about "ring_autotest" which seems to reliably fail in Debian as well as Ubuntu when run on armhf.

28/59 DPDK:fast-tests / ring_autotest            FAIL           0.37s (killed by signal 7 SIGBUS)

More detailed logs are at [4][5].
As it only happend on armhf it might be worth to mention that those run in lxc/ld based containers on a arm64 host - not sure but often enough that is related to armhf only fails.


[1]: https://packaging.ubuntu.com/html/auto-pkg-test.html
[2]: https://autopkgtest.ubuntu.com/
[3]: https://ci.debian.net/
[4]: https://ci.debian.net/data/autopkgtest/unstable/armhf/d/dpdk/13650683/log.gz
[5]: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/d/dpdk/20210712_094652_75b36@/log.gz

Note You need to log in before you can comment on or make changes to this bug.