Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test

Bug #1739560 reported by Po-Hsu Lin on 2017-12-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

1. Deploy an ARM64 system with Trusty
2. Install necessary packages
3. git clone --depth=1 -b next
5. execute the in tests directory

 * 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'

Date: Thu Dec 21 07:49:12 2017
 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

 PATH=(custom, no user)

ProcKernelCmdLine: console=ttyS0,9600n8r ro
 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)

Po-Hsu Lin (cypressyew) wrote :
description: updated

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
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
Po-Hsu Lin (cypressyew) wrote :
Changed in ubuntu-kernel-tests:
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Brad Figg (brad-figg) on 2019-07-24
tags: added: cscc
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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers