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;
MIME-Version: 1.0
References: <5d94766b.1c69fb81.6d9f4.dc6d@mx.google.com> <d8357536-6750-d9ba-e114-30944d8f95ab@collabora.com>
 <20191002.102417.205729199993915832.davem@davemloft.net>
In-Reply-To: <20191002.102417.205729199993915832.davem@davemloft.net>
From:   Masahiro Yamada <yamada.masahiro@socionext.com>
Date:   Thu, 3 Oct 2019 02:26:56 +0900
Message-ID: <CAK7LNAR2Cx+3z6QUO_WSURc2Cq6sQhxB5R+U2EyvVnk_s5cn0g@mail.gmail.com>
Subject: Re: net-next/master boot bisection: v5.3-13203-gc01ebd6c4698 on bcm2836-rpi-2-b
To:     David Miller <davem@davemloft.net>
Cc:     Guillaume Tucker <guillaume.tucker@collabora.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        mgalka@collabora.com, Mark Brown <broonie@kernel.org>,
        matthew.hart@linaro.org, Kevin Hilman <khilman@baylibre.com>,
        Enric Balletbo i Serra <enric.balletbo@collabora.com>,
        Nick Desaulniers <ndesaulniers@google.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        tomeu.vizoso@collabora.com, urezki@gmail.com,
        Joe Lawrence <joe.lawrence@redhat.com>,
        Kees Cook <keescook@chromium.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
        Changbin Du <changbin.du@intel.com>,
        Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
        Sri Krishna chowdary <schowdary@nvidia.com>,
        Catalin Marinas <catalin.marinas@arm.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Oct 3, 2019 at 2:24 AM David Miller <davem@davemloft.net> wrote:
>
> From: Guillaume Tucker <guillaume.tucker@collabora.com>
> 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. :-)


The fix and related discussions are available.

https://lore.kernel.org/patchwork/patch/1132785/


-- 
Best Regards
Masahiro Yamada