From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Lucas Tanure <tanure@linux.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: Kernel Panic - V6.2 - Reseved memory issue
Date: Sun, 2 Apr 2023 19:55:16 +0700 [thread overview]
Message-ID: <ZCl7NFN5igCkIaLz@debian.me> (raw)
In-Reply-To: <CAJX_Q+1Tjc+-TjZ6JW9X0NxEdFe=82a9626yL63j7uVD4LpxEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
On Sun, Apr 02, 2023 at 09:10:36AM +0100, Lucas Tanure wrote:
> Log:
>
> [ 9.792966] SError Interrupt on CPU3, code 0x00000000bf000000 -- SError
> [ 9.792980] CPU: 3 PID: 3471 Comm: kded5 Tainted: G C 6.2.0 #1
> [ 9.792985] Hardware name: Khadas VIM3 (DT)
> [ 9.792987] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 9.792991] pc : kmem_cache_free_bulk.part.98+0x1f0/0x528
> [ 9.793004] lr : kmem_cache_free_bulk.part.98+0x2f8/0x528
> [ 9.793008] sp : ffff80000a2eb7f0
> [ 9.793009] x29: ffff80000a2eb7f0 x28: ffff00001f358518 x27: ffff000000008800
> [ 9.793016] x26: ffff00000262b300 x25: ffff00000262b300 x24: 0000000000000001
> [ 9.793019] x23: ffff00000262b000 x22: 0000000000000000 x21: ffff00001f358538
> [ 9.793022] x20: fffffc0000098ac0 x19: 0000000000000004 x18: 0000000000000040
> [ 9.793025] x17: 0000000000000018 x16: 00000000000007f8 x15: 0000000000000003
> [ 9.793028] x14: 0000000000000006 x13: ffff800008e48550 x12: 0000ffff9dc91fff
> [ 9.793031] x11: 0000000000000004 x10: 0000000000000001 x9 : ffff000007e93680
> [ 9.793035] x8 : 0000000000000020 x7 : ffff000001d2b100 x6 : 0000000000000007
> [ 9.793037] x5 : 0000000000000020 x4 : ffff000000008800 x3 : 0000000000000001
> [ 9.793040] x2 : 0000000000000007 x1 : 0000000000000000 x0 : ffff00001f358540
> [ 9.793045] Kernel panic - not syncing: Asynchronous SError Interrupt
>
> This doesn't happen with downstream Khadas 6.2 kernel, and that's
> because the downstream kernel removed this from
> early_init_dt_reserve_memory (drivers/of/fdt.c):
>
> /*
> * If the memory is already reserved (by another region), we
> * should not allow it to be marked nomap, but don't worry
> * if the region isn't memory as it won't be mapped.
> */
> if (memblock_overlaps_region(&memblock.memory, base, size) &&
> memblock_is_region_reserved(base, size))
> return -EBUSY;
>
What commit on downstream kernel that fix the issue? Can you reproduce
on mainline with above conditional removed? Alternatively, can
you post the downstream fix here?
Also, can you find last working commit on mainline? If so, this is
regression.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-02 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 8:10 Kernel Panic - V6.2 - Reseved memory issue Lucas Tanure
2023-04-02 12:55 ` Bagas Sanjaya [this message]
2023-04-03 11:29 ` Lucas Tanure
2023-04-03 15:28 ` Lucas Tanure
2023-04-02 13:11 ` Christian Hewitt
2023-04-17 12:27 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-04 10:22 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=ZCl7NFN5igCkIaLz@debian.me \
--to=bagasdotme@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tanure@linux.com \
/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