linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215217] Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6)
Date: Mon, 13 Dec 2021 16:39:46 +0000	[thread overview]
Message-ID: <bug-215217-206035-ApKSVi2i7b@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215217-206035@https.bugzilla.kernel.org/>

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

--- Comment #9 from Christophe Leroy (christophe.leroy@csgroup.eu) ---
Erhard, were you able to redo the test with DISABLE_LATENT_ENTROPY_PLUGIN also
disabled for early_32.o  ?

If you can try with it disabled for both early_32.o and setup_32.o
Then if it works, retry with it disabled only for early_32.o

-- 
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:[~2021-12-13 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 22:48 [Bug 215217] New: Kernel fails to boot at an early stage when built with GCC_PLUGIN_LATENT_ENTROPY=y (PowerMac G4 3,6) bugzilla-daemon
2021-12-05  8:08 ` [Bug 215217] " bugzilla-daemon
2021-12-05  9:51 ` bugzilla-daemon
2021-12-05 17:48 ` bugzilla-daemon
2021-12-08 14:49 ` bugzilla-daemon
2021-12-09  3:17 ` bugzilla-daemon
2021-12-09 11:19 ` bugzilla-daemon
2021-12-09 11:20 ` bugzilla-daemon
2021-12-09 11:22 ` bugzilla-daemon
2021-12-13 16:39 ` bugzilla-daemon [this message]
2021-12-14  0:45 ` bugzilla-daemon
2021-12-14  5:41 ` bugzilla-daemon
2021-12-14 15:43 ` bugzilla-daemon
2021-12-17  7:20 ` bugzilla-daemon
2021-12-18  2:19 ` bugzilla-daemon
2022-02-03 17:29 ` 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-215217-206035-ApKSVi2i7b@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).