From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 206527] New: Kernel 5.6-rc1 w. CONFIG_VMAP_STACK=y + CONFIG_KASAN=y fails to boot on a PowerMac G4 3,6
Date: Thu, 13 Feb 2020 20:40:31 +0000 [thread overview]
Message-ID: <bug-206527-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206527
Bug ID: 206527
Summary: Kernel 5.6-rc1 w. CONFIG_VMAP_STACK=y + CONFIG_KASAN=y
fails to boot on a PowerMac G4 3,6
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.6.0-rc1
Hardware: PPC-32
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-32
Assignee: platform_ppc-32@kernel-bugs.osdl.org
Reporter: erhard_f@mailbox.org
Regression: No
Created attachment 287361
--> https://bugzilla.kernel.org/attachment.cgi?id=287361&action=edit
screenshot of stuck boot process
Happens on my G4 DP with kernel 5.6.0-rc1 and KASAN (outline) enabled +
CONFIG_VMAP_STACK enabled. kernel is patched with Christophe's '[v2]
powerpc/32s: Fix DSI and ISI exceptions for CONFIG_VMAP_STACK'
(https://patchwork.ozlabs.org/patch/1237387/)
The kernel loads but booting gets stuck at a stage where the display is
initialized but before kernel dmesg gets show (see screenshot).
The machine boots with either CONFIG_VMAP_STACK=y or CONFIG_KASAN=y enabled but
not with both of them enabled together.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-02-13 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 20:40 bugzilla-daemon [this message]
2020-02-14 9:55 ` [Bug 206527] Kernel 5.6-rc1 w. CONFIG_VMAP_STACK=y + CONFIG_KASAN=y fails to boot on a PowerMac G4 3,6 bugzilla-daemon
2020-02-14 13:06 ` bugzilla-daemon
2020-02-26 15:33 ` 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-206527-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 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).