public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@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 10:11:07 +0000	[thread overview]
Message-ID: <yq0hd5guts4.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <442AB6DD.4020800@sgi.com>

>>>>> "Keith" = Keith Owens <kaos@sgi.com> writes:

Keith> Jes Sorensen (on 30 Mar 2006 03:57:04 -0500) wrote:
>> Please note that if I compile the kernel on a box with an old
>> installation and old toolchain the kernel boots, same source tree
>> built on a system with a new installation and it doesn't boot.

Keith> This sounds like a random data overwrite which depends on the
Keith> exact kernel layout.  Somebody else in SGI (Prarit ?) said that
Keith> they compiled your failing tree on the same platform and their
Keith> kernel worked.  Since the build userid and the pathname to the
Keith> kernel source tree are embedded in the binary, changing either
Keith> of those will disturb the kernel layout, possibly making the
Keith> problem move.

Keith> Jes, try renaming your source tree to something with a
Keith> different pathname length and rebuild the kernel.  Does the
Keith> problem change or go away?

Moved it to /tmp/a and built there - no go.

Cheers,
Jes

  parent reply	other threads:[~2006-03-30 10:11 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 [this message]
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=yq0hd5guts4.fsf@jaguar.mkp.net \
    --to=jes@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