From: "Christian König" <christian.koenig@amd.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Wolfram Gloger <wg@malloc.de>
Subject: Re: 3.9 breaks EFI boot on E350
Date: Sun, 19 May 2013 15:45:16 +0200 [thread overview]
Message-ID: <5198D76C.7020500@amd.com> (raw)
In-Reply-To: <CAE9FiQVofGoSk7q5-0irjkBxemqK729cND4hov-1QCBJDhxpgQ@mail.gmail.com>
Am 17.05.2013 19:54, schrieb Yinghai Lu:
> On Fri, May 17, 2013 at 2:43 AM, Christian König
> <christian.koenig@amd.com> wrote:
>> Am 16.05.2013 17:42, schrieb Yinghai Lu:
>>
>>> On Thu, May 16, 2013 at 8:23 AM, Christian König
>>> <christian.koenig@amd.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@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 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.
> Please check attached patch, it should fix the problem.
Works perfectly, thanks allot.
Christian.
> Thanks
>
> Yinghai
prev parent reply other threads:[~2013-05-19 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 9:46 3.9 breaks EFI boot on E350 Christian König
2013-05-15 14:46 ` Yinghai Lu
2013-05-15 15:20 ` Christian König
2013-05-15 20:57 ` Yinghai Lu
2013-05-16 9:41 ` Christian König
2013-05-16 12:49 ` Christian König
2013-05-16 15:17 ` Yinghai Lu
2013-05-16 15:23 ` Christian König
2013-05-16 15:42 ` Yinghai Lu
2013-05-17 9:43 ` Christian König
2013-05-17 17:54 ` Yinghai Lu
2013-05-17 19:12 ` [tip:x86/urgent] x86, range: fix missing merge during add range tip-bot for Yinghai Lu
2013-05-19 13:44 ` Christian König
2013-05-19 13:45 ` Christian König [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5198D76C.7020500@amd.com \
--to=christian.koenig@amd.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wg@malloc.de \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox