Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test

Bug #1739560 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Medium
Unassigned

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

Results:
 * you will see it stuck at shmoverride_linked test, no output for this test in syslog

truncate_reserve_wraparound (2M: 64): PASS
truncate_sigbus_versus_oom (2M: 64): PASS
get_huge_pages (2M: 64): PASS
shmoverride_linked (2M: 64):

This issue can be reproduced in 3.13.0-137 and 3.13.0-138 in proposed.
As we didn't run any regression-test on this node between 3.13.0-135 ~ 3.13.0-136 (this node was broken).

This test cannot be built on ARM64 before (till 3.13.0-133, we have changed to use the upstream repo since then) therefore I think this can be considered as not a regression.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-137-generic 3.13.0-137.186
ProcVersionSignature: User Name 3.13.0-137.186-generic 3.13.11-ckt39
Uname: Linux 3.13.0-137-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'
CurrentDmesg:

Date: Thu Dec 21 07:49:12 2017
IwConfig:
 lo no wireless extensions.

 enp1s0 no wireless extensions.

 enp1s0d1 no wireless extensions.
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-137-generic N/A
 linux-backports-modules-3.13.0-137-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)
WifiSyslog:

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
tags: added: kernel-da-key
Revision history for this message
Sean Feole (sfeole) wrote :

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

Changed in ubuntu-kernel-tests:
status: New → Incomplete
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in ubuntu-kernel-tests:
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

With the libhugetlbfs updated recently, this will need to be revisited.

tags: added: ubuntu-kvm-smoke-test
tags: added: libhugetlbfs
removed: ubuntu-kvm-smoke-test
Changed in ubuntu-kernel-tests:
status: Confirmed → Incomplete
Revision history for this message
Sean Feole (sfeole) wrote :
Download full text (3.2 KiB)

I have not seen this occur on the -aws nitro backed arm64 instances. Giving that mcdivitt is EOL, killing off this bug.

07/09 11:08:48 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race shared (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race private (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_reserve_wraparound (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_sigbus_versus_oom (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] get_huge_pages (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes shmoverride_linked (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked_static (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes shmoverride_linked_static (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so shmoverride_unlinked (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so HUGETLB_SHM=yes shmoverride_unlinked (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] quota.sh (2M: 64): PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] counters.sh (2M: 64): PASS
07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-gettest 10 20 (2M: 64): PASS
07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-cow 19 20 (2M: 64): PASS
07/09 11:08:49 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040
07/09 11:08:50 DEBUG| utils:0153| [stdout] shm-fork 10 10 (2M: 64): PASS
07/09 11:08:50 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040
07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-fork 10 20 (2M: 64): PASS
07/09 11:08:52 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040
07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-getraw 20 /dev/full (2M: 64): PASS
07/09 11:09:18 DEBUG| utils:0153| [stdout] fallocate_stress.sh (2M: 64): PASS
07/09 11:09:18 DEBUG| utils:0153| [stdout] ********** TEST SUMMARY
07/09 11:09:18 DEBUG| utils:0153| [stdout] * 2M
07/09 11:09:18 DEBUG| utils:0153| [stdout] * 32-bit 64-bit
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Total testcases: 0 113
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Skipped: 0 0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * PASS: 0 111
07/09 11:09:18 DEBUG| utils:0153| [stdout] * FAIL: 0 0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Killed by signal: 0 1
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Bad configuration: 0 1
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Expected FAIL: 0 0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Unexpected PASS: 0 0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Test not present: 0 0
07/09 11:09:18 DEBUG| utils:0153| [stdout] * Strange test result: 0 0 ...

Read more...

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in ubuntu-kernel-tests:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.