[ Pulling in EDK2 folks for help ]
On Wed, 20 Aug, at 08:53:45PM, Michael Brown wrote:
> On 20/08/14 20:05, Mantas Mikulėnas wrote:
> >
> >I experimented with some things (like setting chunk size to a few kB
> >to see if it hangs earlier or only at the very end; etc.), and finally
> >found out tha
On 20/08/14 20:05, Mantas Mikulėnas wrote:
On Wed, Aug 20, 2014 at 8:05 PM, Matt Fleming wrote:
On Wed, 13 Aug, at 07:44:49PM, Matt Fleming wrote:
At this point, I think modifying the max address is the best way to
debug this further, and figure out what address causes the hang.
Mantas, did
On Wed, Aug 20, 2014 at 8:05 PM, Matt Fleming wrote:
> On Wed, 13 Aug, at 07:44:49PM, Matt Fleming wrote:
>>
>> At this point, I think modifying the max address is the best way to
>> debug this further, and figure out what address causes the hang.
>
> Mantas, did you manage to get to the bottom of
On Wed, Aug 20, 2014 at 06:10:57PM +0100, Matt Fleming wrote:
> On Thu, 14 Aug, at 12:32:05PM, Mark Rutland wrote:
> > On Wed, Jul 30, 2014 at 11:59:04AM +0100, Ard Biesheuvel wrote:
> > > If we cannot relocate the kernel Image to its preferred offset of base of
> > > DRAM
> > > plus TEXT_OFFSET,
On Thu, 14 Aug, at 12:32:05PM, Mark Rutland wrote:
> On Wed, Jul 30, 2014 at 11:59:04AM +0100, Ard Biesheuvel wrote:
> > If we cannot relocate the kernel Image to its preferred offset of base of
> > DRAM
> > plus TEXT_OFFSET, instead relocate it to the lowest available 2 MB boundary
> > plus
> >
On Wed, 13 Aug, at 07:44:49PM, Matt Fleming wrote:
>
> At this point, I think modifying the max address is the best way to
> debug this further, and figure out what address causes the hang.
Mantas, did you manage to get to the bottom of this issue?
--
Matt Fleming, Intel Open Source Technology