public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alexey Fisher <bug-track@fisher-privat.net>,
	ykzhao <yakui.zhao@intel.com>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu
Subject: Re: [PATCH] Solve the issue with memory corruption on Intel BIOS.
Date: Wed, 15 Jul 2009 02:10:58 +0200	[thread overview]
Message-ID: <20090715001058.GC1552@ucw.cz> (raw)
In-Reply-To: <20090715103431.4381b423@lxorguk.ukuu.org.uk>

On Wed 2009-07-15 10:34:31, Alan Cox wrote:
> On Wed, 15 Jul 2009 07:55:14 +0200
> Alexey Fisher <bug-track@fisher-privat.net> wrote:
> 
> > In Bug 13710 was reported "corrupted low memory after resume on Intel
> > DG45ID board". It use AMI BIOS with Intel vendor string. We need to add this
> > vendor to CONFIG_X86_RESERVE_LOW_64K workaround.
> 
> Given that this is the first report of a problem with an Intel BIOS, and
> there are millions of systems not affected your match is far too wide I
> think. Match the board identifier as well at least rather than randomly
> making everyone suffer.

Given the intel pushing linux these days... could we get them to
debug&fix their bios?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-07-15 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  5:55 [PATCH] Solve the issue with memory corruption on Intel BIOS Alexey Fisher
2009-07-15  9:34 ` Alan Cox
2009-07-15  0:10   ` Pavel Machek [this message]
2009-07-15 15:57   ` Alexey Fisher

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=20090715001058.GC1552@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bug-track@fisher-privat.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yakui.zhao@intel.com \
    /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