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: <alpine.DEB.2.21.9999.1910041037590.15827@viisi.sifive.com>
In-Reply-To: <alpine.DEB.2.21.9999.1910041037590.15827@viisi.sifive.com>
From:   Masahiro Yamada <yamada.masahiro@socionext.com>
Date:   Sat, 5 Oct 2019 12:12:52 +0900
Message-ID: <CAK7LNASZG1T4wQFTcaZyHx=hpKNG3d269=7uWBmdvxOt4s02Gw@mail.gmail.com>
Subject: Re: kbuild change breaks HiFive-U boot here
To:     Paul Walmsley <paul.walmsley@sifive.com>
Cc:     linux-riscv@lists.infradead.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Paul,

On Sat, Oct 5, 2019 at 2:48 AM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
>
> Commit 858805b336be1cabb3d9033adaa3676574d12e37 ("kbuild: add $(BASH) to
> run scripts with bash-extension") breaks my kernel test flow that targets
> the HiFive Unleashed board.  The boot traps during BBL early boot and
> stops.  QEMU is unaffected.  Reverting 858805b336be fixes the issue.

The reason is because
a shell script using bash-extension is run by 'sh' instead of 'bash'.

Run 'git grep CONFIG_SHELL', then can you find a suspicious script?
Is there a warning/error message in the build log?


> I haven't yet had the opportunity to root-cause the issue.  The issue may
> be related to idiosyncracies in my local boot testing process, rather
> than this commit.
>
>
> - Paul


-- 
Best Regards
Masahiro Yamada