mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: Matt Fleming <matt@console-pimps.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	"Yinghai Lu" <yinghai@kernel.org>,
	"Matt Fleming" <matt.fleming@intel.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Mantas Mikulėnas" <grawity@gmail.com>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v4] x86: only load initrd above 4g on second try
Date: Sat, 6 Sep 2014 21:05:35 +0200	[thread overview]
Message-ID: <20140906190534.GA4767@ad.chargestorm.se> (raw)
In-Reply-To: <20140905221616.GP3001@console-pimps.org>

* Matt Fleming <matt@console-pimps.org> [140906 00:16]:

> On Thu, 04 Sep, at 01:59:05PM, H. Peter Anvin wrote:

> > I am fine with this patch, but at the same time I do want to note that
> > there is an alternative to double-buffer the patch and/or (if that
> > applies to the buggy BIOS) round up the size of the target buffer.

> I took a whack at the double-buffer strategy, and I think the patch is
> conceptually pretty straight forward.

> Could someone try out the following patch? It works around the problem
> on my ASUS machine.

Your patch works around the problem on my Dell machine also. With that
one applied, it boots fine!

Thus, 

Tested-by: Anders Darander <anders@chargestorm.se>

Cheers,
Anders

-- 
All the troubles you have will pass away very quickly.

  reply	other threads:[~2014-09-06 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  4:50 Yinghai Lu
2014-09-04 10:01 ` Matt Fleming
2014-09-04 20:59   ` H. Peter Anvin
2014-09-04 21:29     ` Matt Fleming
2014-09-05  1:19       ` Yinghai Lu
2014-09-05  5:47         ` Anders Darander
2014-09-05  6:38           ` Laszlo Ersek
2014-09-05 17:03             ` Yinghai Lu
2014-09-05 19:20               ` Laszlo Ersek
2014-09-05 22:16     ` Matt Fleming
2014-09-06 19:05       ` Anders Darander [this message]
2014-09-06 20:09       ` Mantas Mikulėnas
2014-09-06 20:10         ` Mantas Mikulėnas
2014-09-08 15:58         ` Matt Fleming

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=20140906190534.GA4767@ad.chargestorm.se \
    --to=anders@chargestorm.se \
    --cc=grawity@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=matt@console-pimps.org \
    --cc=mingo@redhat.com \
    --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

all inboxes | Powered by JetHome®