On Wed, Jan 11, 2023, at 07:55, Naresh Kamboju wrote: > On Tue, 10 Jan 2023 at 23:44, Greg Kroah-Hartman > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >> >> This is the start of the stable review cycle for the 6.1.5 release. >> There are 159 patches in this series, all will be posted as a response >> to this one. If anyone has any issues with these being applied, please >> let me know. >> >> Responses should be made by Thu, 12 Jan 2023 17:59:42 +0000. >> Anything received after that time might be too late. >> >> The whole patch series can be found in one patch at: >> https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.5-rc1.gz >> or in the git tree and branch at: >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y >> and the diffstat can be found below. >> >> thanks, >> >> greg k-h > > Results from Linaro’s test farm. > Regressions on arm64 FVP. > > Reported-by: Linux Kernel Functional Testing <lkft@xxxxxxxxxx> > > Following kernel panic and warning notices on FVP 64k page size > enabled gcc-12 build on 6.1 and 6.0 kernel Image while running > LTP mm test cases. > > CONFIG_ARM64_64K_PAGES=y I assume you mean this only happens with 64K pages but not 4K pages? I see the machine only has 4GB of RAM, so it's possible this is a side-effect of an out-of-memory condition somewhere as kernels with 64K pages need a lot more RAM. > SError Interrupt on CPU3, code 0x00000000be000000 -- SError > Kernel panic - not syncing: Asynchronous SError Interrupt This is an SError from user space, where the 'be' bit is the encoding for SError, and the ISS and ISS2 words are all zero. The CPU enables the 'RAS' extension, so ISS is defined according to [1], but none of the bits are set, so this is 'Uncategorized'. This seems particularly unhelpful from FVP, possibly a bug in the RAS error reporting. > WARNING: CPU: 3 PID: 685 at kernel/sched/core.c:3113 set_task_cpu This again seems unrelated and only happens when it panics the second time. Arnd
