public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: hpa@zytor.com
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386 very early memory detection cleanup patch breaks the build
Date: 13 Mar 2004 14:48:02 -0500	[thread overview]
Message-ID: <1079207284.1759.28.camel@mulgrave> (raw)
In-Reply-To: <1079198139.2512.19.camel@mulgrave>

On Sat, 2004-03-13 at 12:15, James Bottomley wrote:
> P.S.  I'm still compiling, I'll yell again if the patch breaks at
> runtime too.

OK, I confirm a total boot time failure as well.  It looks like the CPUs
are unable to map their CPI memory.

Reversing the patch entirely fixes the problem.

I'll dig around and see if I can uncover the reason.

James


  reply	other threads:[~2004-03-13 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13 17:15 i386 very early memory detection cleanup patch breaks the build James Bottomley
2004-03-13 19:48 ` James Bottomley [this message]
2004-03-13 21:43 ` H. Peter Anvin
2004-03-13 22:10   ` James Bottomley
2004-03-13 22:29     ` H. Peter Anvin
2004-03-13 22:38       ` James Bottomley
2004-03-14  2:05       ` James Bottomley
2004-03-14  2:16         ` H. Peter Anvin

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=1079207284.1759.28.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox