linux-kernel - Re: 3.9 breaks EFI boot on E350

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5195FBBD.6060808@amd.com>
Date:	Fri, 17 May 2013 11:43:25 +0200
From:	Christian König <christian.koenig@....com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Wolfram Gloger <wg@...loc.de>
Subject: Re: 3.9 breaks EFI boot on E350

Am 16.05.2013 17:42, schrieb Yinghai Lu:
> On Thu, May 16, 2013 at 8:23 AM, Christian König
> <christian.koenig@....com> wrote:
>> Am 16.05.2013 17:17, schrieb Yinghai Lu:
>>
>>> On Thu, May 16, 2013 at 5:49 AM, Christian König
>>> <christian.koenig@....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 8d57470d8f859635deffe3919d7d4867b488b85a it indeed crashes
>>>> very
>>>> early in the boot sequence, but commit
>>>> 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 a request for help.
> can you boot with appending with "memtest"?

Sure, bootlog with memtest is attached.

Christian.

>
> Thanks
>
> Yinghai
>


View attachment "bootlog_with_memtest.txt" of type "text/plain" (52048 bytes)