From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 213837] [bisected] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5
Date: Thu, 07 Jul 2022 10:27:19 +0000 [thread overview]
Message-ID: <bug-213837-206035-6lFYFPHym9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213837-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213837
--- Comment #21 from Erhard F. (erhard_f@mailbox.org) ---
(Luckily) I am no longer able to reproduce this. Re-tested on 5.19-rc5.
I'll keep an eye on it and will close here if it stays like that for the next
few stable kernels.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
prev parent reply other threads:[~2022-07-07 10:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 20:00 [Bug 213837] New: "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5 bugzilla-daemon
2021-07-23 20:01 ` [Bug 213837] " bugzilla-daemon
2021-08-20 16:34 ` bugzilla-daemon
2021-08-20 16:35 ` bugzilla-daemon
2021-09-05 14:11 ` bugzilla-daemon
2021-09-08 12:54 ` Michael Ellerman
2021-09-05 14:15 ` bugzilla-daemon
2021-09-08 12:54 ` bugzilla-daemon
2021-09-13 7:16 ` bugzilla-daemon
2021-09-13 7:16 ` bugzilla-daemon
2021-09-22 15:33 ` bugzilla-daemon
2021-09-23 14:05 ` Michael Ellerman
2021-09-23 14:05 ` bugzilla-daemon
2021-09-23 16:29 ` bugzilla-daemon
2021-09-24 22:16 ` bugzilla-daemon
2021-09-24 22:17 ` bugzilla-daemon
2021-09-24 22:25 ` bugzilla-daemon
2021-11-28 14:20 ` bugzilla-daemon
2022-01-22 0:07 ` bugzilla-daemon
2022-01-22 0:14 ` [Bug 213837] [bisected] " bugzilla-daemon
2022-02-19 23:29 ` bugzilla-daemon
2022-02-19 23:31 ` bugzilla-daemon
2022-03-13 11:32 ` bugzilla-daemon
2022-03-13 11:33 ` bugzilla-daemon
2022-03-13 11:34 ` bugzilla-daemon
2022-07-07 10:27 ` bugzilla-daemon [this message]
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-213837-206035-6lFYFPHym9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.