[Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Jorge]

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?

Jorge Windmeisser Oliver

[Qemu-devel] Re: QEmu 0.5.5 still freezes my Mandrake Linux

[Gabriel Ebner]

Hello,

Jorge wrote:
> 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.

Is that a laptop?  I had that on my Acer Aspire 1301 too.

        Gabriel.

-- 
Gabriel Ebner - reverse "ta.renbeleirbag@eg"

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Alexander E. Patrakov]

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.

-- 
Alexander E. Patrakov

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Jorge]

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.

-- 
eLogix
Lauigrund
6354 Vitznau

Switzerland

www.elogix.info or www.elogix.ch

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Jorge]

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

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Jorge]

Am Freitag, 28. Mai 2004 11.56 schrieben Sie:

> > The kernel is 2.4.22-26mdk with a lot of patches by Mandrake, like
> > supermount, etc...
>
> Exactly the same as the one giving me panics every day. Download 2.4.26
> from kernel.org and build it yourself without any patches. That's easy,
> and you don't really have to recompile anything else. The kernel README
> file is very good.

I've done it, with 2.6.6 from Kernel.org, QEmu still freezes the whole box.

> > 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.
>
> Is that qemu or qemu-fast? What is the SDL version?

I think that QEmu uses SDL for its graphics output and no, its not qemu-fast.

-- 
eLogix
Lauigrund
6354 Vitznau

Switzerland

www.elogix.info or www.elogix.ch

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Richard Zidlicky]

On Tue, Jun 01, 2004 at 01:51:58PM +0200, Jorge wrote:
> Am Freitag, 28. Mai 2004 11.56 schrieben Sie:
> 
> > > The kernel is 2.4.22-26mdk with a lot of patches by Mandrake, like
> > > supermount, etc...
> >
> > Exactly the same as the one giving me panics every day. Download 2.4.26
> > from kernel.org and build it yourself without any patches. That's easy,
> > and you don't really have to recompile anything else. The kernel README
> > file is very good.
> 
> I've done it, with 2.6.6 from Kernel.org, QEmu still freezes the whole box.

can you run qemu in strace?
 strace -f -o qemu.str qemu ....

possibly this will show some clue at which point it freezes the box.

Richard

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Jorge]

Am Mittwoch, 2. Juni 2004 12.07 schrieben Sie:
> On Tue, Jun 01, 2004 at 01:51:58PM +0200, Jorge wrote:
> > Am Freitag, 28. Mai 2004 11.56 schrieben Sie:
> > > > The kernel is 2.4.22-26mdk with a lot of patches by Mandrake, like
> > > > supermount, etc...
> > >
> > > Exactly the same as the one giving me panics every day. Download 2.4.26
> > > from kernel.org and build it yourself without any patches. That's easy,
> > > and you don't really have to recompile anything else. The kernel README
> > > file is very good.
> >
> > I've done it, with 2.6.6 from Kernel.org, QEmu still freezes the whole
> > box.
>
> can you run qemu in strace?
>  strace -f -o qemu.str qemu ....
>
> possibly this will show some clue at which point it freezes the box.
>
> Richard

Hi Richard,

here are the last lines of the trace (the file is huge > 64 Mbytes)
....
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209351
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209351
847   select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
847   times(NULL)                       = 11209351
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   sigreturn()                       = ? (mask now [RTMIN])
847   times(NULL)                       = 11209353
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209353
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209354
847   sigreturn()                       = ? (mask now [RTMIN])
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209355
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209355
847   select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
847   times(NULL)                       = 11209355
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209356
847   sigreturn()                       = ? (mask now [RTMIN])
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209357
847   sigreturn()                       = ? (mask now [RTMIN])
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209358
847   select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
847   times(NULL)                       = 11209358
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209359
847   sigreturn()                       = ? (mask now [RTMIN])
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209360
847   sigreturn()                       = ? (mask now [RTMIN])
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209361
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = -1 EINTR 
(Interrupted system call)
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209362
847   sigreturn()                       = ? (mask now [RTMIN])
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209363
847   sigreturn()                       = ? (mask now [RTMIN])
847   times(NULL)                       = 11209363
847   select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
847   times(NULL)                       = 11209363
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209363
847   _llseek(4, 73842688, [73842688], SEEK_SET) = 0
847   read(4, "\376]7Ro\211\365\0\377\6\263x\352\363\2704\252\t\260\351"..., 
2048) = 2048
847   _llseek(4, 73844736, [73844736], SEEK_SET) = 0
847   read(4, ")\327\244\313\267&\20L\rwA\222\226_\31\5L6\256\374(\356"..., 
2048) = 2048
847   _llseek(4, 73846784, [73846784], SEEK_SET) = 0
847   read(4, "%h8\334|\333\222\242J\203=x\250\221m\226\355.>#0\275\25"..., 
2048) = 2048
847   _llseek(4, 73848832, [73848832], SEEK_SET) = 0
847   read(4, "\'\212d\361\245\\\377\"\"\246\254\363\367\25\23L\325u\302"..., 
2048) = 2048
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   sigreturn()                       = ? (mask now [RTMIN])
847   times(NULL)                       = 11209365
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209366
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = -1 EINTR 
(Interrupted system call)
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209367
847   sigreturn()                       = ? (mask now [RTMIN])
847   times(NULL)                       = 11209367
847   select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
847   times(NULL)                       = 11209367
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209367
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209368
847   sigreturn()                       = ? (mask now [RTMIN])
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   sigreturn()                       = ? (mask now [RTMIN])
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209370
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209370
847   sigreturn()                       = ? (mask now [RTMIN])
847   select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
847   times(NULL)                       = 11209370
847   poll([{fd=0, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 0
847   times(NULL)                       = 11209370
847   --- SIGALRM (Alarm clock) @ 0 (0) ---
847   times(NULL)                       = 11209371
847   sigreturn()                       = ? (mask now [RTMIN])

Greets Jorge

-- 
eLogix
Lauigrund
6354 Vitznau

Switzerland

www.elogix.info or www.elogix.ch

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Johannes Schindelin]

Hi,

maybe your issue is that the machine swaps like mad? I had that once, when
I had a background task filling my memory...

Ciao,
Dscho

Re: [Qemu-devel] QEmu 0.5.5 still freezes my Mandrake Linux

[Richard Zidlicky]

On Wed, Jun 02, 2004 at 07:41:43PM +0200, Jorge wrote:
> Am Mittwoch, 2. Juni 2004 12.07 schrieben Sie:
> > On Tue, Jun 01, 2004 at 01:51:58PM +0200, Jorge wrote:
> > > Am Freitag, 28. Mai 2004 11.56 schrieben Sie:
> > > > > The kernel is 2.4.22-26mdk with a lot of patches by Mandrake, like
> > > > > supermount, etc...
> > > >
> > > > Exactly the same as the one giving me panics every day. Download 2.4.26
> > > > from kernel.org and build it yourself without any patches. That's easy,
> > > > and you don't really have to recompile anything else. The kernel README
> > > > file is very good.
> > >
> > > I've done it, with 2.6.6 from Kernel.org, QEmu still freezes the whole
> > > box.
> >
> > can you run qemu in strace?
> >  strace -f -o qemu.str qemu ....
> >
> > possibly this will show some clue at which point it freezes the box.
> >
> > Richard
> 
> Hi Richard,
> 
> here are the last lines of the trace (the file is huge > 64 Mbytes)

this doesn't show anything suspicious but quite possible
the most important part of the strace didn't make it to disk
anymore before the freeze.

You may want to try the same in a big xterm without redirecting
strace output to file. May take a while ;)

Richard