98e7a989979b185f49e86ddaed2ad6890299d9f0 fixes that and now it crashes
while
trying to unpack the initrd with a completely different backtrace.
ok, did you post the boot log for that failing boot ?
Yes, the bootlog is attached, but I also send it as "3.9 breaks EFI boot
on
E350 v2" to LKML with
also send it as 3.9 breaks EFI boot
on
E350 v2 to LKML with a request for help.
can you boot with appending with memtest?
Sure, bootlog with memtest is attached.
Please check attached patch, it should fix the problem.
Works perfectly, thanks allot.
Christian.
Thanks
Yinghai
ad6890299d9f0 fixes that and now it crashes
>>>>> while
>>>>> trying to unpack the initrd with a completely different backtrace.
>>>>>
>>>> ok, did you post the boot log for that failing boot ?
>>>
>>>
>>> Yes,
with a completely different backtrace.
ok, did you post the boot log for that failing boot ?
Yes, the bootlog is attached, but I also send it as "3.9 breaks EFI boot on
E350 v2" to LKML with a request for help.
can you boot with appending with "memtest"?
Sure, bootlog with
it crashes
while
trying to unpack the initrd with a completely different backtrace.
ok, did you post the boot log for that failing boot ?
Yes, the bootlog is attached, but I also send it as 3.9 breaks EFI boot on
E350 v2 to LKML with a request for help.
can you boot with appending with memtest
EFI boot
on
E350 v2 to LKML with a request for help.
can you boot with appending with memtest?
Sure, bootlog with memtest is attached.
Please check attached patch, it should fix the problem.
Thanks
Yinghai
merge_mapped_range.patch
Description: Binary data
t;> 98e7a989979b185f49e86ddaed2ad6890299d9f0 fixes that and now it crashes
>>> while
>>> trying to unpack the initrd with a completely different backtrace.
>>>
>> ok, did you post the boot log for that failing boot ?
>
>
> Yes, the bootlog is attached, b
, the bootlog is attached, but I also send it as "3.9 breaks EFI boot
on E350 v2" to LKML with a request for help.
Christian.
Thanks
Yinghai
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.9.0-030900-ge
On Thu, May 16, 2013 at 5:49 AM, Christian König
wrote:
> Am 16.05.2013 11:41, schrieb Christian König:
>
> Ups, the board DOES have a serial port, and I've got a log now that shows
> the mentioned patch above isn't the root cause.
>
> After commit 8d57470d8f859635deffe3919d7d4867b488b85a it
Hi everybody,
the following crash happens when booting one of our E350 based test
system in EFI mode, booting with in BIOS compatibility mode works fine.
Bisecting initially turned out to be commit
8d57470d8f859635deffe3919d7d4867b488b85a, but that turned out to be a
false positive and
Am 16.05.2013 11:41, schrieb Christian König:
Am 15.05.2013 22:57, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 8:20 AM, Christian König
wrote:
Am 15.05.2013 16:46, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 2:46 AM, Christian König
wrote:
Hi guys,
the following commit breaks booting my
Am 15.05.2013 22:57, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 8:20 AM, Christian König
wrote:
Am 15.05.2013 16:46, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 2:46 AM, Christian König
wrote:
Hi guys,
the following commit breaks booting my E350 based test system in EFI
mode:
commit
Am 15.05.2013 22:57, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 8:20 AM, Christian König
christian.koe...@amd.com wrote:
Am 15.05.2013 16:46, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 2:46 AM, Christian König
christian.koe...@amd.com wrote:
Hi guys,
the following commit breaks booting my
Am 16.05.2013 11:41, schrieb Christian König:
Am 15.05.2013 22:57, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 8:20 AM, Christian König
christian.koe...@amd.com wrote:
Am 15.05.2013 16:46, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 2:46 AM, Christian König
christian.koe...@amd.com wrote:
Hi everybody,
the following crash happens when booting one of our E350 based test
system in EFI mode, booting with in BIOS compatibility mode works fine.
Bisecting initially turned out to be commit
8d57470d8f859635deffe3919d7d4867b488b85a, but that turned out to be a
false positive and
On Thu, May 16, 2013 at 5:49 AM, Christian König
christian.koe...@amd.com wrote:
Am 16.05.2013 11:41, schrieb Christian König:
Ups, the board DOES have a serial port, and I've got a log now that shows
the mentioned patch above isn't the root cause.
After commit
for that failing boot ?
Yes, the bootlog is attached, but I also send it as 3.9 breaks EFI boot
on E350 v2 to LKML with a request for help.
Christian.
Thanks
Yinghai
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.9.0
the initrd with a completely different backtrace.
ok, did you post the boot log for that failing boot ?
Yes, the bootlog is attached, but I also send it as 3.9 breaks EFI boot on
E350 v2 to LKML with a request for help.
can you boot with appending with memtest?
Thanks
Yinghai
On Wed, May 15, 2013 at 8:20 AM, Christian König
wrote:
> Am 15.05.2013 16:46, schrieb Yinghai Lu:
>
>> On Wed, May 15, 2013 at 2:46 AM, Christian König
>> wrote:
>>>
>>> Hi guys,
>>>
>>> the following commit breaks booting my E350 based test system in EFI
>>> mode:
>>>
commit
Am 15.05.2013 16:46, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 2:46 AM, Christian König
wrote:
Hi guys,
the following commit breaks booting my E350 based test system in EFI mode:
commit 8d57470d8f859635deffe3919d7d4867b488b85a
Author: Yinghai Lu
Date: Fri Nov 16 19:38:58 2012 -0800
On Wed, May 15, 2013 at 2:46 AM, Christian König
wrote:
> Hi guys,
>
> the following commit breaks booting my E350 based test system in EFI mode:
>
>> commit 8d57470d8f859635deffe3919d7d4867b488b85a
>> Author: Yinghai Lu
>> Date: Fri Nov 16 19:38:58 2012 -0800
>>
>> x86, mm: setup page
Hi guys,
the following commit breaks booting my E350 based test system in EFI mode:
commit 8d57470d8f859635deffe3919d7d4867b488b85a
Author: Yinghai Lu
Date: Fri Nov 16 19:38:58 2012 -0800
x86, mm: setup page table in top-down
This commit was supposed to fix it but obviously there
Hi guys,
the following commit breaks booting my E350 based test system in EFI mode:
commit 8d57470d8f859635deffe3919d7d4867b488b85a
Author: Yinghai Lu ying...@kernel.org
Date: Fri Nov 16 19:38:58 2012 -0800
x86, mm: setup page table in top-down
This commit was supposed to fix it but
On Wed, May 15, 2013 at 2:46 AM, Christian König
christian.koe...@amd.com wrote:
Hi guys,
the following commit breaks booting my E350 based test system in EFI mode:
commit 8d57470d8f859635deffe3919d7d4867b488b85a
Author: Yinghai Lu ying...@kernel.org
Date: Fri Nov 16 19:38:58 2012 -0800
Am 15.05.2013 16:46, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 2:46 AM, Christian König
christian.koe...@amd.com wrote:
Hi guys,
the following commit breaks booting my E350 based test system in EFI mode:
commit 8d57470d8f859635deffe3919d7d4867b488b85a
Author: Yinghai Lu ying...@kernel.org
On Wed, May 15, 2013 at 8:20 AM, Christian König
christian.koe...@amd.com wrote:
Am 15.05.2013 16:46, schrieb Yinghai Lu:
On Wed, May 15, 2013 at 2:46 AM, Christian König
christian.koe...@amd.com wrote:
Hi guys,
the following commit breaks booting my E350 based test system in EFI
mode:
26 matches
Mail list logo