From: Mike Galbraith <efault@gmx.de>
To: Will Deacon <will@kernel.org>
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, 01 Aug 2023 10:39:14 +0200 [thread overview]
Message-ID: <abd93ae835b2220277131081a448e038cce7e451.camel@gmx.de> (raw)
In-Reply-To: <20230801072732.GA25854@willie-the-truck>
On Tue, 2023-08-01 at 08:27 +0100, Will Deacon wrote:
> 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!
Weird, I don't see that even booting my 16G desktop box with mem=4G,
with a crashdump kernel setup and the GUI up and running...
homer:/root # echo 0 > /proc/sys/vm/overcommit_memory
homer:/root # free -h
total used free shared buff/cache available
Mem: 3.2Gi 1.6Gi 667Mi 18Mi 1.1Gi 1.6Gi
Swap: 4.0Gi 0B 4.0Gi
homer:/root # swapoff -a
homer:/root # perf test 26
26: Object code reading : Ok
homer:/root # dmesg | tail
[ 9.379431] br0: port 1(eth0) entered blocking state
[ 9.379434] br0: port 1(eth0) entered forwarding state
[ 9.379527] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
[ 9.388643] NET: Registered PF_PACKET protocol family
[ 17.225053] usblp0: removed
[ 17.226278] usblp 2-10:1.1: usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x04E8 pid 0x342E
[ 17.911334] r8169 0000:03:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM
[ 18.430787] NFSD: Using UMH upcall client tracking operations.
[ 18.430802] NFSD: starting 90-second grace period (net f0000000)
[ 20.578718] logitech-hidpp-device 0003:046D:401B.0006: HID++ 2.0 device connected.
homer:/root # uname -r
6.4.7-stable
homer:/root #
Same for a limited objdump -d, though unrestricted will oom instantly.
-Mike
prev parent reply other threads:[~2023-08-01 8:39 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
2023-08-01 8:39 ` Mike Galbraith [this message]
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=abd93ae835b2220277131081a448e038cce7e451.camel@gmx.de \
--to=efault@gmx.de \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lstoakes@gmail.com \
--cc=mark.rutland@arm.com \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
/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®