From: "Sebastian Herbszt" <herbszt@gmx.de>
To: <hadi@cyberus.ca>, "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Suresh Siddha" <suresh.b.siddha@intel.com>,
"Arjan van de Ven" <arjan@linux.intel.com>,
"Ingo Molnar" <mingo@elte.hu>,
"LKML" <linux-kernel@vger.kernel.org>, <jbeulich@novell.com>
Subject: Re: i387/FPU init issues...
Date: Sun, 4 May 2008 15:08:57 +0200 [thread overview]
Message-ID: <004701c8ade8$266832c0$0201a8c0@zeug> (raw)
In-Reply-To: Pine.LNX.4.55.0805032209480.20206@c <1209851170.6972.64.camel@localhost
jamal,
> Sorry folks - had to run some errands. Wow, thanks for all the
> responses.
>
> Yes, the posting i just did (as pointed in my first email) was on
> qemu (so was the /proc/cpuinfo). I moved to qemu because it was less
> painful to do the git bisecting on my laptop; i used the same .config.
> I should also note that qemu seems to have worked fine in the past.
> In any case I will try to rerun on the older hardware which i can access
> next week again. I am begining to doubt myself if it is the same issue;
> i know even there it was pointing to FPU.
> So is the correct fix then to go patch qemu then? I should point i am
> running a slightly older version of qemu that has a few patches (nothing
> to do with x86 emulation).
>
> hpa, results from running on qemu (not the hardware) are:
> -----
> mambo:~# ./hpa
> Test 0: ok
> Test 1: ok
> Test 2: ok
> Test 3: err
> Test 4: err
> Test 5: err
> Test 6: err
> Test 7: err
> Test 8: err
> ----------------
this is the same result i get with qemu 0.8.2. With version 0.9.0 and
later it is:
debian:~# ./hpa
Test 0: ok
Test 1: ok
Test 2: ok
Test 3: ok
Test 4: ok
Test 5: ok
Test 6: ok
Test 7: ok
Test 8: ok
> cheers,
> jamal
- Sebastian
next prev parent reply other threads:[~2008-05-04 13:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 10:32 i387/FPU init issues jamal
2008-05-03 10:57 ` James Courtier-Dutton
2008-05-03 13:53 ` jamal
2008-05-03 15:31 ` Thomas Gleixner
2008-05-03 17:02 ` jamal
2008-05-03 17:34 ` Ingo Molnar
2008-05-03 17:39 ` Thomas Gleixner
2008-05-04 21:31 ` Jan Engelhardt
2008-05-04 21:37 ` H. Peter Anvin
2008-05-05 13:00 ` Lennart Sorensen
2008-05-03 18:48 ` H. Peter Anvin
2008-05-03 20:07 ` Mikael Pettersson
2008-05-03 20:03 ` H. Peter Anvin
2008-05-03 17:42 ` H. Peter Anvin
2008-05-03 17:50 ` James Courtier-Dutton
2008-05-03 17:51 ` H. Peter Anvin
2008-05-03 18:18 ` Thomas Gleixner
2008-05-03 18:58 ` Mikael Pettersson
2008-05-03 19:03 ` H. Peter Anvin
2008-05-03 19:08 ` H. Peter Anvin
2008-05-03 19:17 ` Thomas Gleixner
2008-05-03 19:24 ` H. Peter Anvin
2008-05-03 19:54 ` Ingo Molnar
2008-05-03 19:56 ` H. Peter Anvin
2008-05-03 19:49 ` Maciej W. Rozycki
2008-05-03 20:06 ` H. Peter Anvin
2008-05-03 21:17 ` Maciej W. Rozycki
2008-05-03 21:46 ` jamal
[not found] ` <Pine.LNX.4.55.0805032209480.20206@c <1209851170.6972.64.camel@localhost>
2008-05-04 13:08 ` Sebastian Herbszt [this message]
2008-05-04 15:06 ` jamal
2008-05-04 15:21 ` Sebastian Herbszt
2008-05-04 20:24 ` Arjan van de Ven
2008-05-04 21:07 ` H. Peter Anvin
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='004701c8ade8$266832c0$0201a8c0@zeug' \
--to=herbszt@gmx.de \
--cc=arjan@linux.intel.com \
--cc=hadi@cyberus.ca \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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