Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1097774ybn; Wed, 2 Oct 2019 10:48:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqxnet9srjIjM6+UTBNTWSNyIf4Z0GWuqRtpRFx/Xc9zZaZazKFe9/9X10jf29ArMGqp7Emd X-Received: by 2002:a17:906:8041:: with SMTP id x1mr4141213ejw.132.1570038500455; Wed, 02 Oct 2019 10:48:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570038500; cv=none; d=google.com; s=arc-20160816; b=XPxacbTeqc2tq3NYD4SdX5W1eou8tXDuNQs1vVRwIe0xxnG16e4k8JdV0NdX0M5qZY 0CPmAVk5TVY2WFLVDQEc75PnNwxTNXCTtz/VgonmAn+VVEmoTBSjK8ZlMSawK512KjJR V1K6pofsM40ir4gsuT00pebNdxwcxHbA/pNQLTx90ZQ+tDk3XXK7CjcXqZmz0RiPKhMg ZlmV94Yt7eeky0LFI5xogaMbWwQ5vCWKfFKe0GMpmrzNU51RY0I/0cVj7BlcbBVo2wyy KLX4Xv9qgFzF1J+00gURTNzRDhRojEBSisyYBevi/E6ADcZuCenVltAVAP8lbYM+rI+8 Odzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=KgEQHljyOzATJ04VSg3nvPwHN3BTb7QVl8pHA4U7hPo=; b=YzTZn/YPdtucdz1kt4Wt8NemGjcfNpjLd1crCDez4uFrFR+Sa0JTHMtG1hnrIMifdp Z5m2GaUMRH4DG6bTDgAgzW+0KyNVzbNldJLlT6adrp6jWNHn/oyujWCBjAWd0SH/3pnp KdcU4x1vmpXMBMs4zev2DdW9sYlpxeMnSluFE77pq7BMnl2soVFYhNOogyK63f0XnjeQ KbF7E7l691whAvR+QJVQ/5kp0ZOo3x+5c3lx50SFzkDupiBuGApsDzoJB0YxpCIh2OYp TWbMqyMBj5hRmYBZIDtp/jovyoye2RvVYiihz5aRWwoLfMnihfQVKylNPaDJwLyMXWQ+ qMiw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h26si12176410edb.141.2019.10.02.10.47.55; Wed, 02 Oct 2019 10:48:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728575AbfJBRoU (ORCPT + 99 others); Wed, 2 Oct 2019 13:44:20 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:57806 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726076AbfJBRoT (ORCPT ); Wed, 2 Oct 2019 13:44:19 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: gtucker) with ESMTPSA id 5270228F755 Subject: Re: net-next/master boot bisection: v5.3-13203-gc01ebd6c4698 on bcm2836-rpi-2-b To: Masahiro Yamada , David Miller Cc: Linus Torvalds , mgalka@collabora.com, Mark Brown , matthew.hart@linaro.org, Kevin Hilman , Enric Balletbo i Serra , Nick Desaulniers , Andrew Morton , tomeu.vizoso@collabora.com, urezki@gmail.com, Joe Lawrence , Kees Cook , Linux Kernel Mailing List , Andy Shevchenko , Changbin Du , Tetsuo Handa , Sri Krishna chowdary , Catalin Marinas References: <5d94766b.1c69fb81.6d9f4.dc6d@mx.google.com> <20191002.102417.205729199993915832.davem@davemloft.net> From: Guillaume Tucker Message-ID: Date: Wed, 2 Oct 2019 18:44:14 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/10/2019 18:26, Masahiro Yamada wrote: > On Thu, Oct 3, 2019 at 2:24 AM David Miller wrote: >> >> From: Guillaume Tucker >> Date: Wed, 2 Oct 2019 18:21:31 +0100 >> >>> It seems like this isn't the case on the Raspberry Pi 2b with >>> bcm2835_defconfig. Here's an example of the kernel errors: >> >> This has been fixed upstream I believe, it was some ARM assembler issue >> or something like that. >> >> In any event, definitely not a networking problem. :-) Quite, and there was also a bisection on the clk-next branch. If some subsystem branches don't rebase with the fix and the problem keeps happening then we'll be disabling boot bisections for them temporarily to avoid email noise. On a side note, we're also planning to add a way to mark a revision as fixed to stop reporting particular failures that have been fixed upstream - but that's not possible at the moment. > The fix and related discussions are available. > > https://lore.kernel.org/patchwork/patch/1132785/ Great, thanks! Sorry I missed that thread. Thank you also for having mentioned the kernelci.org bot in the fix. Guillaume