[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230801072732.GA25854@willie-the-truck>
Date: Tue, 1 Aug 2023 08:27:33 +0100
From: Will Deacon <will@...nel.org>
To: Mike Galbraith <efault@....de>
Cc: Lorenzo Stoakes <lstoakes@...il.com>,
lkml <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
wangkefeng.wang@...wei.com, catalin.marinas@....com,
ardb@...nel.org
Subject: Re: arm64: perf test 26 rpi4 oops
On Tue, Aug 01, 2023 at 06:34:15AM +0200, Mike Galbraith wrote:
> On Tue, 2023-08-01 at 01:48 +0200, Mike Galbraith wrote:
> >
> > root@...4:~# dmesg|tail -2
> > [ 979.003019] __vm_enough_memory: pid: 12439, comm: objdump, not enough memory for the allocation
> > [ 979.003080] __vm_enough_memory: pid: 12439, comm: objdump, not enough memory for the allocation
>
> Ancient bug droppings are due to VMALLOC_END-VMALLOC_START=265885319168.
FWIW, I see the same thing on my x86 laptop. I'm guessing objdump tries
to read all of the vmalloc space into memory, which is going to end
pretty badly!
Will
Powered by blists - more mailing lists