linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russ Anderson <rja@sgi.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Alex Thorlton <athorlton@sgi.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: [BUG] Linux 3.14 fails to boot with new EFI changes
Date: Fri, 31 Jan 2014 07:53:55 -0600	[thread overview]
Message-ID: <20140131135355.GB22498@sgi.com> (raw)
In-Reply-To: <20140131080428.GA29136@console-pimps.org>

On Fri, Jan 31, 2014 at 08:04:28AM +0000, Matt Fleming wrote:
> On Thu, 30 Jan, at 04:19:50PM, Alex Thorlton wrote:
> > Re-adding lkml.
>  
> Also add linux-efi.
> 
> > The quick answer is I think it is a virtual address, because
> > it does not work in physical mode.  If you ever see "virtefi"
> > on the RHEL bootline it is because RH switched the default
> > to physical mode, which caused UV to not boot.  "virtefi"
> > forced it back to virtual mode.
> 
> Do you have details of the failure, links to bug reports? Is it a
> limitation of the firmware?

That was a non-upstream regression in the distro kernel.  The
3.13 community kernel was boots fine.  The current problem is a
regression introduced in this merge window which needs to be fixed.


-- 
Russ Anderson,  Kernel and Performance Software Team Manager
SGI - Silicon Graphics Inc          rja@sgi.com

  reply	other threads:[~2014-01-31 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52E2ADB1.2030007@zytor.com>
     [not found] ` <20140124183730.GC11788@pd.tnic>
     [not found]   ` <20140124184842.GD11788@pd.tnic>
     [not found]     ` <20140124191709.GT18196@sgi.com>
     [not found]       ` <20140127222129.GK6839@pd.tnic>
     [not found]         ` <20140128110552.GA815@pd.tnic>
     [not found]           ` <20140128200754.GZ18196@sgi.com>
     [not found]             ` <20140128225905.GN815@pd.tnic>
     [not found]               ` <20140128234036.GB18196@sgi.com>
     [not found]                 ` <20140129141822.GC24887@pd.tnic>
2014-01-30 22:19                   ` [BUG] Linux 3.14 fails to boot with new EFI changes Alex Thorlton
2014-01-30 22:23                     ` H. Peter Anvin
2014-01-31 10:07                       ` Borislav Petkov
2014-01-31 14:02                         ` Russ Anderson
2014-01-31 14:23                           ` Borislav Petkov
2014-01-31 14:36                             ` Borislav Petkov
2014-02-05 21:45                             ` Alex Thorlton
2014-02-05 23:15                               ` Borislav Petkov
2014-02-11 22:19                                 ` Alex Thorlton
2014-02-11 22:36                                   ` Borislav Petkov
2014-01-31  8:04                     ` Matt Fleming
2014-01-31 13:53                       ` Russ Anderson [this message]
2014-01-23 22:11 Alex Thorlton
2014-01-23 22:48 ` Borislav Petkov

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=20140131135355.GB22498@sgi.com \
    --to=rja@sgi.com \
    --cc=athorlton@sgi.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.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;
as well as URLs for NNTP newsgroup(s).