All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 209869] Kernel 5.10-rc1 fails to boot on a PowerMac G4 3,6 at an early stage
Date: Wed, 04 Nov 2020 14:30:21 +0000	[thread overview]
Message-ID: <bug-209869-206035-yRNzCMlXBk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209869-206035@https.bugzilla.kernel.org/>

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

--- Comment #3 from Christophe Leroy (christophe.leroy@csgroup.eu) ---
Ok, thanks for the verification. I'm still having hard time understand what the
problem can be. That commit sets up at all time the early hash table that was
previously only set up when CONFIG_KASAN was set. As far as I remember, you
tried KASAN many times.

Could you test whether CONFIG_KASAN works:
- on 5.10-rc1 with that commit reverted ?
- on 5.9 ?

If CONFIG_KASAN is already broken on 5.9, are you able to find the last kernel
version on which CONFIG_KASAN works ?

Thanks
Christophe

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

  parent reply	other threads:[~2020-11-04 14:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 13:40 [Bug 209869] New: Kernel 5.10-rc1 fails to boot on a PowerMac G4 3, 6 at an early stage bugzilla-daemon
2020-11-03  7:36 ` [Bug 209869] Kernel 5.10-rc1 fails to boot on a PowerMac G4 3,6 " bugzilla-daemon
2020-11-03 11:06 ` bugzilla-daemon
2020-11-04 14:30 ` bugzilla-daemon [this message]
2020-11-04 23:18 ` bugzilla-daemon
2020-11-04 23:19 ` bugzilla-daemon
2020-11-04 23:20 ` bugzilla-daemon
2020-11-04 23:21 ` bugzilla-daemon
2020-11-04 23:21 ` bugzilla-daemon
2020-11-05  9:26 ` bugzilla-daemon
2020-11-05 16:13 ` bugzilla-daemon
2020-11-07  9:11 ` bugzilla-daemon
2020-11-09 19:35 ` bugzilla-daemon
2020-11-27 12:08 ` bugzilla-daemon
2020-11-29  6:11 ` bugzilla-daemon
2020-11-30  1:36 ` 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-209869-206035-yRNzCMlXBk@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 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.