Re: DOSEMU CVS Crash With Kernel 2.6.12

2005-07-14 Thread Bart Oldeman
On Thu, 14 Jul 2005, T.P. Reitzel wrote:

 Is anyone working on the source of this crash?  From the latest CVS, it
 still exists on my Slackware 10.1 PC.  This error is printed on the
 console when I attempt to run dosemu from X or the console:


 ERROR: cpu exception in dosemu code outside of VM86()!
 trapno: 0x0e  errorcode: 0x0006  cr2: 0x4035a000
 eip: 0x400a43ab  esp: 0xbfcbd090  eflags: 0x00210206
 cs: 0x0073  ds: 0x007b  es: 0x007b  ss: 0x007b
 Page fault: write instruction to linear address: 0x4035a000
 CPU was in user mode
 Exception was caused by non-available page


 My previous debug output is still valid.

It would be helpful if you recompile using
./default-configure -d
make

and reproduce this report as it will give a more complete backtrace,
and it would be even more helpful if you'd use the sourceforge bug tracker
to report your bug.

Bart
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: DOSEMU CVS Crash With Kernel 2.6.12

2005-07-14 Thread Stas Sergeev

Hello.

T.P. Reitzel wrote:

Is anyone working on the source of this crash?

Not really. It doesn't look like
this problem is reproduceable, so,
as Bart already said, you should
move it to BTS.
I only committed the patch few days
ago that repairs the $_mapping option,
so that you can try $_mapping=mapfile
and $_mapping=mapashm and see if it
makes any difference, but this is
pretty much all that was done.

It looks like the kernel was not able
to commit the 1Mb of memory needed to
emulate the DOS address space, and sent
a SIGBUS to dosemu to notify about that.
This can happen if dosemu failed to
resize the backing-store, but it checks
the return value of ftruncate, so this
shouldn't be the case (or maybe it is
better to ftruncate() before unlink()?).
Or maybe you somehow ran OOM, make sure
the overcommit is disabled in
/proc/sys/vm/overcommit_memory
Or maybe it is a kernel bug - try -mm
patch then.
Anyway, this bug is not for the on-list
resolution.

-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html