mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Guenter Roeck" <linux@roeck-us.net>,
	shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, "Pavel Machek" <pavel@denx.de>,
	"Jon Hunter" <jonathanh@nvidia.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
	srw@sladewatkins.net, rwarsow@gmx.de,
	"Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH 6.1 000/159] 6.1.5-rc1 review
Date: Wed, 11 Jan 2023 15:18:08 +0100	[thread overview]
Message-ID: <ff7096b8-aaee-45db-8d0a-2790d9d227eb@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYuQzq1bBt9k0PtpAc0Ubn9wXmjzVGNRhSOFBr-fx3KQQw@mail.gmail.com>

On Wed, Jan 11, 2023, at 07:55, Naresh Kamboju wrote:
> On Tue, 10 Jan 2023 at 23:44, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> 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@linaro.org>
>
> 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

  reply	other threads:[~2023-01-11 14:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 18:02 Greg Kroah-Hartman
2023-01-10 19:38 ` Florian Fainelli
2023-01-11  0:35 ` Shuah Khan
2023-01-11  0:59 ` ogasawara takeshi
2023-01-11  6:55 ` Naresh Kamboju
2023-01-11 14:18   ` Arnd Bergmann [this message]
2023-01-11 10:58 ` Rudi Heitbaum
2023-01-11 11:17 ` Jon Hunter
2023-01-11 11:24 ` Ron Economos
2023-01-11 12:58 ` Sudip Mukherjee
2023-01-11 16:49 ` Naresh Kamboju
2023-01-11 17:28 ` Allen Pais
2023-01-11 17:28 ` Justin Forbes
2023-01-11 18:55 ` Conor Dooley
2023-01-12  0:40 ` Guenter Roeck
2023-01-12  2:04 ` Bagas Sanjaya
2023-01-12  3:02 ` Kelsey Steele
2023-01-10 19:33 Ronald Warsow

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=ff7096b8-aaee-45db-8d0a-2790d9d227eb@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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®