libhugetlbfs test suite failed with brk_near_huge test
Bug #1653597 reported by
Po-Hsu Lin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Triaged
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
linux-azure (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Kernel: 4.8.0-34.36
The libhugetlbfs failed with the brk_near_huge test on x86_64(gce)
12/24 04:59:42 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS
12/24 04:59:42 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2403: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
12/24 04:59:42 DEBUG| utils:0153| [stdout] brk_near_huge (2M: 64):
12/24 04:59:42 DEBUG| utils:0153| [stdout] task-size-overrun (2M: 64): PASS
Full log: http://
summary: |
- libhugetlbfs failed with brk_near_huge test on GCE with 4.8.0-34.36 + libhugetlbfs test suite failed with brk_near_huge test on GCE with + 4.8.0-34.36 |
summary: |
- libhugetlbfs test suite failed with brk_near_huge test on GCP + libhugetlbfs test suite failed with brk_near_huge test on GCP & Azure |
tags: | added: aws |
tags: | added: azure gcp |
summary: |
- libhugetlbfs test suite failed with brk_near_huge test on GCP & Azure + libhugetlbfs test suite failed with brk_near_huge test |
tags: | removed: kqa-azure yakkety |
tags: | added: cscc |
tags: | added: sru-20190722 |
tags: | added: 20190812 |
tags: |
added: sru-20190812 removed: 20190812 |
tags: | added: libhugetlbfs |
Changed in linux (Ubuntu): | |
assignee: | nobody → Connor Kuehl (connork) |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
assignee: | Connor Kuehl (connork) → nobody |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1653597
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.