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: <CAE9FiQWNDn8uHUAe+CSvYdJXeJi57G+9RBxs688+VaFRS-GXBA@mail.gmail.com>
Date:	Thu, 16 May 2013 08:42:04 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Christian König <christian.koenig@....com>
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

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"?

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/