From: Paul Jackson <pj@sgi.com>
To: John Reiser <jreiser@BitWagon.com>
Cc: akpm@osdl.org, mike@navi.cx, pageexec@freemail.hu,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
ashok.raj@intel.com
Subject: Re: arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot
Date: Mon, 3 May 2004 14:04:59 -0700 [thread overview]
Message-ID: <20040503140459.10b9d3eb.pj@sgi.com> (raw)
In-Reply-To: <4096526C.4060503@BitWagon.com>
> 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.
Since I see Andrew dropped the patch for the moment, I'm thinking that
the ball is back in you guys court. If you end up with some patch to a
well-known base (Linus rc or Andrew mm, say) that you'd like me to try
out, let me know. You might want to include the printk's of
args/results that you describe above, right in the patch, so I can
provide more rapid and useful feedback, should whatever be this
execve/sharedlib problem still persist.
Yes - I have the hardware - but I must ration my time on this patch.
Will this work for you?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-05-03 21:07 UTC|newest]
Thread overview: 11+ 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 ` arch/ia64/ia32/binfmt_elf32.c: elf32_map() broken ia64 build _and_ boot Paul Jackson
2004-05-03 14:08 ` John Reiser
2004-05-03 17:57 ` Andrew Morton
2004-05-03 21:04 ` Paul Jackson [this message]
2004-05-03 21:29 ` Mike Hearn
2004-05-03 22:10 ` Paul Jackson
2004-05-03 22:20 ` Mike Hearn
2004-05-03 22:26 ` 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=20040503140459.10b9d3eb.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=jreiser@BitWagon.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@navi.cx \
--cc=pageexec@freemail.hu \
/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