Re: Kernel v5.2+ on HiKey960?

From: Will Deacon <will@kernel.org>
To: Jerome Forissier <jerome@forissier.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	maz@kernel.org
Subject: Re: Kernel v5.2+ on HiKey960?
Date: Fri, 6 Dec 2019 16:09:56 +0000	[thread overview]
Message-ID: <20191206160955.GA27982@willie-the-truck> (raw)
In-Reply-To: <e3ac6a90-c6e7-460e-087a-880e3735051e@forissier.org>

On Thu, Dec 05, 2019 at 03:54:10PM +0100, Jerome Forissier wrote:
> On 12/5/19 9:57 AM, Will Deacon wrote:
> > On Thu, Dec 05, 2019 at 08:26:48AM +0100, Jerome Forissier wrote:
> >> On 12/4/19 6:57 PM, Will Deacon wrote:
> >>> On Wed, Dec 04, 2019 at 03:58:57PM +0100, Jerome Forissier wrote:
> >>>> Fails indeed (panic): https://pastebin.com/F0jpktii
> >>>
> >>> Interesting. I followed your instructions and my board boots fine even
> >>> after applying that patch, but then I see the following on shutdown:
> >>>
> >>> [   83.022955] WARNING: CPU: 0 PID: 1995 at kernel/time/tick-broadcast.c:647 tick_handle_oneshot_broadcast+0x1c8/0x1e8
> >>> [   83.033392] Modules linked in:
> >>> [   83.036447] CPU: 0 PID: 1995 Comm: init Tainted: G S                5.1.0-253105-g2b41f6584d59 #3
> >>
> >> That is not v5.1 plus one commit, is it?
> > 
> > No, and I wasn't claiming that it was. 
> 
> ;-) My apologies, I was confused.
> 
> > I followed the instructions you pointed us to [1] and cherry-picked 75a19a0202db> on top. If there's something different that I need to do in order to
> reproduce> the problem, then please holler.
> > My experience with Hikey960 has been 100% "bloody awful"
> > so I don't have a good setup for simply building and running a kernel on it.
> > 
> > I also had to hack some of the EDK2 code in there to get it to compile, so
> > it continues to live up to expectations.
> 
> What error did you encounter? Is it this one by chance?
> 
>  error: ‘__builtin_strncpy’ output truncated [...]
> 
> I just noticed GCC 9.x shows this, while GCC 8.x doesn't. So it depends
> on what distribution you are using. I will need to do something to
> address this problem.

I just bodged it with a strcpy(), but that's probably not the right fix.

That aside, I'm perplexed that I can't reproduce the exact problem you're
seeing. Are you doing anything other than thos instructions you provided?
(e.g. different .config, command line, userspace)

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel