From: Will Deacon <will@kernel.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Lorenzo Stoakes <lstoakes@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
wangkefeng.wang@huawei.com, catalin.marinas@arm.com,
ardb@kernel.org
Subject: Re: arm64: perf test 26 rpi4 oops
Date: Tue, 1 Aug 2023 08:27:33 +0100 [thread overview]
Message-ID: <20230801072732.GA25854@willie-the-truck> (raw)
In-Reply-To: <7b94619ad89c9e308c7aedef2cacfa10b8666e69.camel@gmx.de>
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@rpi4:~# 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
next prev parent reply other threads:[~2023-08-01 7:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 4:06 Mike Galbraith
2023-07-28 14:18 ` Will Deacon
2023-07-28 15:12 ` Mike Galbraith
2023-07-28 15:23 ` Will Deacon
2023-07-28 16:35 ` Mike Galbraith
2023-07-29 16:30 ` Mike Galbraith
2023-07-30 5:54 ` Mike Galbraith
2023-07-30 11:01 ` Mike Galbraith
2023-07-30 16:09 ` Mike Galbraith
2023-07-31 10:43 ` Will Deacon
2023-07-31 11:37 ` Mike Galbraith
2023-07-31 11:52 ` Will Deacon
2023-07-31 16:07 ` Mike Galbraith
2023-07-31 21:08 ` Lorenzo Stoakes
2023-07-31 21:54 ` Lorenzo Stoakes
2023-07-31 23:27 ` Mike Galbraith
2023-07-31 23:48 ` Mike Galbraith
2023-08-01 0:33 ` Mike Galbraith
2023-08-01 4:34 ` Mike Galbraith
2023-08-01 7:27 ` Will Deacon [this message]
2023-08-01 8:39 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230801072732.GA25854@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lstoakes@gmail.com \
--cc=mark.rutland@arm.com \
--cc=wangkefeng.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®