All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Yinghai Lu <yinghai@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.9-rc1
Date: Wed, 06 Mar 2013 11:34:39 -0800	[thread overview]
Message-ID: <51379A4F.4020200@linux.intel.com> (raw)
In-Reply-To: <20130306193612.GA513@polaris.bitmath.org>

On 03/06/2013 11:36 AM, Henrik Rydberg wrote:
> Hi Yinghai,
> 
>>>> Can you get a boot log with "debug memblock=debug" from the last
>>>> successful commit point?  Are you booting EFI or BootCamp?
>>>
>>> Attached the dmesg log, booting from f763ad1 which is on top of
>>> 3.7-rc6. I am booting with EFI_STUB, straight into the kernel.
>>> The command line and modules are built in.
>>
>> will check that EFI_STUB path.
>>
>> Can you check bootloader like grub.efi ?
> 
> I checked, same story. I tried without EFI_STUB, no joy. I ran with
> and without nouveau, just in case. Without the patch, everything
> works. With the patch, nothing works, and no output at all.
> 
> With a bit of luck, I could maybe get the first lines of output using
> grub.efi, but frankly I cannot remember if that ever worked on this
> machine.
> 

A simpler one is efilinux:

https://github.com/mfleming/efilinux

	-hpa



  reply	other threads:[~2013-03-06 19:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  0:28 Linux 3.9-rc1 Linus Torvalds
2013-03-04  1:17 ` Jiri Kosina
2013-03-04  1:42   ` Linus Torvalds
2013-03-04  2:32     ` Randy Dunlap
2013-03-04  2:55       ` Linus Torvalds
2013-03-04  3:39     ` Linus Torvalds
2013-03-04  4:22 ` linux-next stats (Was: Linux 3.9-rc1) Stephen Rothwell
2013-03-04  5:02   ` Stephen Rothwell
2013-03-04  9:54 ` Regression from 3.8.0 - USB mouse (was: " Harald Arnesen
2013-03-06  8:06 ` Linux 3.9-rc1 Henrik Rydberg
2013-03-06  9:17   ` H. Peter Anvin
2013-03-06 10:07     ` Henrik Rydberg
2013-03-06 17:51       ` Yinghai Lu
2013-03-06 19:36         ` Henrik Rydberg
2013-03-06 19:34           ` H. Peter Anvin [this message]
2013-03-06 19:54             ` Henrik Rydberg
2013-03-06 20:00               ` Yinghai Lu
2013-03-06 20:45                 ` Henrik Rydberg
2013-03-06 20:58                   ` H. Peter Anvin
2013-03-06 21:33                     ` Yinghai Lu
2013-03-06 21:49                       ` H. Peter Anvin
2013-03-06 22:04                         ` Henrik Rydberg
2013-03-06 22:27                           ` H. Peter Anvin
2013-03-06 22:44                             ` Yinghai Lu
2013-03-06 22:48                               ` H. Peter Anvin
2013-03-06 22:54                                 ` Yinghai Lu
2013-03-07  4:28                               ` [tip:x86/urgent] x86, mm: Make sure to find a 2M free block for the first mapped area tip-bot for Yinghai Lu
2013-03-06 22:14                         ` Linux 3.9-rc1 Yinghai Lu
2013-03-06 22:19                           ` Yinghai Lu
2013-03-06 22:28                           ` H. Peter Anvin
2013-03-06 22:46                             ` Yinghai Lu
2013-03-06 22:47                               ` H. Peter Anvin
2013-03-06 16:08   ` Linus Torvalds
2013-03-06 16:57     ` H. Peter Anvin
2013-03-06 21:07     ` Henrik Rydberg

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=51379A4F.4020200@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rydberg@euromail.se \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.