Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp2013713rwb; Thu, 19 Jan 2023 19:28:33 -0800 (PST) X-Google-Smtp-Source: AMrXdXtJ7FjwbEKANwEMEV7AnFPvyDELtdtYkYAKKKJhnDewKsB2EC0dn0HMhkJtgIFlGQU1h3Nf X-Received: by 2002:a17:902:cec9:b0:195:e480:acec with SMTP id d9-20020a170902cec900b00195e480acecmr950110plg.5.1674185313026; Thu, 19 Jan 2023 19:28:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674185313; cv=none; d=google.com; s=arc-20160816; b=gFRZhVGlmfBC1ehIvzyfkoIoC0bO44l16Um71xkoCyawh5igAcTJUOAFvxcdeA8xHo +0vBH5fowru4mGyOQvoW9N+b5e518Qx6aiHCnJPGWfp18W5fjjSdhqBqFCU40johif0b +cmCJHjFCkVFUtWUooiGK+rfWFXpO3KqOE91D0tXI5hZNKkzNOuN3sSHjFuuN57/RJfJ qSjMqUVI3Ksw+WIdvhrzjV/mdBRxgQ06g6t5LdQ4sBW3eIzsBTe+AAjjKiWWRmDEnQWN 9bUmHj67OwlYd7Ws4SabCN/3bzT/yvj8D4vFZeKc9FFOwgJgzyWDP9FdGzBHkw3TEHv+ tvHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:references :in-reply-to:mime-version:dkim-signature; bh=3Hpc5Ciyxu29gomOTvRt7HRyn5ui+yh0jFZKfccP/3A=; b=U6+W23ME1N0t4Zy5/G3Ak0IQazBfWQNOomYhc0JSDSOs1Algy85aoLUrw8JmAaqXGj euC3r19YDkFMF/zPVGq4Q7/y5b7uoubEFeU6Jw7VLNwDhqiH10tvkWPrkfOvLe357IKg rjXYRrIqZwRics1yhIZwaP8PbYID+oaMMIOyVu1JGTYgd+JnxSY+A9AmDbEqcGvW4fbm k5M7yLxNZVrpuQdD0feZtP9n5L4D7RYXG+gOoQx8e2B8XBghCNo6oYcsipVQ/1wTf6rb OdUmTa/MARfaLVNjUpAecDXR96ttloRcJQjJM779g+qQALwYrFleDx8kwzDALfwipY5x 2okQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@draconx-ca.20210112.gappssmtp.com header.s=20210112 header.b=6ipErWbF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bj12-20020a170902850c00b00176953fee67si5608815plb.86.2023.01.19.19.28.26; Thu, 19 Jan 2023 19:28:33 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@draconx-ca.20210112.gappssmtp.com header.s=20210112 header.b=6ipErWbF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229731AbjATDQI (ORCPT + 46 others); Thu, 19 Jan 2023 22:16:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34484 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229814AbjATDQA (ORCPT ); Thu, 19 Jan 2023 22:16:00 -0500 Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4D5D7B1EDE for ; Thu, 19 Jan 2023 19:15:39 -0800 (PST) Received: by mail-vs1-xe33.google.com with SMTP id i185so4359699vsc.6 for ; Thu, 19 Jan 2023 19:15:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=draconx-ca.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3Hpc5Ciyxu29gomOTvRt7HRyn5ui+yh0jFZKfccP/3A=; b=6ipErWbF5wYAMGrwowJPn2VP4KJ9ijlP4WCHTjoDjDh9WU2oC66c2szaAh27ljPc/2 /qcJlPmhvqZmNOYwkIXjFzWXXYg3MM+iGn+Mv3KFuOdX692Pmq0PW5Z7IcBwlMFLjDpT r2tUwTkUAm9b0oCWn3acyclThA0FWFRKYmWlrcjw+AYHlcXhWfSIgH0tkXNqrWEjeTrQ L6NMCRU0hmCZUWhwYST4V6b6L4P6XUhlyvTw8zLAZZd5CMnYiYGIusHPB8xwEdTVSQGu /Wis04U9Zb5RvqO9FjEV3MuaPyXKgigSsleVPI8wC0SMbslSqQP6AsNmsXpW1ZQaZIha 0zuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3Hpc5Ciyxu29gomOTvRt7HRyn5ui+yh0jFZKfccP/3A=; b=Zog6c3BSMgLHqps84sFfWei8t74zKVh/d59u1tHeHu6xEAcHYTExfC059vL29IGiqO TEOB7A2jKf9Czg9aEbcDX5rkULBinQ4/Y5e3kqgc7tMTUG3jqvveVkiyxWwiFh8cp42e gcI7cBe8RFcHKMuTumWux1+J5yK53olArCIwzmsHTc2YYzXXbQEsiodArR+Wm5aZJ+Yj Ce9Lenojl7RQSPlNreU36iRC8hagnIjmvKp/CzGqfWkqK4UOGEB8BuwvLkSaImKXS6CN cQG5NxUxKsEck4M8m7mZD0poKCxyFDmy0ow91fxsz9E1YbmP8+ITKfM0zbIGRQr9mbGM JvIw== X-Gm-Message-State: AFqh2kqyJD5+b5c2cwKNZ/KhMSaRBnwsAiP7cvWkNrEIO78W5UcBHIdk uBarFGiBm0UkiCZQz2dZjbaIju+lVCqnYXjrn3wC2urUKgFr0VS6Mr4= X-Received: by 2002:a05:6102:1510:b0:3d3:e5dc:e359 with SMTP id f16-20020a056102151000b003d3e5dce359mr1785070vsv.61.1674184538020; Thu, 19 Jan 2023 19:15:38 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6130:1015:b0:559:9619:d862 with HTTP; Thu, 19 Jan 2023 19:15:37 -0800 (PST) X-Originating-IP: [24.53.241.20] In-Reply-To: References: From: Nick Bowler Date: Thu, 19 Jan 2023 22:15:37 -0500 Message-ID: Subject: Re: PROBLEM: Only one CPU active on Ultra 60 since ~4.8 (regression) To: sparclinux@vger.kernel.org Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I'm resending this report CC'd to linux-kernel as there was no response on the sparclinux list. I tried 6.2-rc4 and there is no change in behaviour. Reverting the indicated commit still works to fix the problem. On 2022-07-12, Nick Bowler wrote: > When using newer kernels on my Ultra 60 with dual 450MHz UltraSPARC-II > CPUs, I noticed that only CPU 0 comes up, while older kernels (including > 4.7) are working fine with both CPUs. > > I bisected the failure to this commit: > > 9b2f753ec23710aa32c0d837d2499db92fe9115b is the first bad commit > commit 9b2f753ec23710aa32c0d837d2499db92fe9115b > Author: Atish Patra > Date: Thu Sep 15 14:54:40 2016 -0600 > > sparc64: Fix cpu_possible_mask if nr_cpus is set > > This is a small change that reverts very easily on top of 5.18: there is > just one trivial conflict. Once reverted, both CPUs work again. > > Maybe this is related to the fact that the CPUs on this system are > numbered CPU0 and CPU2 (there is no CPU1)? > > Here is /proc/cpuinfo on a working kernel: > > % cat /proc/cpuinfo > cpu : TI UltraSparc II (BlackBird) > fpu : UltraSparc II integrated FPU > pmu : ultra12 > prom : OBP 3.23.1 1999/07/16 12:08 > type : sun4u > ncpus probed : 2 > ncpus active : 2 > D$ parity tl1 : 0 > I$ parity tl1 : 0 > cpucaps : flush,stbar,swap,muldiv,v9,mul32,div32,v8plus,vis > Cpu0ClkTck : 000000001ad31b4f > Cpu2ClkTck : 000000001ad31b4f > MMU Type : Spitfire > MMU PGSZs : 8K,64K,512K,4MB > State: > CPU0: online > CPU2: online > > And on a broken kernel: > > % cat /proc/cpuinfo > cpu : TI UltraSparc II (BlackBird) > fpu : UltraSparc II integrated FPU > pmu : ultra12 > prom : OBP 3.23.1 1999/07/16 12:08 > type : sun4u > ncpus probed : 2 > ncpus active : 1 > D$ parity tl1 : 0 > I$ parity tl1 : 0 > cpucaps : flush,stbar,swap,muldiv,v9,mul32,div32,v8plus,vis > Cpu0ClkTck : 000000001ad31861 > MMU Type : Spitfire > MMU PGSZs : 8K,64K,512K,4MB > State: > CPU0: online > > Let me know if you need any more info. > > Thanks, > Nick