From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 213837] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5
Date: Sun, 28 Nov 2021 14:20:25 +0000 [thread overview]
Message-ID: <bug-213837-206035-i8LqeujfEW@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 #13 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 299755
--> https://bugzilla.kernel.org/attachment.cgi?id=299755&action=edit
dmesg (5.16-rc2 + patch, PowerMac G5 11,2)
Still happens with with 5.16-rc2, but getting a slightly different error
message this time. Also this crash happened earlier, not at building distcc but
at unpacking the to be built tar.gz archive with tar + pigz:
[...]
stack: c000000005b0e600: 00000000 00000003 c0000000 00105b2c ..............[,
stack: c000000005b0e610: c0000000 05b0e6a0 0031faa1 bd74990f .........1...t..
stack: c000000005b0e620: c0000000 00104f50 00000000 00000006 ......OP........
stack: c000000005b0e630: c0000000 05b0e6a0 0031faa1 bd74990f .........1...t..
kernel tried to execute exec-protected page (c000000005b0bbe0) - exploit
attemp? (uid: 0)
stack: c000000005b0e640: c0000000 00000001 c0000000 022f2a08 ............./*.
The last 2 lines were not in the netconsole.log but only were to be seen on the
screen of the frozen G5 so I added them manually.
--
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.
next prev parent reply other threads:[~2021-11-28 14:27 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 [this message]
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
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-i8LqeujfEW@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.