public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on Itanium
Date: Thu, 30 Mar 2006 15:49:07 +0000	[thread overview]
Message-ID: <20060330154906.GA21663@sgi.com> (raw)
In-Reply-To: <442AB6DD.4020800@sgi.com>

On Thu, Mar 30, 2006 at 08:43:43AM -0700, David Mosberger-Tang wrote:
> On 3/30/06, Jack Steiner <steiner@sgi.com> wrote:
> 
> > Is this problem unique to SN systems
> 
> No, the same will happen on all other systems (that I know of).
> 
> > The BIOS reports that most
> > memory ranges support both CACHED & UNCACHED references. I _think_
> > this is correct.
> 
> That's correct.  The map shows the ways the page *can* be mapped, not
> the way it *should* be mapped.
> 
> It's strange that ACPI would prefer to use WC when WB mapping is
> possible.  They definitely need to pick one way and stick with it
> though.  As you say, mapping the same page with different cacheability
> is a no-no (and at least in theory, it should cause an MCA even on
> real hardware).

It does, at least on our chipset. If the chipset detects a simultaneous
UC & C reference, it generates a BUS error. It is surprising how
quickly this MCA occurs when we break the rules.



> 
>   --david
> 
> --
> Mosberger Consulting LLC, http://www.mosberger-consulting.com/

-- 
Jack



  parent reply	other threads:[~2006-03-30 15:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 16:33 [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on Itanium Prarit Bhargava
2006-03-29 16:34 ` Prarit Bhargava
2006-03-29 16:55 ` Chen, Kenneth W
2006-03-29 18:55 ` Prarit Bhargava
2006-03-29 19:01 ` Greg Edwards
2006-03-29 19:55 ` Chen, Kenneth W
2006-03-29 20:13 ` Luck, Tony
2006-03-29 20:51 ` Grant Grundler
2006-03-29 20:57 ` [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on James Bottomley
2006-03-29 20:58 ` [Fedora-ia64-list] kernel 2.6.16-1.2097_FC6 unbootable on Itanium Luck, Tony
2006-03-29 21:36 ` Émeric Maschino
2006-03-29 22:04 ` Jack Steiner
2006-03-30  8:57 ` Jes Sorensen
2006-03-30  9:04 ` Jes Sorensen
2006-03-30  9:08 ` Jes Sorensen
2006-03-30  9:14 ` Keith Owens
2006-03-30 10:11 ` Jes Sorensen
2006-03-30 12:29 ` Jes Sorensen
2006-03-30 13:24 ` Jes Sorensen
2006-03-30 15:16 ` Jack Steiner
2006-03-30 15:42 ` Prarit Bhargava
2006-03-30 15:43 ` David Mosberger-Tang
2006-03-30 15:49 ` Jack Steiner [this message]
2006-03-30 15:53 ` David Mosberger-Tang
2006-03-30 16:34 ` H. J. Lu
2006-03-30 16:38 ` Prarit Bhargava
2006-03-30 16:45 ` H. J. Lu
2006-03-30 16:52 ` Prarit Bhargava
2006-03-30 16:53 ` Bjorn Helgaas
2006-03-30 17:10 ` Jack Steiner
2006-03-30 18:23 ` Luck, Tony
2006-03-30 18:23 ` Prarit Bhargava
2006-03-30 18:54 ` Grant Grundler

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=20060330154906.GA21663@sgi.com \
    --to=steiner@sgi.com \
    --cc=linux-ia64@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