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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 08AB5C433F5 for ; Wed, 6 Apr 2022 09:32:05 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4KYK6D3fQFz3bZC for ; Wed, 6 Apr 2022 19:32:04 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=QUqYwudk; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=gmail.com (client-ip=2a00:1450:4864:20::62a; helo=mail-ej1-x62a.google.com; envelope-from=zhouzhouyi@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=QUqYwudk; dkim-atps=neutral Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4KYK5T2cC4z2yPY for ; Wed, 6 Apr 2022 19:31:24 +1000 (AEST) Received: by mail-ej1-x62a.google.com with SMTP id qh7so2948640ejb.11 for ; Wed, 06 Apr 2022 02:31:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FI+EACkCTDn0l2CnSWYFgxS84Koe1S8eDRxILRKVO+w=; b=QUqYwudkm5hdLASSInYwknK32f48QP5wrARDQ0sfAKPa4GRifQ1IsWNHCEA6CUFdho mzxcQfPOyjJNtAEbp4nei8JQU05coMPHffudcBxYyAUNxt5L85Z6OcG7ALOk52Y8paRa IbYARhO7kcfEiZih9ggf2DKd/RRqSUrDYJ/IDN/iYcUe9JxBiE8W8YJ34g7MBNXk1E2f EVt1GGnMFv1KcmCQcoiGG5Hs4Hvftv8MWd00VyOZ9Gwf8BwrbTM+bcUE7547DUmb9k52 PZO61kSd5UgxSUuq51I/Nul2Kx5zdoD+QSzHPZYLRXM9qZHlY0JRLrWKmTkvXvIETT/E f/4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FI+EACkCTDn0l2CnSWYFgxS84Koe1S8eDRxILRKVO+w=; b=ZQDgKul9rUzYMK2QxgtXPIkL0sA/9Baxkex0ulASLFHf7/dBls+hx5/4OUvAWJsrSY H1d6PYa/HyknoyJz5PqKqsJ3+4Kt8GQg+8JAAJmysrHtXS9FyCIbjwyvpdsFGjX/SuVH vbwKzcx2vRTKx7XHNFsIQJ+kf+GZJu4UPsNgtEES1ymIMVgBT9kwipt0G0UWZjUob6CA DVcrRWiBhsNOuWfRYsOFNexcsLKV/Iw24OBL6SCfQ/EOj/krPO4DUCXP6TDb972xm3gH GovJ1y0K/I0vd5xDYFTfpizSjkt7cNoTA5dLBWBrRF7Pa28NkYuek5aECcIVpCNzXj0Z 7Riw== X-Gm-Message-State: AOAM5311K9+kLAYt/8u1Tm21pPjPRwP4/dhUWKbs2GnTXAOZiI+esLYy ccwDeDxAsvCofx4o8Warc6L3ehrKrjhFH7MufsY= X-Google-Smtp-Source: ABdhPJw8KQFjuLQmdXLOWEa2QDdz165o3Fngnj3VRfnJc7mZFia9owQqLuL5XH1JB37XLCcEbR4lIpRCuKC2KmxQ4x8= X-Received: by 2002:a17:907:6d07:b0:6e7:979e:9c0a with SMTP id sa7-20020a1709076d0700b006e7979e9c0amr7295488ejc.614.1649237481267; Wed, 06 Apr 2022 02:31:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Zhouyi Zhou Date: Wed, 6 Apr 2022 17:31:10 +0800 Message-ID: Subject: Re: rcu_sched self-detected stall on CPU To: Miguel Ojeda Content-Type: text/plain; charset="UTF-8" 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: , Cc: rcu , linuxppc-dev Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Hi I can reproduce it in a ppc virtual cloud server provided by Oregon State University. Following is what I do: 1) curl -l https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/snapshot/linux-5.18-rc1.tar.gz -o linux-5.18-rc1.tar.gz 2) tar zxf linux-5.18-rc1.tar.gz 3) cp config linux-5.18-rc1/.config 4) cd linux-5.18-rc1 5) make vmlinux -j 8 6) qemu-system-ppc64 -kernel vmlinux -nographic -vga none -no-reboot -smp 2 (QEMU 4.2.1) 7) after 12 rounds, the bug got reproduced: (http://154.223.142.244/logs/20220406/qemu.log.txt) Cheers ;-) Zhouyi On Wed, Apr 6, 2022 at 3:47 PM Miguel Ojeda wrote: > > Hi PPC/RCU, > > While merging v5.18-rc1 changes I noticed our CI PPC runs broke. I > reproduced the problem in v5.18-rc1 as well as next-20220405, under > both QEMU 4.2.1 and 6.1.0, with `-smp 2`; but I cannot reproduce it in > v5.17 from a few tries. > > Sadly, the problem is not deterministic although it is not too hard to > reproduce (1 out of 5?). Please see attached config and QEMU output. > > Cheers, > Miguel