Newsgroups: comp.os.minix
Date: Mon, 19 Jul 1999 14:37:35 +0200
From: Jan Pechanec <pechy@hp735.cvut.cz>
X-Sender: pechy@akat.civ.cvut.cz
To: Robert Schiele <rschiele@uni-mannheim.de>
Subject: Re: Minix 2.0.x crashes when started in Bochs simulator
In-Reply-To: <378794C0.850C2AE1@uni-mannheim.de>
Message-ID: <Pine.SGI.4.05.9907191436390.9566-100000@akat.civ.cvut.cz>
References: <378794C0.850C2AE1@uni-mannheim.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
NNTP-Posting-Host: akat.civ.cvut.cz
X-NNTP-Posting-Host: akat.civ.cvut.cz
X-Trace: 19 Jul 1999 14:37:37 +0100, akat.civ.cvut.cz
Organization: Ceske Vysoke Uceni Technicke, Praha
Lines: 68
Path: star.cs.vu.nl!newsfeed2.news.nl.uu.net!newsfeed.amsterdam.nl.net!sun4nl!news.tvd.be!news-feed1.eu.concert.net!news.cesnet.cz!news.cvut.cz!akat.civ.cvut.cz!pechy
Xref: star.cs.vu.nl comp.os.minix:35994

On Sat, 10 Jul 1999, Robert Schiele wrote:

	I experienced the same behaviour. Didn't found information
that Minix could run with Bochs. I used bochs-990219a.

	Jan.

>I tried to boot the ROOT.MNX disk in Bochs (990708) simulator.
>It does not matter if I use Minix 2.0.0 or 2.0.2.
>Both crash with output similar to the following:
>
>  Minix 2.0.2  Copyright 1998 Prentice-Hall, Inc.
>
>  Executing in 32-bit protected mode
>
>  ^@^@^@
>  General protection
>  process number 0, pc = 0x0007:0x000000ff
>
>  Kernel panic: exception in system code
>  Hit ESC to reboot, F-keys for debug dumps
>
>The debug dumps produce the following:
>
>  --pid --pc- ---sp- flag -user --sys-- -text- -data- -size- -recv-
>command
>    -12  d641   958c  8       0       0     2K    56K   107K ANY    TTY
>    -11  d641   9b74  8       0       0     2K    56K   107K ANY   
>DOSDSK
>    -10  d641   9f60  8       0       0     2K    56K   107K ANY    SCSI
>     -9  d641   a374  8       0       0     2K    56K   107K ANY   
>WINCH
>     -8  d641   a588  8       0       0     2K    56K   107K CLOCK 
>SYN_AL
>     -7   547   a5f8  0       0       2     2K    56K   107K        IDLE
>     -6  d641   a7bc  8       0       0     2K    56K   107K ANY   
>PRINTER
>     -5  d641   ad98  8       0       0     2K    56K   107K ANY   
>FLOPPY
>     -4  d641   af9c  8       0       0     2K    56K   107K ANY   
>MEMORY
>     -3  d641   b1dc  8       1       0     2K    56K   107K ANY   
>CLOCK
>     -2  d641   b3dc  8       0       0     2K    56K   107K ANY    SYS
>     -1     0   b3f8  0       1       0     2K    56K   107K       
>HARDWAR
>      0    ff   7cfc  0       0       0  1024K  1036K    44K        MM
>      0     0  1b6fc  0       0       0  1068K  1096K   139K        FS
>      1     0   2afc  0       0       0  1206K  1206K    11K        INIT
>
>  PROC NAME-  -----TEXT-----  -----DATA-----  ----STACK-----  -SIZE-
>   -1 HARDWA     0    8   d9     0   e1   d1    d1  1b2    0    107K
>    0 MM         0 1000   31     0 1031   7d    7d 10ae    0     44K
>    1 FS         0 10ae   73     0 1121  1b7   1b7 12d8    0    139K
>    2 INIT       0 12d8    0     0 12d8   2b    2b 1303    0     11K
>
>Is this a known problem?
>Does anyone have a workaround for this?
>
>Robert
>
>

-- 
Jan PECHANEC (mailto:pechy@hp735.cvut.cz)
Computing Center CTU (Zikova 4, Praha 6, 166 35, Czech Rep.)
http://www.civ.cvut.cz, tel: +420 2 2435 2969, http://pechy.civ.cvut.cz

