From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 204375] kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage
Date: Wed, 31 Jul 2019 09:13:44 +0000 [thread overview]
Message-ID: <bug-204375-206035-ofYSpOGYJd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204375-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204375
--- Comment #5 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 284057
--> https://bugzilla.kernel.org/attachment.cgi?id=284057&action=edit
early boot picture (PowerMac G4 DP, kernel 5.2.5)
Thanks! Your patch cleanly applied against kernel 5.2.5.
The boot process continues further and KASAN shadow mem is listed in Kernel
virtual memory layout (see picture). But it still hangs. It's still OF output,
I don't get to the point where radeon DRM kicks in.
I get a reboot after ~2min, most probably due to the soft lockup + hung tasks
timeout.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-07-31 9:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 23:24 [Bug 204375] New: kernel 5.2.4 w. KASAN enabled fails to boot on a PowerMac G4 3,6 at very early stage bugzilla-daemon
2019-07-29 23:27 ` [Bug 204375] " bugzilla-daemon
2019-07-31 4:49 ` bugzilla-daemon
2019-07-31 5:19 ` bugzilla-daemon
2019-07-31 6:04 ` bugzilla-daemon
2019-07-31 9:13 ` bugzilla-daemon [this message]
2019-07-31 9:27 ` bugzilla-daemon
2019-07-31 9:38 ` bugzilla-daemon
2019-07-31 9:39 ` bugzilla-daemon
2019-07-31 10:38 ` bugzilla-daemon
2019-07-31 11:37 ` bugzilla-daemon
2019-07-31 13:11 ` bugzilla-daemon
2019-08-01 5:36 ` bugzilla-daemon
2019-08-01 11:53 ` bugzilla-daemon
2019-08-05 0:42 ` bugzilla-daemon
2019-08-08 22:04 ` bugzilla-daemon
2019-08-09 12:25 ` 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-204375-206035-ofYSpOGYJd@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).