From mboxrd@z Thu Jan  1 00:00:00 1970
From: hch@lst.de <hch@lst.de>
Date: Thu, 20 Dec 2018 15:46:04 +0100
Subject: [OpenRISC] ensure dma_alloc_coherent always returns zeroed
	memory
In-Reply-To: <1545316759.14089.22.camel@synopsys.com>
References: <20181214082515.14835-1-hch@lst.de>
 <20181219165939.GA26087@lst.de> <1545316369.14089.20.camel@synopsys.com>
 <20181220143415.GA17726@lst.de> <1545316759.14089.22.camel@synopsys.com>
Message-ID: <20181220144604.GA18034@lst.de>
List-Id: <openrisc.lists.librecores.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: openrisc@lists.librecores.org

On Thu, Dec 20, 2018 at 02:39:20PM +0000, Eugeniy Paltsev wrote:
> > I would be really surprised if that is caused by the patch to add
> > the zeroing. 
> Me too :)
> 
> >  Can you check which commit caused the issue by bisecting
> > from a known good baseline?
> 
> Yep. At least kernel build from v4.20-rc4 (which is base for your branch)
> seems to work fine.

Well, the branch has quite a few commits.  Can you check the commit
just before the zeroing to start, and if that is already broken (which
I suspect) bisect the offending commit?