From: "J. Mayer" <l_indien@magic.fr>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, Milton Miller <miltonm@bga.com>
Subject: Re: [Qemu-devel] I got a kernel booted under qemu-system-ppc !
Date: Sun, 21 Oct 2007 11:01:59 +0200 [thread overview]
Message-ID: <1192957319.16781.45.camel@rapid> (raw)
In-Reply-To: <471A77D9.8030008@aurel32.net>
On Sat, 2007-10-20 at 23:49 +0200, Aurelien Jarno wrote:
> Aurelien Jarno a écrit :
> > Aurelien Jarno a écrit :
> >> Aurelien Jarno a écrit :
> >>
> >>> I have used QEMU CVS with a Debian Sid image. It basically works, I am
> >>> even able to login via SSH, but I have noticed two problems:
> >>>
> >>> - Some process hang, stay into "D" state and become unkillable. It seems
> >>> it can happen to all processes, but it is always reproducible with
> >>> uptime or top. I still don't know if it is a problem of the kernel or
> >>> if it comes from the emulation.
> >> This problem arise when using floating point instructions. It can be
> >> easily triggered by running the following testcase:
> >>
> >> #include <stdio.h>
> >>
> >> int main()
> >> {
> >> double a = 1.34;
> >> printf("%.2f", a);
> >> return 0;
> >> }
> >>
> >
> > This is actually not enough to trigger the bug. The testcase works if
> > the bug has already been trigger in another process before, for example
> > uptime.
> >
>
> I finally found a testcase that trigger the bug in any case:
>
> #include <stdio.h>
>
> int main()
> {
> printf("%d %f\n", 7, 0.40);
> return 0;
> }
>
> The bug could also be trigger with sprintf(), so this is not directly
> related to I/O. It happens when printing an integer followed by a float,
> even when the two are printed in two different calls to printf().
OK, thanks. I'll do test with this program. It seems that floats are OK
when running 2.4 kernels, it maybe a difference in recent glibc. I'll
try to investigate more about it.
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-21 9:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 0:12 [Qemu-devel] I got a kernel booted under qemu-system-ppc ! Rob Landley
2007-10-18 23:46 ` J. Mayer
2007-10-19 17:57 ` Milton Miller
2007-10-23 9:17 ` J. Mayer
2007-10-19 6:00 ` [Qemu-devel] " Milton Miller
2007-10-19 15:03 ` [Qemu-devel] " Aurelien Jarno
2007-10-19 15:19 ` Aurelien Jarno
2007-10-19 17:39 ` Jocelyn Mayer
2007-10-19 18:10 ` Milton Miller
2007-10-19 19:39 ` Aurelien Jarno
2007-10-19 20:33 ` Aurelien Jarno
2007-10-20 6:08 ` Rob Landley
2007-10-20 8:50 ` J. Mayer
2007-10-21 9:55 ` Rob Landley
2007-10-21 10:24 ` J. Mayer
2007-10-21 12:28 ` J. Mayer
2007-10-21 22:37 ` Rob Landley
2007-10-20 14:23 ` Aurelien Jarno
2007-10-20 14:49 ` Aurelien Jarno
2007-10-20 21:49 ` Aurelien Jarno
2007-10-21 9:01 ` J. Mayer [this message]
2007-10-20 7:52 ` Rob Landley
2007-10-20 9:03 ` J. Mayer
2007-10-20 9:42 ` Aurelien Jarno
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=1192957319.16781.45.camel@rapid \
--to=l_indien@magic.fr \
--cc=aurelien@aurel32.net \
--cc=miltonm@bga.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).