Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 16.3.2018 16:18, Rob Herring wrote: > On Wed, Mar 14, 2018 at 10:04 AM, Michal Simek wrote: >> On 12.3.2018 11:21, Michal Simek wrote: >>> On 12.3.2018 08:52, Alvaro G. M. wrote: On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: > On Fri, Mar 9, 2018 at

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 16.3.2018 16:18, Rob Herring wrote: > On Wed, Mar 14, 2018 at 10:04 AM, Michal Simek wrote: >> On 12.3.2018 11:21, Michal Simek wrote: >>> On 12.3.2018 08:52, Alvaro G. M. wrote: On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: > On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G.

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On Wed, Mar 14, 2018 at 10:04 AM, Michal Simek wrote: > On 12.3.2018 11:21, Michal Simek wrote: >> On 12.3.2018 08:52, Alvaro G. M. wrote: >>> On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M.

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On Wed, Mar 14, 2018 at 10:04 AM, Michal Simek wrote: > On 12.3.2018 11:21, Michal Simek wrote: >> On 12.3.2018 08:52, Alvaro G. M. wrote: >>> On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: > Hi, > > I've

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 12.3.2018 11:21, Michal Simek wrote: > On 12.3.2018 08:52, Alvaro G. M. wrote: >> On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: >>> On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. >>> wrote: Hi, I've found via git bisect that

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 12.3.2018 11:21, Michal Simek wrote: > On 12.3.2018 08:52, Alvaro G. M. wrote: >> On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: >>> On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. >>> wrote: Hi, I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 12.3.2018 08:52, Alvaro G. M. wrote: > On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: >> On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: >>> Hi, >>> >>> I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b >>> makes microblaze

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 12.3.2018 08:52, Alvaro G. M. wrote: > On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: >> On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: >>> Hi, >>> >>> I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b >>> makes microblaze unbootable. >>> >>> I'm sorry

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: > On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: > > Hi, > > > > I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b > > makes microblaze unbootable. > > > > I'm sorry I can't provide

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: > On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: > > Hi, > > > > I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b > > makes microblaze unbootable. > > > > I'm sorry I can't provide any console output, as

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 9.3.2018 20:05, Rob Herring wrote: > On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: >> Hi, >> >> I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b >> makes microblaze unbootable. >> >> I'm sorry I can't provide any console output, as nothing

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On 9.3.2018 20:05, Rob Herring wrote: > On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: >> Hi, >> >> I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b >> makes microblaze unbootable. >> >> I'm sorry I can't provide any console output, as nothing appears at all, >> even

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: > Hi, > > I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b > makes microblaze unbootable. > > I'm sorry I can't provide any console output, as nothing appears at all, > even when setting

Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. wrote: > Hi, > > I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b > makes microblaze unbootable. > > I'm sorry I can't provide any console output, as nothing appears at all, > even when setting earlyprintk (or at least I wasn't

Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

Hi, I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b makes microblaze unbootable. I'm sorry I can't provide any console output, as nothing appears at all, even when setting earlyprintk (or at least I wasn't able to get anything back!). I'm providing both dts and defconfig

Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

Hi, I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b makes microblaze unbootable. I'm sorry I can't provide any console output, as nothing appears at all, even when setting earlyprintk (or at least I wasn't able to get anything back!). I'm providing both dts and defconfig