linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	lkft-triage@lists.linaro.org,
	Linux Regressions <regressions@lists.linux.dev>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next-20240219: arm64: boot failed - gic_of_init
Date: Mon, 19 Feb 2024 09:48:28 +0000	[thread overview]
Message-ID: <86edd84wer.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+G9fYugYiLd7MDn3wCxK+x5Td9WO-VUX2OvOtTN7D1d4GHCfg@mail.gmail.com>

On Mon, 19 Feb 2024 09:42:45 +0000,
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> 
> The qemu-arm64 boot failed with linux next-20240219 tag kernel.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> Boot log:
> ---------
> <6>[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> <1>[    0.000000] Unable to handle kernel paging request at virtual
> address ffff80008001ffe8
> <1>[    0.000000] Mem abort info:
> <1>[    0.000000]   ESR = 0x0000000096000004
> <1>[    0.000000]   EC = 0x25: DABT (current EL), IL = 32 bits
> <1>[    0.000000]   SET = 0, FnV = 0
> <1>[    0.000000]   EA = 0, S1PTW = 0
> <1>[    0.000000]   FSC = 0x04: level 0 translation fault
> <1>[    0.000000] Data abort info:
> <1>[    0.000000]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
> <1>[    0.000000]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
> <1>[    0.000000]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
> <1>[    0.000000] swapper pgtable: 4k pages, 52-bit VAs, pgdp=0000000042497000
> <1>[    0.000000] [ffff80008001ffe8] pgd=10000000439a5003,
> p4d=10000001000e3003, pud=10000001000e4003, pmd=10000001000e5003,
> pte=006800000800f413
> <0>[    0.000000] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
> <4>[    0.000000] Modules linked in:
> <4>[    0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
> 6.8.0-rc5-next-20240219 #1
> <4>[    0.000000] Hardware name: linux,dummy-virt (DT)
> <4>[    0.000000] pstate: 804000c9 (Nzcv daIF +PAN -UAO -TCO -DIT
> -SSBS BTYPE=--)
> <4>[    0.000000] pc : gic_of_init+0x84/0x3a8
> <4>[    0.000000] lr : gic_of_init+0x290/0x3a8
> ...
> <4>[    0.000000] Call trace:
> <4>[    0.000000]  gic_of_init+0x84/0x3a8
> <4>[    0.000000]  of_irq_init+0x1d4/0x3d0
> <4>[    0.000000]  irqchip_init+0x20/0x50
> <4>[    0.000000]  init_IRQ+0xa8/0xc8
> <4>[    0.000000]  start_kernel+0x270/0x690
> <4>[    0.000000]  __primary_switched+0x80/0x90
> <0>[    0.000000] Code: f94017e0 f90007e0 d29ffd00 8b0002c0 (b9400000)
> <4>[    0.000000] ---[ end trace 0000000000000000 ]---
> <0>[    0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
> <0>[    0.000000] ---[ end Kernel panic - not syncing: Attempted to
> kill the idle task! ]---
> 
> Links:
>  - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240219/testrun/22730192/suite/boot/test/gcc-13-lkftconfig-armv8_features/log
>  - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240219/testrun/22730192/suite/boot/tests/

Where is the configuration file? What are the parameters to QEMU?
Please consider making this a useful and actionable report.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-02-19  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  9:42 next-20240219: arm64: boot failed - gic_of_init Naresh Kamboju
2024-02-19  9:48 ` Marc Zyngier [this message]
2024-02-19 11:32   ` Marc Zyngier
2024-02-19 14:46     ` Zenghui Yu
2024-02-19 15:02       ` Marc Zyngier
2024-02-19 15:27       ` Marc Zyngier
2024-02-20  2:26         ` Zenghui Yu
2024-02-20 10:30         ` Naresh Kamboju

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=86edd84wer.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).