[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21777dec0233b1bc65f51764ead9a03efa9baa64.camel@gmx.de>
Date: Tue, 01 Aug 2023 01:48:19 +0200
From: Mike Galbraith <efault@....de>
To: Lorenzo Stoakes <lstoakes@...il.com>, Will Deacon <will@...nel.org>
Cc: 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, 2023-08-01 at 01:27 +0200, Mike Galbraith wrote:
> On Mon, 2023-07-31 at 22:54 +0100, Lorenzo Stoakes wrote:
> >
> > Posted a fix at:-
> >
> > https://lore.kernel.org/all/20230731215021.70911-1-lstoakes@gmail.com/
> >
> > Please give that a go and indicate whether that resolves the issue.
>
> Yup, that fixed the oops issue.
Heh, using Jiri's pick a spot from /proc/kallsyms test...
root@...4:~# cat /proc/kallsyms | grep ksys_read
ffffffe950baf7f8 T ksys_readahead
ffffffe950c38708 T ksys_read
root@...4:~# objdump -d --start-address=0xffffffe950c38708 --stop-address=0xffffffe950c3870a /proc/kcore
/proc/kcore: file format elf64-littleaarch64
Disassembly of section load1:
ffffffe950c38708 <load1+0x238708>:
ffffffe950c38708: Address 0xffffffe950c38708 is out of bounds.
objdump: error: /proc/kcore(load2) is too large (0x3de8000000 bytes)
objdump: Reading section load2 failed because: memory exhausted
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
Powered by blists - more mailing lists