On Mon, Aug 25, 2014 at 5:53 AM, Matt Fleming wrote:
> On Mon, 25 Aug, at 02:08:59PM, Mantas Mikulėnas wrote:
>> [0.00] RAMDISK: [mem 0xbe22e000-0xbe799fff]
that is pushed down under 4G.
>
> OK, we're out of options here. Yinghai, we're going to have to revert
> your patch, 4bf7111f5016
On Mon, 25 Aug, at 02:08:59PM, Mantas Mikulėnas wrote:
>
> Well, all I could find is:
>
> > Freeing initrd memory: 5552K (8800be22e000 - 8800be79a000)
>
> Attaching the entire log.
Here we go,
> [0.00] RAMDISK: [mem 0xbe22e000-0xbe799fff]
OK, we're out of options here. Yinghai
On Sun, 24 Aug, at 10:19:04PM, Mantas Mikulėnas wrote:
>
> Finally got around to testing it, and yes, your patch fixes the initrd
> boot for me.
Could you found out where the initrd gets loaded with this patch? It'll
be in the dmesg.
--
Matt Fleming, Intel Open Source Technology Center
--
To un
On Fri, Aug 22, 2014 at 5:43 PM, Mantas Mikulėnas wrote:
>
> On Fri, Aug 22, 2014 at 5:24 PM, Harald Hoyer wrote:
> > On 09.08.2014 16:23, Mantas Mikulėnas wrote:
> >> As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
> >> the kernel freezes at the earliest possible moment wh
On Fri, Aug 22, 2014 at 5:24 PM, Harald Hoyer wrote:
> On 09.08.2014 16:23, Mantas Mikulėnas wrote:
>> As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
>> the kernel freezes at the earliest possible moment when trying to boot
>> via UEFI on my Asus laptop. (It still boots via
On 09.08.2014 16:23, Mantas Mikulėnas wrote:
> As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
> the kernel freezes at the earliest possible moment when trying to boot
> via UEFI on my Asus laptop. (It still boots via BIOS.)
>
> If I revert that commit on current master (c30
On 08/20/14 22:30, Matt Fleming wrote:
> [ 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 t
[ 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, 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
On Wed, 13 Aug, at 07:38:14PM, Mantas Mikulėnas wrote:
>
> Here you go.
>
> [0.00] BIOS-e820: [mem 0x0001-0x000137ff] usable
[...]
> [0.00] reserve setup_data: [mem
> 0x0001-0x000137ff] usable
[...]
> [0.00] efi: mem201: type=7,
On Wed, Aug 13, 2014 at 5:02 PM, Matt Fleming wrote:
>
> On Sun, 10 Aug, at 09:43:32PM, Mantas Mikulėnas wrote:
> > On Sun, Aug 10, 2014 at 8:55 AM, Yinghai Lu wrote:
> > > On Sat, Aug 9, 2014 at 3:45 PM, Mantas Mikulėnas
> > > wrote:
> > >> On Sat, Aug 9, 2014 at 10:23 PM, Matt Fleming
> > >
On Sun, 10 Aug, at 09:43:32PM, Mantas Mikulėnas wrote:
> On Sun, Aug 10, 2014 at 8:55 AM, Yinghai Lu wrote:
> > On Sat, Aug 9, 2014 at 3:45 PM, Mantas Mikulėnas wrote:
> >> On Sat, Aug 9, 2014 at 10:23 PM, Matt Fleming
> >> wrote:
> >> [However... Whether it's five chunks, four (after making th
On Sun, Aug 10, 2014 at 8:55 AM, Yinghai Lu wrote:
> On Sat, Aug 9, 2014 at 3:45 PM, Mantas Mikulėnas wrote:
>> On Sat, Aug 9, 2014 at 10:23 PM, Matt Fleming wrote:
>> [However... Whether it's five chunks, four (after making the initrd
>> smaller), or just one (with your efi=nochunk), I noticed
On Sat, Aug 9, 2014 at 3:45 PM, Mantas Mikulėnas wrote:
> On Sat, Aug 9, 2014 at 10:23 PM, Matt Fleming wrote:
> [However... Whether it's five chunks, four (after making the initrd
> smaller), or just one (with your efi=nochunk), I noticed that it
> *always* hangs during the *last* read, and the
On Sat, Aug 9, 2014 at 10:23 PM, Matt Fleming wrote:
>
> On Sat, 09 Aug, at 09:44:55AM, Yinghai Lu wrote:
> > On Sat, Aug 9, 2014 at 7:23 AM, Mantas Mikulėnas wrote:
> > > As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
> > > the kernel freezes at the earliest possible mome
On Sat, 09 Aug, at 09:44:55AM, Yinghai Lu wrote:
> On Sat, Aug 9, 2014 at 7:23 AM, Mantas Mikulėnas wrote:
> > As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
> > the kernel freezes at the earliest possible moment when trying to boot
> > via UEFI on my Asus laptop. (It still
On Sat, Aug 9, 2014 at 7:23 AM, Mantas Mikulėnas wrote:
> As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
> the kernel freezes at the earliest possible moment when trying to boot
> via UEFI on my Asus laptop. (It still boots via BIOS.)
>
> If I revert that commit on current
As of commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"),
the kernel freezes at the earliest possible moment when trying to boot
via UEFI on my Asus laptop. (It still boots via BIOS.)
If I revert that commit on current master (c309bfa9b481), it boots
correctly again [although I see "s
20 matches
Mail list logo
