* [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono
@ 2014-05-13 15:56 manut
2014-05-13 16:31 ` Peter Maydell
` (11 more replies)
0 siblings, 12 replies; 13+ messages in thread
From: manut @ 2014-05-13 15:56 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling avoids using mono
Status in QEMU:
New
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
@ 2014-05-13 16:31 ` Peter Maydell
2014-12-20 19:51 ` [Qemu-devel] [Bug 1319100] " Daniel Llewellyn
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Peter Maydell @ 2014-05-13 16:31 UTC (permalink / raw)
To: Bug 1319100; +Cc: QEMU Developers
On 13 May 2014 16:56, manut <1319100@bugs.launchpad.net> wrote:
> running mono in a chroot environment with qemu-user-static is not posible
> because at least one signal used during termination of mono is routed to the
> host.
>
> This can be reproduced by:
> debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
> cp /usr/bin/qemu-arm-static mono-test/usr/bin
> mount -t proc none mono-test/proc
> mount -o bind /dev mono-test/dev
> mount -o bind /sys mono-test/sys
> chroot mono-test
> ../debootstrap/debootstrap --second-stage
> exit
> mount -t proc none mono-test/proc
> mount -o bind /sys mono-test/sys
> chroot mono-test
> QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
>
> This will block on a futex:
>
> --8<--
> 18663 sched_yield(0,0,2582980,0,0,2582928) = 0
> 18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
> 18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
> 18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
> --8<--
>
> If you use mono within strace on a native x86 box you can see, that signals
> between threads are used during termination:
Multithreaded guest process are unreliable under qemu
linux-user mode anyway, even ignoring the signal handling
related races here.
See also:
https://bugs.launchpad.net/qemu/+bug/955379
> There is an openSuSE patch against qemu:
> https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch is a very hacky bandaid papering over the
real problem. It is not suitable for upstream (and
personally I wouldn't ship it in a distro either :-)).
thanks
-- PMM
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling avoids using mono
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
2014-05-13 16:31 ` Peter Maydell
@ 2014-12-20 19:51 ` Daniel Llewellyn
2014-12-20 19:55 ` Daniel Llewellyn
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Daniel Llewellyn @ 2014-12-20 19:51 UTC (permalink / raw)
To: qemu-devel
** Tags added: trusty
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling avoids using mono
Status in QEMU:
New
Status in qemu-kvm package in Ubuntu:
New
Status in qemu-kvm package in Debian:
Unknown
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling avoids using mono
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
2014-05-13 16:31 ` Peter Maydell
2014-12-20 19:51 ` [Qemu-devel] [Bug 1319100] " Daniel Llewellyn
@ 2014-12-20 19:55 ` Daniel Llewellyn
2014-12-21 1:49 ` Bug Watch Updater
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Daniel Llewellyn @ 2014-12-20 19:55 UTC (permalink / raw)
To: qemu-devel
** Project changed: qemu => qemu-kvm (Ubuntu)
** Also affects: qemu
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #748043
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling avoids using mono
Status in QEMU:
New
Status in qemu-kvm package in Ubuntu:
New
Status in qemu-kvm package in Debian:
Unknown
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling avoids using mono
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (2 preceding siblings ...)
2014-12-20 19:55 ` Daniel Llewellyn
@ 2014-12-21 1:49 ` Bug Watch Updater
2015-01-16 21:26 ` Serge Hallyn
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Bug Watch Updater @ 2014-12-21 1:49 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu-kvm (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling avoids using mono
Status in QEMU:
New
Status in qemu-kvm package in Ubuntu:
New
Status in qemu-kvm package in Debian:
Confirmed
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling avoids using mono
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (3 preceding siblings ...)
2014-12-21 1:49 ` Bug Watch Updater
@ 2015-01-16 21:26 ` Serge Hallyn
2015-03-05 15:22 ` [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono to hang Daniel Llewellyn
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Serge Hallyn @ 2015-01-16 21:26 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling avoids using mono
Status in QEMU:
New
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in qemu-kvm package in Debian:
Confirmed
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono to hang
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (4 preceding siblings ...)
2015-01-16 21:26 ` Serge Hallyn
@ 2015-03-05 15:22 ` Daniel Llewellyn
2016-06-17 16:02 ` [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java " Peter Maydell
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Daniel Llewellyn @ 2015-03-05 15:22 UTC (permalink / raw)
To: qemu-devel
also causes problems with java.
** Summary changed:
- qemu-arm-static bug in signal handling avoids using mono
+ qemu-arm-static bug in signal handling causes mono to hang
** Summary changed:
- qemu-arm-static bug in signal handling causes mono to hang
+ qemu-arm-static bug in signal handling causes mono and java to hang
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling causes mono and java to hang
Status in QEMU:
New
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in qemu-kvm package in Debian:
Confirmed
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java to hang
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (5 preceding siblings ...)
2015-03-05 15:22 ` [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono to hang Daniel Llewellyn
@ 2016-06-17 16:02 ` Peter Maydell
2016-10-12 3:27 ` Chris L
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Peter Maydell @ 2016-06-17 16:02 UTC (permalink / raw)
To: qemu-devel
Recent changes to QEMU's handling of signals fix this hang trying to run
mono under QEMU; they should be out in QEMU 2.7.
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling causes mono and java to hang
Status in QEMU:
Fix Committed
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in qemu-kvm package in Debian:
Confirmed
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java to hang
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (6 preceding siblings ...)
2016-06-17 16:02 ` [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java " Peter Maydell
@ 2016-10-12 3:27 ` Chris L
2016-10-12 9:13 ` Peter Maydell
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Chris L @ 2016-10-12 3:27 UTC (permalink / raw)
To: qemu-devel
Did this fix end up making it into QEMU 2.7?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling causes mono and java to hang
Status in QEMU:
Fix Committed
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in qemu-kvm package in Debian:
Confirmed
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java to hang
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (7 preceding siblings ...)
2016-10-12 3:27 ` Chris L
@ 2016-10-12 9:13 ` Peter Maydell
2016-10-14 22:34 ` Bug Watch Updater
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: Peter Maydell @ 2016-10-12 9:13 UTC (permalink / raw)
To: qemu-devel
Yes it did.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling causes mono and java to hang
Status in QEMU:
Fix Released
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in qemu-kvm package in Debian:
Confirmed
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java to hang
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (8 preceding siblings ...)
2016-10-12 9:13 ` Peter Maydell
@ 2016-10-14 22:34 ` Bug Watch Updater
2017-06-06 23:16 ` ChristianEhrhardt
2017-06-06 23:17 ` ChristianEhrhardt
11 siblings, 0 replies; 13+ messages in thread
From: Bug Watch Updater @ 2016-10-14 22:34 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu-kvm (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling causes mono and java to hang
Status in QEMU:
Fix Released
Status in qemu-kvm package in Ubuntu:
Confirmed
Status in qemu-kvm package in Debian:
Fix Released
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java to hang
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (9 preceding siblings ...)
2016-10-14 22:34 ` Bug Watch Updater
@ 2017-06-06 23:16 ` ChristianEhrhardt
2017-06-06 23:17 ` ChristianEhrhardt
11 siblings, 0 replies; 13+ messages in thread
From: ChristianEhrhardt @ 2017-06-06 23:16 UTC (permalink / raw)
To: qemu-devel
Fixed in 2.7 and thereby >=Zesty
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling causes mono and java to hang
Status in QEMU:
Fix Released
Status in qemu-kvm package in Ubuntu:
Fix Released
Status in qemu-kvm package in Debian:
Fix Released
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java to hang
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
` (10 preceding siblings ...)
2017-06-06 23:16 ` ChristianEhrhardt
@ 2017-06-06 23:17 ` ChristianEhrhardt
11 siblings, 0 replies; 13+ messages in thread
From: ChristianEhrhardt @ 2017-06-06 23:17 UTC (permalink / raw)
To: qemu-devel
I can't guess very well how important this would be for an SRU (or not),
leaving that up for user feedback to be decided.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1319100
Title:
qemu-arm-static bug in signal handling causes mono and java to hang
Status in QEMU:
Fix Released
Status in qemu-kvm package in Ubuntu:
Fix Released
Status in qemu-kvm package in Debian:
Fix Released
Bug description:
Note, this bug is already reported to debian, but it seems to also affect the upstream code.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748043
running mono in a chroot environment with qemu-user-static is not posible
because at least one signal used during termination of mono is routed to the
host.
This can be reproduced by:
debootstrap --include=mono-runtime --foreign --arch=armel "wheezy" "mono-test" "http://ftp.de.debian.org//debian"
cp /usr/bin/qemu-arm-static mono-test/usr/bin
mount -t proc none mono-test/proc
mount -o bind /dev mono-test/dev
mount -o bind /sys mono-test/sys
chroot mono-test
../debootstrap/debootstrap --second-stage
exit
mount -t proc none mono-test/proc
mount -o bind /sys mono-test/sys
chroot mono-test
QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
This will block on a futex:
--8<--
18663 sched_yield(0,0,2582980,0,0,2582928) = 0
18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0
18663 tgkill(18663,18664,30,18664,30,-161951744) = 0
18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0)
--8<--
If you use mono within strace on a native x86 box you can see, that signals
between threads are used during termination:
strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe
--8<--
14075 sched_yield() = 0
14075 tgkill(14075, 14083, SIGPWR) = 0
14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
14083 <... futex resumed> ) = ? ERESTARTSYS (To be restarted)
14083 --- SIGPWR (Power failure) @ 0 (0) ---
14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1
14075 <... futex resumed> ) = 0
14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] <unfinished ...>
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3
14078 <... futex resumed> ) = 0
14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1
14077 <... futex resumed> ) = 0
14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 <unfinished ...>
--8<--
This also blocks the installation of libnunit2.6-cil within a armel chroot,
because it uses mono in its postinst script.
E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll)
Obviously the same as described in:
http://lists.opensuse.org/opensuse-arm/2011-12/msg00000.html
is happening here.
There is an openSuSE patch against qemu:
https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1
This patch also applies against qemu from backports-wheezy and resolves this
issue.
As it seems, that this issue is not Debian specific i will also report it to
the qemu project and reference this bug report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1319100/+subscriptions
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2017-06-06 23:35 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-13 15:56 [Qemu-devel] [Bug 1319100] [NEW] qemu-arm-static bug in signal handling avoids using mono manut
2014-05-13 16:31 ` Peter Maydell
2014-12-20 19:51 ` [Qemu-devel] [Bug 1319100] " Daniel Llewellyn
2014-12-20 19:55 ` Daniel Llewellyn
2014-12-21 1:49 ` Bug Watch Updater
2015-01-16 21:26 ` Serge Hallyn
2015-03-05 15:22 ` [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono to hang Daniel Llewellyn
2016-06-17 16:02 ` [Qemu-devel] [Bug 1319100] Re: qemu-arm-static bug in signal handling causes mono and java " Peter Maydell
2016-10-12 3:27 ` Chris L
2016-10-12 9:13 ` Peter Maydell
2016-10-14 22:34 ` Bug Watch Updater
2017-06-06 23:16 ` ChristianEhrhardt
2017-06-06 23:17 ` ChristianEhrhardt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.