All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: indexer <indexer@internode.on.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression in efi.c 2.6.32-rc7
Date: Tue, 17 Nov 2009 23:49:26 -0800	[thread overview]
Message-ID: <4B03A706.6040400@zytor.com> (raw)
In-Reply-To: <4B02B654.9080304@internode.on.net>

On 11/17/2009 06:42 AM, indexer wrote:
> I would like to report a possible regression in efi.c with kernels
> 2.6.31 , 2.6.32-rc5 and 2.6.32.rc7.
> 
> Attempting to boot x86_64 with elilo succeeds using 2.6.30 . Using the
> same config cannot boot with any of the 3 afore mentioned kernels. Elilo
> freezes at bootloader as system attempts to initiate. Cannot attach a
> serial console for debug, and no errors appear on screen. No version of
> refit, elilo, efi firmware changes, only the kernel in question. This
> results in an unbootable system using efi.
> 
> I have already followed the patch described here,
> http://bugzilla.kernel.org/show_bug.cgi?id=14466 , it does not change
> the situation on 2.6.31 or 2.6.32-rc5, and no need to patch 2.6.32-rc7
> as it was merged already.
> 
> The below diff shows the differences in efi.c between 2.6.30 and
> 2.6.32-rc7. Please also find attached my .config for 2.6.32.rc7
> 

Can you do a git bisect between 2.6.30 and 2.6.31?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2009-11-18  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 14:42 Regression in efi.c 2.6.32-rc7 indexer
2009-11-18  7:49 ` H. Peter Anvin [this message]
2009-11-19  0:40   ` indexer
  -- strict thread matches above, loose matches on Subject: below --
2009-11-20  9:07 indexer
2009-11-20 17:15 ` H. Peter Anvin
2009-11-20 17:19   ` indexer
2009-11-21 19:21   ` indexer

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=4B03A706.6040400@zytor.com \
    --to=hpa@zytor.com \
    --cc=indexer@internode.on.net \
    --cc=linux-kernel@vger.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.