Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #65705 > unrolled thread

Bug#945213: linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled

Back to article view | Back to linux.debian.kernel

Contents

  Bug#945213: linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled Anton Ivanov <anton.ivanov@kot-begemot.co.uk> - 2019-11-21 10:30 +0100
    Bug#945213: linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled Ben Hutchings <ben@decadent.org.uk> - 2019-11-22 20:40 +0100
      Bug#945213: linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled Anton Ivanov <anton.ivanov@kot-begemot.co.uk> - 2019-11-23 00:00 +0100
    Processed: Re: Bug#945213: linux-image-5.2.0-3-amd64: OOM  handling broken if hugepages are enabled "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-11-22 20:40 +0100

#65705 — Bug#945213: linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled

Package: linux-image-5.2.0-3-amd64
Version: 5.2.17+1
Severity: important

Dear Maintainer,

Dear Maintainer,

OOM handling appears to be broken in 5.2.17-1 if hugepages are enabled.

Test system: AMD A4-5300, 40G RAM, no swap, booted disklessly.

Without hugepages enabled can compile dpdk without any issues. With huge
pages enabled it will reproducibly OOM when trying to link one of the
libraries. There are 20G+ free RAM at that point according to free with the
rest being mostly used as buffers.

It is sufficient to just enable huge pages to trigger this (2G out of 40G),
they are not allocated or used by anything. 


-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]

#65709

[Multipart message — attachments visible in raw view] — view raw

Control: reassign -1 src:linux 5.2.17-1
Control: tag -1 moreinfo

On Thu, 2019-11-21 at 08:58 +0000, Anton Ivanov wrote:
> Package: linux-image-5.2.0-3-amd64
> Version: 5.2.17+1
> Severity: important
> 
> Dear Maintainer,
> 
> Dear Maintainer,
> 
> OOM handling appears to be broken in 5.2.17-1 if hugepages are enabled.
> 
> Test system: AMD A4-5300, 40G RAM, no swap, booted disklessly.
> 
> Without hugepages enabled can compile dpdk without any issues. With huge
> pages enabled it will reproducibly OOM when trying to link one of the
> libraries. There are 20G+ free RAM at that point according to free with the
> rest being mostly used as buffers.
> 
> It is sufficient to just enable huge pages to trigger this (2G out of 40G),
> they are not allocated or used by anything. 

What do you mean by "if hugepages are enabled"?  hugetlbfs and THP are
enabled by default.

You need to provide a log of the OOM messages.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.
It's the only way to be sure.

[toc] | [prev] | [next] | [standalone]

#65711

[Multipart message — attachments visible in raw view] — view raw

On 22/11/2019 19:32, Ben Hutchings wrote:
> Control: reassign -1 src:linux 5.2.17-1
> Control: tag -1 moreinfo
>
> On Thu, 2019-11-21 at 08:58 +0000, Anton Ivanov wrote:
>> Package: linux-image-5.2.0-3-amd64
>> Version: 5.2.17+1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> Dear Maintainer,
>>
>> OOM handling appears to be broken in 5.2.17-1 if hugepages are enabled.
>>
>> Test system: AMD A4-5300, 40G RAM, no swap, booted disklessly.
>>
>> Without hugepages enabled can compile dpdk without any issues. With huge
>> pages enabled it will reproducibly OOM when trying to link one of the
>> libraries. There are 20G+ free RAM at that point according to free with the
>> rest being mostly used as buffers.
>>
>> It is sufficient to just enable huge pages to trigger this (2G out of 40G),
>> they are not allocated or used by anything.
> What do you mean by "if hugepages are enabled"?  hugetlbfs and THP are
> enabled by default.

$ tail -2 sysctl.conf

vm.nr_hugepages=1024

If you do not have that, compile completes fine. If you have that 
compile blows up when linking one of the dpdk libraries. At that point 
the machine has ~ 20G free RAM.
> You need to provide a log of the OOM messages.

Ack. I will re-run the tests tomorrow and update the bug with detailed 
logs and the OOM.

>
> Ben.
>

-- 
Anton R. Ivanov
https://www.kot-begemot.co.uk/

[toc] | [prev] | [next] | [standalone]

#65710 — Processed: Re: Bug#945213: linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled

Processing control commands:

> reassign -1 src:linux 5.2.17-1
Bug #945213 [linux-image-5.2.0-3-amd64] linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled
Bug reassigned from package 'linux-image-5.2.0-3-amd64' to 'src:linux'.
No longer marked as found in versions 5.2.17+1.
Ignoring request to alter fixed versions of bug #945213 to the same values previously set
Bug #945213 [src:linux] linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled
Marked as found in versions linux/5.2.17-1.
> tag -1 moreinfo
Bug #945213 [src:linux] linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled
Added tag(s) moreinfo.

-- 
945213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945213
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web