[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <d41a6d08-981b-481b-9108-fe91afaa0f82@app.fastmail.com>
Date: Sun, 02 Jul 2023 10:26:15 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Naresh Kamboju" <naresh.kamboju@...aro.org>,
"open list" <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org
Cc: "Frederic Weisbecker" <frederic@...nel.org>,
"Paul E. McKenney" <paulmck@...nel.org>,
"Mark Rutland" <mark.rutland@....com>,
"Anders Roxell" <anders.roxell@...aro.org>,
"Dan Carpenter" <dan.carpenter@...aro.org>
Subject: Re: qemu-arm64: Unexpected kernel BRK exception at EL1 - WARNING: CPU: 3 PID:
0 at kernel/context_tracking.c:128 ct_kernel_exit.constprop
On Sat, Jul 1, 2023, at 10:42, Naresh Kamboju wrote:
> Links:
> -
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.4-8686-ge55e5df193d2/testrun/17999853/suite/log-parser-test/tests/
> -
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.4-8686-ge55e5df193d2/testrun/17999906/suite/log-parser-test/tests/
I can't see which build artifacts correspond to the logs. Can you link to the
vmlinux file?
Arnd
Powered by blists - more mailing lists