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: Wed, 29 Mar 2006 22:04:16 +0000	[thread overview]
Message-ID: <20060329220415.GB18889@sgi.com> (raw)
In-Reply-To: <442AB6DD.4020800@sgi.com>

On Wed, Mar 29, 2006 at 12:58:40PM -0800, Luck, Tony wrote:
> > Tiger still boots with my release tree (just has seven patches that
> > haven't been sent to Linus yet, including Russ' fix for my merge
> > goof that created item "3" above).  I haven't pulled in from Linus
> >in about three days, so I'm about 458 commits behind the bleeding
> > edge.  So a "git bisect" between Linus head and the point where I last
> > merged (commit 64bc0430) might yield the problem (for Ken's tiger
> > boot issue).
> 
> Just started the bisection ... and the current tip of Linus' git
> tree (f3cab8a0) booted just fine on tiger!  There are 85 commits
> in there since git-17 was cut, but a quick glance at gitk doesn't
> show any obvious fixes or reverts that might affect ia64.
> 

I don't know if this helps or not.

I ran Jes's kernel on the simulator. Unfortunately, he sent me a stripped
kernel so I have no symbol table.

The kernel blows up right after printing:

	...
	Virtual mem_map starts at 0xa0007fffd5f2c000
	Built 1 zonelists
	Kernel command line: root=/dev/hda2 init=/bin/bash console=ttyS0
	PID hash table entries: 1024 (order: 10, 32768 bytes)
	Console: colour dummy device 80x25

The failure is an MCA caused by a cache hit on a memory reference to an
uncached address. The simulator detects this error & stops.

The code that took the failure was memcopy (or equiv). I recognized the
code from the prefetchs and ld/st sequence. The data appears to be
an ACPI table that is being copied into kernel memory. The current
reference is using uncached addresses but 15M instructions in the past, the
table was referenced cached.

Does this ring any bells with anyone?  This failure may 
occur only in our simulator environment, so don't spent any
time on this unless it sounds familar.

As soon as I get a symbol table, I'll know a lot more about the
failure.

---
Jack

  parent reply	other threads:[~2006-03-29 22:04 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 [this message]
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
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=20060329220415.GB18889@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