From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Joe Marzot <gmarzot@nortelnetworks.com>
Subject: Re: handle_trap - failed to wait at end of syscall [was Re: [uml-devel] debugging UML cores]
Date: Fri, 20 Aug 2004 13:46:53 +0200 [thread overview]
Message-ID: <200408201346.53688.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200408132147.i7DLlB2o003883@ccure.user-mode-linux.org>
Alle 23:47, venerdì 13 agosto 2004, Jeff Dike ha scritto:
> gmarzot@nortelnetworks.com said:
> > WSTOPSIG(err) = SIGHUP
> > does this give any clues...any ideas of what else to look at?
>
> Do you have any idea how you're making this happen? The userspace process
> is getting a SIGHUP in the middle of having a system call nullified. This
> is OK since a SIGHUP can happen any time if you log out on it or something,
> but I'd like to know exactly what's going on so I can decide what the right
> reaction to it is.
I'm getting a similar problem, in another situation. With my current tree (but
also any 2.6.7-bb should do; but you can test it on -bb4, to be sure), on a
2.6.7 host with host-skas3-2.6.7-v2.patch (notice -v2, it contains SYSEMU)
(never got this on 2.4 host, but I'll retest), if I do "echo 0
> /proc/sysemu" I get the same failure, but with 2943 as status (i.e.
WSTOPSIG=SIGSEGV) and EINTR as errno (but I think that's from a previous
loop, since I've applied the catch-EINTR patch; i.e. probably it did the
syscall, it was interrupted, and did the syscall again which returned SIGSEGV
as stop status). And this is definitely reproducible with echo 0
> /proc/sysemu. But when booting with nosysemu, it works, and I can even
reenable it with echo 1 > /proc/sysemu; but if I try disabling it again, I
get the same problem.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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-08-20 11:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 15:32 [uml-devel] debugging UML cores Joe Marzot
2004-08-12 5:41 ` Jeff Dike
2004-08-12 15:21 ` Joe Marzot
2004-08-12 16:56 ` Jeff Dike
2004-08-12 16:16 ` Joe Marzot
2004-08-12 15:36 ` Joe Marzot
2004-08-12 15:47 ` Joe Marzot
2004-08-13 15:46 ` [uml-devel] handle_trap - failed to wait at end of syscall [was Re: [uml-devel] debugging UML cores] Joe Marzot
2004-08-13 18:01 ` Joe Marzot
2004-08-13 21:47 ` Jeff Dike
2004-08-16 17:47 ` [uml-devel] Re: handle_trap - failed to wait at end of syscall [was Re: [uml- devel] " Joe Marzot
2004-08-16 19:25 ` Joe Marzot
2004-08-16 19:53 ` D. Bahi
2004-08-17 5:26 ` Jeff Dike
2004-08-20 11:46 ` BlaisorBlade [this message]
2004-09-13 15:39 ` [uml-devel] handle_trap - failed to wait at end of syscall Joe Marzot
2004-09-13 19:39 ` BlaisorBlade
2004-09-13 22:14 ` Jeff Dike
2004-09-14 10:41 ` BlaisorBlade
2004-09-14 16:09 ` Joe Marzot
2004-09-14 21:23 ` Jeff Dike
2004-09-15 5:00 ` Richard Potter
2004-09-15 19:35 ` Joe Marzot
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=200408201346.53688.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=gmarzot@nortelnetworks.com \
--cc=jdike@addtoit.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