09/12 11:27:57 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): FAIL Killed by signal "Bus error" due to overcommit
Bug still valid. http://10.246.72.4/test-results/3.13.0-158.208-generic/ms10-35-mcdivittB0-kernel__3.13.0-158.208__2018-09-12_11-15-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html ** Changed in: ubuntu-kernel-tests Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747828 Title: chunk-overcommit test in libhugetlbfs test suite will fail on Trusty ARM64 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Steps: 1. Deploy an ARM64 system with Trusty 2. Install necessary packages 3. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 4. make BUILDTYPE=NATIVEONLY 5. execute the run_test.py in tests directory Result: * The chunk-overcommit test case will fail chunk-overcommit (2M: 64): Starting testcase "chunk-overcommit", pid 17370 overcommit: 31935 hugepages available: chunk1=15968 chunk2=15968 Looks like we've overcommitted, testing... FAIL Killed by signal "Bus error" due to overcommit Error message could be found in syslog: AutotestCrashHandler: Application chunk-overcommi, PID 2269 crashed AutotestCrashHandler: Writing core files to ['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.chunk-overcommi.2269'] AutotestCrashHandler: Could not determine from which application core file /home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.chunk-overcommi.2269/core is from Please find the attachement for the core file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-141-generic 3.13.0-141.190 ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39 Uname: Linux 3.13.0-141-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.27 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed Feb 7 04:14:16 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-141-generic N/A linux-backports-modules-3.13.0-141-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1747828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
