All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 207129] PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760"
Date: Tue, 27 Feb 2024 15:25:10 +0000	[thread overview]
Message-ID: <bug-207129-206035-WIslPzcryo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207129-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207129

--- Comment #10 from Christophe Leroy (christophe.leroy@csgroup.eu) ---
I built a kernel with your .config, the problem is a size problem.

PPC32 kernels are not designed to be that big.

Extract from generated System.map:
  c2394000 D _etext
  c2800000 T _sinittext
  c2bf5000 B _end

You need to keep the size of the kernel below 32Mbytes, or a deep work is
required to enable the kernel to perform far jumps before the kernel is
relocated.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-02-27 15:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 21:32 [Bug 207129] New: PowerMac G4 DP (5.6.2 debug kernel + inline KASAN) freezes shortly after booting with "do_IRQ: stack overflow: 1760" bugzilla-daemon
2020-04-06  5:29 ` [Bug 207129] " bugzilla-daemon
2020-04-06 12:26 ` bugzilla-daemon
2020-04-06 12:27 ` bugzilla-daemon
2020-04-06 22:57 ` bugzilla-daemon
2020-04-08 14:55 ` bugzilla-daemon
2020-04-08 15:59 ` bugzilla-daemon
2024-02-26 11:02 ` bugzilla-daemon
2024-02-26 11:02 ` bugzilla-daemon
2024-02-27  0:40 ` bugzilla-daemon
2024-02-27  0:42 ` bugzilla-daemon
2024-02-27 15:25 ` bugzilla-daemon [this message]
2024-02-28 21:44 ` bugzilla-daemon

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=bug-207129-206035-WIslPzcryo@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.