From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: "Tsillas, Demetrios J" <jtsillas@enterasys.com>
Subject: Re: [uml-devel] 2.6.8.1: Kernel panic: handle_trap - failed to wait at end of syscall, errno = 4, status = 4479
Date: Tue, 5 Oct 2004 21:44:09 +0200 [thread overview]
Message-ID: <200410052144.09628.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <EAC7622167479948B614F8B9AD41C505ECA5CD@MAANDMBX2.ets.enterasys.com>
On Tuesday 05 October 2004 21:22, Tsillas, Demetrios J wrote:
> I'm trying with root_fs.fc-2-client.pristine.20040504. I've got
> the incrementals in there:
Tried without any of them? Does it make any difference? Also, against which
tree are you applying patches, 2.6.8.1-1 or 2.6.9-rc2-mm4? And does using
different filesystems change anything?
> VFS: Mounted root (ext2 filesystem) readonly.
> Mounted devfs on /dev
> INIT: version 2.85 booting
> Kernel panic: handle_trap - failed to wait at end of syscall, errno = 4,
> status = 4479
This is quite strange. The child has been stopped by SIGCHLD, which is
completely unexpected (except if any syscall is executing on the host). Have
you made sure you have moved, inside the fs, /lib/tls to /lib/notls?
About the 4479 value:
./testprogs/waitstatus 4479
WSTOPSIG(status) is 17
Signal 17 is SIGCHLD
waitstatus.c:
#include <sys/types.h>
#include <sys/wait.h>
#include <signal.h>
#include <stdio.h>
#include <stdlib.h>
int main(int argc, char * argv[])
{
int status = 2943;
if (argc >= 2)
status = atol(argv[1]);
if (WIFSIGNALED(status))
printf("error, process signaled\n");
if (WIFEXITED(status))
printf("error, process exited\n");
if (!WIFSTOPPED(status))
printf("error, process not stopped\n");
if (WSTOPSIG(status) != SIGTRAP)
printf("WSTOPSIG(status) is %d\n", WSTOPSIG(status));
return 0;
}
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-05 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 19:22 [uml-devel] 2.6.8.1: Kernel panic: handle_trap - failed to wait at end of syscall, errno = 4, status = 4479 Tsillas, Demetrios J
2004-10-05 19:44 ` BlaisorBlade [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-05 20:33 Stroesser, Bodo
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=200410052144.09628.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=jtsillas@enterasys.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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