From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 213837] New: "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5
Date: Fri, 23 Jul 2021 20:00:41 +0000 [thread overview]
Message-ID: <bug-213837-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213837
Bug ID: 213837
Summary: "Kernel panic - not syncing: corrupted stack end
detected inside scheduler" at building via distcc on a
G5
Product: Memory Management
Version: 2.5
Kernel Version: 5.13.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: akpm@linux-foundation.org
Reporter: erhard_f@mailbox.org
CC: platform_ppc-64@kernel-bugs.osdl.org
Regression: No
Created attachment 298017
--> https://bugzilla.kernel.org/attachment.cgi?id=298017&action=edit
dmesg (5.13.4, PowerMac G5 11,2)
Happens when building larger projects on my G5 via distcc. Time to failure is
about 3-10 minutes. Kernel 5.10.x does not show this problem. Probably
connected to bug #213079.
[..]
Call Trace:
Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 1 PID: 11467 Comm: powerpc64-unkno Tainted: G W
5.13.4-PowerMacG5+ #2
[c00000003e79ea80] [c000000000541c90] .dump_stack+0xe0/0x13c (unreliable)
[c00000003e79eb20] [c00000000006813c] .panic+0x168/0x430
[c00000003e79ebd0] [c00000000080a4b0] .__schedule+0x80/0x840
[c00000003e79ecb0] [c00000000080adbc] .preempt_schedule_common+0x28/0x48
[c00000003e79ed30] [c00000000080ae0c] .__cond_resched+0x30/0x4c
[c00000003e79edb0] [c0000000001c6d80] .mempool_alloc+0x38/0x198
[c00000003e79ee90] [c00000000049a444] .bio_alloc_bioset+0x94/0x174
[c00000003e79ef40] [c00000000049a544] .bio_clone_fast+0x20/0x7c
[c00000003e79efd0] [c00000000049a60c] .bio_split+0x6c/0xc4
[c00000003e79f060] [c0000000004a7018] .__blk_queue_split+0x120/0x474
[c00000003e79f160] [c0000000004adc30] .blk_mq_submit_bio+0x88/0x524
[c00000003e79f250] [c0000000004a0e30] .submit_bio_noacct+0xc4/0x26c
[c00000003e79f340] [c000000000355bec] .ext4_io_submit+0x5c/0x70
[c00000003e79f3c0] [c000000000355f08] .ext4_bio_write_page+0x2f4/0x480
[c00000003e79f480] [c000000000334b84] .mpage_submit_page+0x70/0xa0
[c00000003e79f500] [c00000000033b09c] .ext4_writepages+0xcc4/0xe5c
[c00000003e79f7b0] [c0000000001cf214] .do_writepages+0x54/0xa0
[c00000003e79f830] [c0000000001c3ab8] .__filemap_fdatawrite_range+0xc0/0xfc
[c00000003e79f930] [c000000000337f34] .ext4_alloc_da_blocks+0xf4/0x100
[c00000003e79f9b0] [c000000000328594] .ext4_release_file+0x24/0xd8
[c00000003e79fa40] [c00000000026ea5c] .__fput+0x12c/0x270
[c00000003e79fae0] [c00000000008eb40] .task_work_run+0xa0/0xc0
[c00000003e79fb70] [c00000000006e284] .do_exit+0x55c/0xa6c
[c00000003e79fc60] [c00000000006e824] .do_group_exit+0x50/0xb0
[c00000003e79fcf0] [c00000000006e898] .__wake_up_parent+0x0/0x34
[c00000003e79fd60] [c000000000021540] .system_call_exception+0x1b4/0x1ec
[c00000003e79fe10] [c00000000000b9c4] system_call_common+0xe4/0x214
--- interrupt: c00 at 0x3fffadc46aa8
NIP: 00003fffadc46aa8 LR: 00003fffadba6d04 CTR: 0000000000000000
REGS: c00000003e79fe80 TRAP: 0c00 Tainted: G W
(5.13.4-PowerMacG5+)
MSR: 900000000200f032 <SF,HV,VEC,EE,PR,FP,ME,IR,DR,RI> CR: 22000482 XER:
00000000
IRQMASK: 0
GPR00: 00000000000000ea 00003ffff3f1ae50 00003fffadd65300 0000000000000000
GPR04: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR12: 0000000000000000 00003fffadeddc30 000000014af075a0 000000012379b0f0
GPR16: 000000012947ec38 00003fffd7d95cd8 000000012947eb28 000000000000002f
GPR20: 0000000000000000 00003fffadd5fff8 0000000000000001 00003fffadd5ea58
GPR24: 0000000000000000 0000000000000000 0000000000000003 0000000000000001
GPR28: 0000000000000000 00003fffaded6c50 fffffffffffff000 0000000000000000
NIP [00003fffadc46aa8] 0x3fffadc46aa8
LR [00003fffadba6d04] 0x3fffadba6d04
--- interrupt: c00
Rebooting in 40 seconds..
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching someone on the CC list of the bug.
next reply other threads:[~2021-07-23 20:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 20:00 bugzilla-daemon [this message]
2021-07-23 20:01 ` [Bug 213837] "Kernel panic - not syncing: corrupted stack end detected inside scheduler" at building via distcc on a G5 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
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@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.