From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 77520C433EF for ; Thu, 23 Sep 2021 16:30:20 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7F02C60FC1 for ; Thu, 23 Sep 2021 16:30:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 7F02C60FC1 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=bugzilla.kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4HFgcn6l5zz302W for ; Fri, 24 Sep 2021 02:30:17 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=mIn/kf4j; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=bugzilla.kernel.org (client-ip=198.145.29.99; helo=mail.kernel.org; envelope-from=bugzilla-daemon@bugzilla.kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=mIn/kf4j; dkim-atps=neutral Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4HFgc03HcMz2xY4 for ; Fri, 24 Sep 2021 02:29:36 +1000 (AEST) Received: by mail.kernel.org (Postfix) with ESMTPS id 53DD160F4C for ; Thu, 23 Sep 2021 16:29:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1632414573; bh=6oc49AygF4MdKCSC+x5iyXb0svZPo/FkEhYu3+8o8ps=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mIn/kf4jU4cTZlfD/+cNmRwSiz2wMaRoI2ry6Ld8YRqb71m/77S5AKs36ZODc/Vpb 7XNfoFGUC9ygrrs3mW5EaevI8azQQUlFMs3lgKjbQHeS1vOyRAue1Bc0Av4bHRGqs3 u9rnFo0f/Fi98F8tCqzERUelNitqznjRd87VxVdAqjNguvIU1f16XiW2hRKKJbVL3C Zrk85AxnerQBTnP/7b46ZMPd5gxMleZnseFTqbpy2Yae0Q3MolNQpwAo6cQpOatgsH JQnEZyu/0Rnk//45NrObArkBBu/IlIQX2Xvs7jJditFOq5XwCjH6/TDVORlxgYa4Wq KDVb2qq3/zWrg== 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: Thu, 23 Sep 2021 16:29:32 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo CC platform_ppc-64@kernel-bugs.osdl.org X-Bugzilla-Product: Platform Specific/Hardware X-Bugzilla-Component: PPC-64 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: erhard_f@mailbox.org X-Bugzilla-Status: NEEDINFO X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: platform_ppc-64@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" https://bugzilla.kernel.org/show_bug.cgi?id=3D213837 --- Comment #9 from Erhard F. (erhard_f@mailbox.org) --- Created attachment 298933 --> https://bugzilla.kernel.org/attachment.cgi?id=3D298933&action=3Dedit System.map (5.15-rc2 + patch, PowerMac G5 11,2) (In reply to mpe from comment #8) > So it looks like you have actually overran your stack, rather than > something else clobbering your stack. >=20 > Can you attach your System.map for that exact kernel? We might be able > to work out what functions we were in when we overran. >=20 > You could also try changing CONFIG_THREAD_SHIFT to 15, that might keep > the system running a bit longer and give us some other clues. >=20 > cheers Hm, interesting... What I do to trigger this bug is building llvm-12 on the G5 via distcc (on = the other side is a 16-core Opteron) and MAKEOPTS=3D"-j10 -l3". As the G5 got 1= 6 GiB RAM building runs in a zstd-compressed ext2 filesystem (/sbin/zram-init -d1= -s2 -azstd -text2 -orelatime -m1777 -Lvar_tmp_dir 49152 /var/tmp). Most of the = time the bug is triggered very shortly after the actual building starts via meso= n. At this time the build directory /var/tmp/portage occupies about 800 MiB. Also sometimes I don't get a proper stack trace via netconsole but this: BUG: unable to handle kernel data access on write at 0xc000000037c82040 BUG: unable to handle kernel data access on write at 0xc000000037c80000 Please find the relevant System.map attached. I'll do another kernel build = with CONFIG_THREAD_SHIFT=3D15 and see if anything changes. Thanks for investigating this! --=20 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.=