[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMj1kXEA8TmK_pqDxrEg5==OPfWp8LWEBE=iFhJ8-5cm_DOgyA@mail.gmail.com>
Date: Mon, 14 Mar 2022 10:02:55 +0100
From: Ard Biesheuvel <ardb@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>,
open list <linux-kernel@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linus Walleij <linus.walleij@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
Corentin Labbe <clabbe.montjoie@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Daniel Díaz <daniel.diaz@...aro.org>,
lkft-triage@...ts.linaro.org
Subject: Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
On Mon, 14 Mar 2022 at 10:02, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>
> Hi Ard and Russell,
>
> Your three patches applied and tested on x15 tested by Daniel and reported
> kernel crash did not find it after multiple iterations.
>
> ARM: unwind: set frame.pc correctly for current-thread unwinding
> ARM: entry: fix unwinder problems caused by IRQ stacks
> ARM: Revert "unwind: dump exception stack from calling frame"
>
> Tested-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
Thank you Naresh.
Powered by blists - more mailing lists