[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYsP1XN31sWMtPsaXzRtiAvHsn+A2cFZS2s6+muE_Qh61Q@mail.gmail.com>
Date: Wed, 24 May 2023 21:39:50 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: open list <linux-kernel@...r.kernel.org>,
linux-stable <stable@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, LTP List <ltp@...ts.linux.it>,
lkft-triage@...ts.linaro.org, X86 ML <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andy Lutomirski <luto@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
Dan Carpenter <dan.carpenter@...aro.org>,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: qemu-x86_64 compat: LTP: controllers: RIP: 0010:__alloc_pages
Hi Peter,
On Wed, 24 May 2023 at 19:37, Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Wed, May 24, 2023 at 02:32:20PM +0530, Naresh Kamboju wrote:
> > While running LTP controllers following kernel crash noticed on qemu-x86_64
> > compat mode with stable-rc 6.3.4-rc2.
>
> Both your reports are stable-rc 6.3.4-rc2; can I assume that stable
> 6.3.3 is good?
It was not good.
starting from 6.3.1-c1 these issues were there on
both i386 and x86_64.
I need to check back on other branches and compare it
with Linux mainline and Linux next master branches.
>
> Either way, could you please:
>
> 1) try linus/master
> 2) bisect stable-rc
>
> I don't immediately see a patch in that tree that would cause either of
> these things.
Thanks for asking these questions.
I should have included this information in my earlier email.
I have been noticing this from day one on stable-rc 6.3.1-rc1.
As per your suggestions, I will try to reproduce on other trees and
branches and get back to you.+
FYI,
These are running in AWS cloud as qemu-i386 and qemu-x86_64.
A few old links showing the history of the problem.
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.3.y/build/v6.3.3-364-ga37c304c022d/testrun/17170422/suite/log-parser-test/test/check-kernel-panic-7c768ef1d898edf92187a69f777efd2977be7fb965a68b333443bd4120e64c06/history/
i386:
====
Boot failed due to the following kernel crash.
<6>[ 2.078988] sched_clock: Marking stable (2023078833,
55554488)->(2088116191, -9482870)
<4>[ 2.081669] int3: 0000 [#1] PREEMPT SMP
<4>[ 2.082070] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.3.3-rc1 #1
<4>[ 2.082174] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),
BIOS 1.14.0-2 04/01/2014
<4>[ 2.082326] EIP: sched_clock_cpu+0xa/0x2b0
i386: while running LTP controllers tests
====
<4>[ 888.113619] int3: 0000 [#1] PREEMPT SMP
<4>[ 888.113966] CPU: 0 PID: 8805 Comm: pids.sh Not tainted 6.3.1-rc1 #1
<4>[ 888.114134] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),
BIOS 1.14.0-2 04/01/2014
<4>[ 888.114360] EIP: get_page_from_freelist+0xf1/0xc70
x86_64: while running LTP controllers tests
======
<4>[ 3182.753415] int3: 0000 [#1] PREEMPT SMP PTI
<4>[ 3182.755092] CPU: 0 PID: 69163 Comm: cgroup_fj_stres Not tainted
6.3.1-rc1 #1
<4>[ 3182.755228] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),
BIOS 1.14.0-2 04/01/2014
<4>[ 3182.755394] RIP: 0010:__alloc_pages+0xeb/0x340
x86_64: while running LTP tracing tests
======
<4>[ 52.392251] int3: 0000 [#1] PREEMPT SMP PTI
<4>[ 52.392648] CPU: 0 PID: 331 Comm: journal-offline Not tainted 6.3.3-rc1 #1
<4>[ 52.392794] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),
BIOS 1.14.0-2 04/01/2014
<4>[ 52.393070] RIP: 0010:syscall_trace_enter.constprop.0+0x1/0x1b0
- Naresh
Powered by blists - more mailing lists