[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYuK4FWaLizcuVyW3ApR6fcgjMccYp3YxdAm61BOedXxzQ@mail.gmail.com>
Date: Wed, 21 Jun 2023 20:10:57 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Puranjay Mohan <puranjay12@...il.com>
Cc: Mark Rutland <mark.rutland@....com>,
Alexei Starovoitov <ast@...nel.org>,
Song Liu <song@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
linux-rpi-kernel@...ts.infradead.org,
Netdev <netdev@...r.kernel.org>, lkft-triage@...ts.linaro.org,
Arnd Bergmann <arnd@...db.de>,
Dan Carpenter <dan.carpenter@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Anshuman Khandual <anshuman.khandual@....com>,
bpf <bpf@...r.kernel.org>
Subject: Re: next: Rpi4: Unexpected kernel BRK exception at EL1
On Wed, 21 Jun 2023 at 19:46, Puranjay Mohan <puranjay12@...il.com> wrote:
>
> Hi,
>
> On Wed, Jun 21, 2023 at 3:39 PM Naresh Kamboju
> <naresh.kamboju@...aro.org> wrote:
> >
> > On Wed, 21 Jun 2023 at 18:27, Mark Rutland <mark.rutland@....com> wrote:
> > >
> > > On Wed, Jun 21, 2023 at 06:06:51PM +0530, Naresh Kamboju wrote:
> > > > Following boot warnings and crashes noticed on arm64 Rpi4 device running
> > > > Linux next-20230621 kernel.
> > > >
> > > > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> > > >
> > > > boot log:
> > > >
> > > > [ 22.331748] Kernel text patching generated an invalid instruction
> > > > at 0xffff8000835d6580!
> > > > [ 22.340579] Unexpected kernel BRK exception at EL1
> > > > [ 22.346141] Internal error: BRK handler: 00000000f2000100 [#1] PREEMPT SMP
> > >
> > > This indicates execution of AARCH64_BREAK_FAULT.
> >
> > I see kernel panic with kselftest merge configs on Juno-r2 and Rpi4.
>
> Is there a way to reproduce this setup on Qemu?
Not reproducible on Qemu-arm64.
I see only on arm64 devices Juno-r2 and Rpi4.
>
> I am able to build the linux-next kernel with the config given below.
> But the bug doesn't reproduce in Qemu with debian rootfs.
>
> I guess I would need the Rootfs that is being used here to reproduce it.
> Can you point me to the rootfs for this?
Here is the link for rootfs - OE one.
https://storage.tuxsuite.com/public/linaro/lkft/oebuilds/2RVA7dHPf73agY0gDJD6XEdBQBI/images/juno/
>
> Thanks,
> Puranjay
>
> > metadata:
> > git_ref: master
> > git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> > git_sha: 15e71592dbae49a674429c618a10401d7f992ac3
> > git_describe: next-20230621
> > kernel_version: 6.4.0-rc7
> > kernel-config:
> > https://storage.tuxsuite.com/public/linaro/lkft/builds/2RVAA4lj35ia3YDkqaoV6ztyqdW/config
> > artifact-location:
> > https://storage.tuxsuite.com/public/linaro/lkft/builds/2RVAA4lj35ia3YDkqaoV6ztyqdW/
> > toolchain: gcc-11
> > build_name: gcc-11-lkftconfig-kselftest
> >
> >
> > --
> > Linaro LKFT
> > https://lkft.linaro.org
- Naresh
Powered by blists - more mailing lists