All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Reiser <jreiser@BitWagon.com>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, mike@navi.cx, pageexec@freemail.hu,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org, "Raj,
	Ashok" <ashok.raj@intel.com>
Subject: Re: arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build
Date: Mon, 03 May 2004 14:08:44 +0000	[thread overview]
Message-ID: <4096526C.4060503@BitWagon.com> (raw)
In-Reply-To: <20040501013304.32a750d3.pj@sgi.com>

Paul Jackson wrote:
> Not only don't the bssprot patches in Andrew's 2.6.6-rc2-mm2 not build,
> they don't boot on SGI's SN2 ia64 with sn2_defconfig.  If I remove these
> 4 bssprot patches, then 2.6.6-rc2-mm2 builds (with the easy build fixes
> already understood earlier this week) and boots on SN2 ia64 with
> sn2_defconfig.
[snip]
> But trying to boot the resulting kernel on an SGI SN2 system fails.  The
> boot successfully prints out:
> 
>   Freeing unused kernel memory: 336kB freed
> 
> but freezes prior to displaying the next line expected:
> 
>   INIT: version 2.85 booting
> 
> I have to reset instead at this point.
> 
> On this system the program /sbin/init is the following type:
> 
>   /sbin/init: ELF 64-bit LSB executable, IA-64, version 1 (SYSV),
>   for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped

This indicates a problem with the very first execve() and/or its shared
libraries.  It is likely that printk() of the arguments and results
to elf_map() and load_elf_interp(), both in fs/binfmt_elf.c,
will aid in finding the problem.  This I would do, if I had hardware.

Are there any reports, either success or failure, for any other 64-bit
architecture?

-- 


WARNING: multiple messages have this Message-ID (diff)
From: John Reiser <jreiser@BitWagon.com>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, mike@navi.cx, pageexec@freemail.hu,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org, "Raj,
	Ashok" <ashok.raj@intel.com>
Subject: Re: arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot
Date: Mon, 03 May 2004 07:08:44 -0700	[thread overview]
Message-ID: <4096526C.4060503@BitWagon.com> (raw)
In-Reply-To: <20040501013304.32a750d3.pj@sgi.com>

Paul Jackson wrote:
> Not only don't the bssprot patches in Andrew's 2.6.6-rc2-mm2 not build,
> they don't boot on SGI's SN2 ia64 with sn2_defconfig.  If I remove these
> 4 bssprot patches, then 2.6.6-rc2-mm2 builds (with the easy build fixes
> already understood earlier this week) and boots on SN2 ia64 with
> sn2_defconfig.
[snip]
> But trying to boot the resulting kernel on an SGI SN2 system fails.  The
> boot successfully prints out:
> 
>   Freeing unused kernel memory: 336kB freed
> 
> but freezes prior to displaying the next line expected:
> 
>   INIT: version 2.85 booting
> 
> I have to reset instead at this point.
> 
> On this system the program /sbin/init is the following type:
> 
>   /sbin/init: ELF 64-bit LSB executable, IA-64, version 1 (SYSV),
>   for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped

This indicates a problem with the very first execve() and/or its shared
libraries.  It is likely that printk() of the arguments and results
to elf_map() and load_elf_interp(), both in fs/binfmt_elf.c,
will aid in finding the problem.  This I would do, if I had hardware.

Are there any reports, either success or failure, for any other 64-bit
architecture?

-- 


  reply	other threads:[~2004-05-03 14:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27  1:56 arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Paul Jackson
2004-04-27  5:17 ` John Reiser
2004-04-27  5:27   ` Paul Jackson
2004-05-01  8:33 ` Paul Jackson
2004-05-01  8:33   ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Paul Jackson
2004-05-03 14:08   ` John Reiser [this message]
2004-05-03 14:08     ` John Reiser
2004-05-03 17:57     ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Andrew Morton
2004-05-03 17:57       ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Andrew Morton
2004-05-03 21:04     ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Paul Jackson
2004-05-03 21:04       ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Paul Jackson
2004-05-03 21:29       ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Mike Hearn
2004-05-03 21:29         ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Mike Hearn
2004-05-03 22:10         ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Paul Jackson
2004-05-03 22:10           ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Paul Jackson
2004-05-03 22:20           ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Mike Hearn
2004-05-03 22:20             ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Mike Hearn
2004-05-03 22:26             ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build Paul Jackson
2004-05-03 22:26               ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Paul Jackson

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=4096526C.4060503@BitWagon.com \
    --to=jreiser@bitwagon.com \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@navi.cx \
    --cc=pageexec@freemail.hu \
    --cc=pj@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.