From: "Bradley D. LaRonde" <brad@ltc.com>
To: <sseeger@stellartec.com>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: sys_execve problem
Date: Fri, 5 Jul 2002 19:39:24 -0400 [thread overview]
Message-ID: <006401c2247d$3356e580$4c00a8c0@prefect> (raw)
In-Reply-To: 01c501c2243f$2951c700$3501a8c0@wssseeger
Is your init static? Does it need ld.so? Is ld.so executable (that's a
tricky one).
Regards,
Brad
----- Original Message -----
From: "Steven Seeger" <sseeger@stellartec.com>
To: <linux-mips@oss.sgi.com>
Sent: Friday, July 05, 2002 12:15 PM
Subject: sys_execve problem
> Hey guys. I have compiled 2.4.19-ac1 from the CVS with the linux_2_4 tag
for
> my NEC Osprey board (NEC VR4181) It boots fine and stuff, but doesn't load
> init. I've confirmed with simple print statements that do_execve is
> returning a 0 at the point in fs/exec.c where it says "/* execve success
*/"
> and yet init doesn't load. The system just sits there. I see on a scope
that
> my timer interrupt is firing every 10 ms and the serial console responds
> properly. It echos characters and stops the echo when it receives a ctrl-S
> and resumes it on ctrl-Q. Obviously this is the last little part of the
> kernel to work though here. Any ideas?
>
> Steve
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: sseeger@stellartec.com
Cc: linux-mips@oss.sgi.com
Subject: Re: sys_execve problem
Date: Fri, 5 Jul 2002 19:39:24 -0400 [thread overview]
Message-ID: <006401c2247d$3356e580$4c00a8c0@prefect> (raw)
Message-ID: <20020705233924.aFdJD7nuI-YnMsFB9aWyHXm1mAfmaffpV23Jm7No_-Y@z> (raw)
In-Reply-To: 01c501c2243f$2951c700$3501a8c0@wssseeger
Is your init static? Does it need ld.so? Is ld.so executable (that's a
tricky one).
Regards,
Brad
----- Original Message -----
From: "Steven Seeger" <sseeger@stellartec.com>
To: <linux-mips@oss.sgi.com>
Sent: Friday, July 05, 2002 12:15 PM
Subject: sys_execve problem
> Hey guys. I have compiled 2.4.19-ac1 from the CVS with the linux_2_4 tag
for
> my NEC Osprey board (NEC VR4181) It boots fine and stuff, but doesn't load
> init. I've confirmed with simple print statements that do_execve is
> returning a 0 at the point in fs/exec.c where it says "/* execve success
*/"
> and yet init doesn't load. The system just sits there. I see on a scope
that
> my timer interrupt is firing every 10 ms and the serial console responds
> properly. It echos characters and stops the echo when it receives a ctrl-S
> and resumes it on ctrl-Q. Obviously this is the last little part of the
> kernel to work though here. Any ideas?
>
> Steve
next prev parent reply other threads:[~2002-07-05 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 16:15 sys_execve problem Steven Seeger
2002-07-05 16:15 ` Steven Seeger
2002-07-05 23:39 ` Bradley D. LaRonde [this message]
2002-07-05 23:39 ` Bradley D. LaRonde
2002-07-05 23:57 ` Steven Seeger
2002-07-05 23:57 ` Steven Seeger
2002-07-06 2:32 ` Bradley D. LaRonde
2002-07-06 2:32 ` Bradley D. LaRonde
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='006401c2247d$3356e580$4c00a8c0@prefect' \
--to=brad@ltc.com \
--cc=linux-mips@oss.sgi.com \
--cc=sseeger@stellartec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox