From: Mike Galbraith <efault@gmx.de>
To: Lorenzo Stoakes <lstoakes@gmail.com>, Will Deacon <will@kernel.org>
Cc: 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 02:33:29 +0200 [thread overview]
Message-ID: <5c9043d0bd8257c813435e35c2df2f943543d168.camel@gmx.de> (raw)
In-Reply-To: <21777dec0233b1bc65f51764ead9a03efa9baa64.camel@gmx.de>
On Tue, 2023-08-01 at 01:48 +0200, Mike Galbraith wrote:
> 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@rpi4:~# cat /proc/kallsyms | grep ksys_read
> ffffffe950baf7f8 T ksys_readahead
> ffffffe950c38708 T ksys_read
> root@rpi4:~# 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@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
crash> p ksys_read
ksys_read = $2 =
{ssize_t (unsigned int, char *, size_t)} 0xffffffe950c38710 <ksys_read>
crash> dis 0xffffffe950c38710 10
0xffffffe950c38710 <ksys_read+8>: paciasp
0xffffffe950c38714 <ksys_read+12>: stp x29, x30, [sp, #-64]!
0xffffffe950c38718 <ksys_read+16>: mrs x3, sp_el0
0xffffffe950c3871c <ksys_read+20>: mov x29, sp
0xffffffe950c38720 <ksys_read+24>: stp x21, x22, [sp, #32]
0xffffffe950c38724 <ksys_read+28>: mov x21, x1
0xffffffe950c38728 <ksys_read+32>: mov x22, x2
0xffffffe950c3872c <ksys_read+36>: ldr x1, [x3, #1320]
0xffffffe950c38730 <ksys_read+40>: str x1, [sp, #56]
0xffffffe950c38734 <ksys_read+44>: mov x1, #0x0 // #0
crash>
Ah, so arm64 kallsyms fibs a little.. x64_64 doesn't.
root@rpi4:~# objdump -d --start-address=0xffffffe950c38710 --stop-address=0xffffffe950c38734 /proc/kcore
/proc/kcore: file format elf64-littleaarch64
Disassembly of section load1:
ffffffe950c38710 <load1+0x238710>:
ffffffe950c38710: d503233f paciasp
ffffffe950c38714: a9bc7bfd stp x29, x30, [sp, #-64]!
ffffffe950c38718: d5384103 mrs x3, sp_el0
ffffffe950c3871c: 910003fd mov x29, sp
ffffffe950c38720: a9025bf5 stp x21, x22, [sp, #32]
ffffffe950c38724: aa0103f5 mov x21, x1
ffffffe950c38728: aa0203f6 mov x22, x2
ffffffe950c3872c: f9429461 ldr x1, [x3, #1320]
ffffffe950c38730: f9001fe1 str x1, [sp, #56]
objdump: error: /proc/kcore(load2) is too large (0x3de8000000 bytes)
objdump: Reading section load2 failed because: memory exhausted
root@rpi4:~#
next prev parent reply other threads:[~2023-08-01 0:33 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 [this message]
2023-08-01 4:34 ` Mike Galbraith
2023-08-01 7:27 ` Will Deacon
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=5c9043d0bd8257c813435e35c2df2f943543d168.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®