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 206501] Kernel 5.6-rc1 fails to boot on a PowerMac G4 3,6 with CONFIG_VMAP_STACK=y: Oops! Machine check, sig: 7  [#1]
Date: Wed, 12 Feb 2020 17:47:33 +0000	[thread overview]
Message-ID: <bug-206501-206035-1UDJ6jToo7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206501-206035@https.bugzilla.kernel.org/>

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

--- Comment #5 from Christophe Leroy (christophe.leroy@c-s.fr) ---
Interesting.

NIP:  00000550
NIP:  0000045c
NIP:  00000c38
NIP:  00000370

The kernel seems to badly fault on the first write to the stack. This suggests
that there is no page allocated for the stack yet. Which is unexpected because
in copy_thread_tls() several writes to the stack are performed so the pages
must exist in page tables.

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

  parent reply	other threads:[~2020-02-12 17:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 19:25 [Bug 206501] New: Kernel 5.6-rc1 fails to boot on a PowerMac G4 3,6 with CONFIG_VMAP_STACK=y: Oops! Machine check, sig: 7 [#1] bugzilla-daemon
2020-02-11 19:26 ` [Bug 206501] " bugzilla-daemon
2020-02-12  8:13 ` bugzilla-daemon
2020-02-12 11:53 ` bugzilla-daemon
2020-02-12 15:10 ` bugzilla-daemon
2020-02-12 17:47 ` bugzilla-daemon [this message]
2020-02-12 18:15 ` bugzilla-daemon
2020-02-13 10:45 ` bugzilla-daemon
2020-02-13 11:34 ` bugzilla-daemon
2020-02-13 17:32 ` bugzilla-daemon
2020-02-13 19:49 ` bugzilla-daemon
2020-02-26 15:34 ` 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-206501-206035-1UDJ6jToo7@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).