Re: handle_trap - failed to wait at end of syscall [was Re: [uml-devel] debugging UML cores]

[BlaisorBlade <bla...@ya...>]

Alle 23:47, venerd=EC 13 agosto 2004, Jeff Dike ha scritto:
> gm...@no... said:
> > WSTOPSIG(err) =3D 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 somethin=
g,
> but I'd like to know exactly what's going on so I can decide what the rig=
ht
> reaction to it is.
I'm getting a similar problem, in another situation. With my current tree (=
but=20
also any 2.6.7-bb should do; but you can test it on -bb4, to be sure), on a=
=20
2.6.7 host with host-skas3-2.6.7-v2.patch (notice -v2, it contains SYSEMU)=
=20
(never got this on 2.4 host, but I'll retest), if I do "echo 0=20
> /proc/sysemu" I get the same failure, but with 2943 as status (i.e.=20
WSTOPSIG=3DSIGSEGV) and EINTR as errno (but I think that's from a previous=
=20
loop, since I've applied the catch-EINTR patch; i.e. probably it did the=20
syscall, it was interrupted, and did the syscall again which returned SIGSE=
GV=20
as stop status). And this is definitely reproducible with echo 0=20
> /proc/sysemu. But when booting with nosysemu, it works, and I can even=20
reenable it with echo 1 > /proc/sysemu; but if I try disabling it again, I=
=20
get the same problem.
=2D-=20
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729