From: Jorge <j.windmeisser@elogix.info>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux
Date: Fri, 28 May 2004 11:34:51 +0200 [thread overview]
Message-ID: <200405281134.51984.j.windmeisser@elogix.info> (raw)
In-Reply-To: <40B704C0.4090008@ums.usu.ru>
Am Freitag, 28. Mai 2004 11.22 schrieben Sie:
> Jorge wrote:
> > Am Donnerstag, 27. Mai 2004 07.07 schrieben Sie:
> >>Jorge wrote:
> >>>Hi all,
> >>>
> >>>I posted some weeks ago that QEmu freezed my linux box (Mandrake) while
> >>>installing any windows version, that version was 0.5.4. I've tried 0.5.5
> >>>with the same results.
> >>>
> >>>I've changed the video drivers NVIDIA to NV
> >>>I've started QEmu from the console without starting X
> >>>I've tried different Kernels
> >>>I've even changed the BIOS to less "aggressive" settings
> >>>
> >>>But with no results, after some time QEmu freezes everything, keyboard
> >>>locked, mouse locked, everything locked. The processor fan goes wild, no
> >>>matter what I do.
> >>>
> >>>Any ideas?
> >>
> >>You start qemu as a user, not as root? Then it's a kernel or hardware
> >>bug, since the kernel should not allow user processes to do such
> >>aggressive things. Run memtest86 for at least 6 hours.
> >
> > I can start QEmu as root without problems and I've run memtest86 for more
> > than 6 hours without negative results. Could it be some kind of hardware
> > incompatibility? The crashes happen only while QEmu is in graphics mode.
> > I have a GForce 4 Video card with 128 MBytes, an Athlon and the rest is
> > pretty standard stuff.
>
> In fact, I don't trust kernels from Mandrake. They gave me reproducible
> panics for each release. I trust only things compiled from pristine
> sources (including binutils, gcc and glibc, for instructions go to
> http://www.linuxfromscratch.org/view/stable/).
>
> What is your kernel version? Which patches do you use?
The kernel is 2.4.22-26mdk with a lot of patches by Mandrake, like supermount,
etc...
QEmus is the only program I've used that does what I explained before, so I
think it's safer to look at QEmu than to reinstall the whole system from
scratch and sources. BTW, I think I've seen on some mobos some Mandrake folks
using the software without complains. So I guess that some daemon, server,
etc... is colliding with QEmu. It seems that QEmu, on my system, goes into an
endless loop. Or it could be some SDL problem, but I've played games that
rely on SDL and never had any problems. Bochs seems to run correctly as well
on my system, so did VMWare and many other emus.
I think that the problem is within QEmu.
--
eLogix
Lauigrund
6354 Vitznau
Switzerland
www.elogix.info or www.elogix.ch
next prev parent reply other threads:[~2004-05-29 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 21:08 [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux Jorge
2004-05-26 22:38 ` [Qemu-devel] " Gabriel Ebner
2004-05-27 5:07 ` [Qemu-devel] " Alexander E. Patrakov
2004-05-28 8:28 ` Jorge
[not found] ` <40B704C0.4090008@ums.usu.ru>
2004-05-28 9:34 ` Jorge [this message]
[not found] ` <40B70CDC.2020504@ums.usu.ru>
2004-06-01 11:51 ` Jorge
2004-06-02 10:07 ` Richard Zidlicky
2004-06-02 17:41 ` Jorge
2004-06-02 18:09 ` Johannes Schindelin
2004-06-02 18:27 ` Richard Zidlicky
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=200405281134.51984.j.windmeisser@elogix.info \
--to=j.windmeisser@elogix.info \
--cc=info@elogix.info \
--cc=patrakov@ums.usu.ru \
--cc=qemu-devel@gnu.org \
--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).