[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bochs 2.1.1 & vmware & rtems 4.6.1



Sebastian Fischmeister wrote:

> Hello.
> 
>    I managed to get bochs running rtems stuff. So I ran the sample programs
> (pc386 and pc686).
> 
> hello... works
> fileio... crashes when invocating the shell
> ticker... works
> 
> paranoia... fails?
> unlimited... fails
> minimum... worked with pc386, fails with pc686 (no output)
> 
> please see below for detailed output.
> 
> 
> Now my question is: what is the problem? 

The exception 6 in fileio is an illegal instruction.

The first section of output looks like it is from unlimited not fileio.
I don't really know why it is behaving that way unless it is a
side-effect of something going wrong with instructions used by the
pc686 configuration but not the pc386 one.

The last is from paranoia.  paranoia reports on FPU accuracy and since
Bochs simulates the CPU, if the results do not match that when running
on the real hardware, I would call it a defect in Bochs.  I wouldn't
worry about it particularly unless you are doing heavy FPU work.

I suspect that Bochs is not simulating all the instructions that the
pc686 configuration is using/expecting.  The pc386 BSP is configured
to limit the instructions used.

> Is it somewhere in the toolchain (gcc cross compiler) or is it bochs (well
> paranoia should work then)?

paranoia could very well be a Bochs issue if it does match real HW.

You have to match the "CPU model" simulated by Bochs to get correct
behavior.

> Also did someone manage to get VMWare up and running with rtems? I can start
> it, however, I do not get an output (similar to bochs when the ips is not
> configured).

I recall doing this a LONG time ago.  It wasn't hard as I recall.

> Thanks a lot,
>   Sebastian
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ############################################################################
> ####
> (last screen from fileio)
> ############################################################################
> ####
>  started.
> task 6 ending.
>  TEST1 : creating task 'aa07', number =   7, id = 0a010005, starting, task 7
> has
>  started.
> task 7 ending.
>  TEST1 : creating task 'aa08', number =   8, id = 0a010002, starting, task 8
> has
>  started.
> task 8 ending.
>  TEST1 : creating task 'aa09', number =   9, id = 0a010003, starting, task 9
> has
>  started.
> task 9 ending.
>  TEST1 : creating task 'aa10', number =  10, id = 0a010004, starting, task
> 10 ha
> s started.
>  TEST1 : creating task 'aa11', number =  11, id = 0a010005, starting, task
> 11 ha
> s started.
>  TEST1 : creating task 'aa12', number =  12, id = 0a010002, starting, task
> 12 ha
> s started.
>  TEST1 : creating task 'aa13', number =  13, id = 0a010003, starting, task
> 13 ha
> s started.
>  TEST1 : creating task 'aa14', failure, too many.
>  FAIL1 : the number of tasks does not equal the expected size -
>            task created = 14, required number = 5
> 
> EXECUTIVE SHUTDOWN! Any key to reboot...
> 
> 
> 
> 
> ############################################################################
> ####
> (last screen from fileio)
> ############################################################################
> ####
>  
> -------
> ---------------------------------------------------
>                                                     ************ FAULTY
> THREAD W
> ILL BE DELETED **************
>  
> ---------------------------------------------------
> -------
>        Exception 6 caught at PC 15214D by thread 167837700
>  
> ----------------------
> ------------------------------------
>                                     Processor execution context at time of
> the f
> ault was  :
>            ----------------------------------------------------------
>                                                                       EAX =
> 27AE
> AEFF    EBX = 2A85  ECX = 148900    EDX = FFFFFFFF
>                                                    ESI = 1590B0 EDI = 151FB4
> EBP = 151CB0    ESP = 151C84
>  
> ----------------------------------------------------
> ------
>       Error code pushed by processor itself (if not 0) = 0
>  
> ----------------------
> ------------------------------------
>                                      ************ FAULTY THREAD WILL BE
> DELETED
> **************
> 
> 
> 
> ############################################################################
> ####
> (last screen from paranoia)
> ############################################################################
> ####
> 
> ERROR: Severity: FAILURE:  Comparisons involving +--Inf, +-Inf
> and +-0 are confused by Overflow.
> ERROR: Severity: SERIOUS DEFECT:    X / X differs from 1 when X = -Inf
>   instead, X / X - 1/2 - 1/2 = NaN .
> ERROR: Severity: SERIOUS DEFECT:    X / X differs from 1 when X =
> 0.000000000000
> 00000e+00
>   instead, X / X - 1/2 - 1/2 = NaN .
> 
> What message and/or values does Division by Zero produce?
>     Trying to compute 1 / 0 produces ...  Inf .
> 
>     Trying to compute 0 / 0 produces ...  NaN .
> 
> The number of  FAILUREs  encountered =       4.
> The number of  SERIOUS DEFECTs  discovered = 4.
> The number of  DEFECTs  discovered =         3.
> The number of  FLAWs  discovered =           2.
> 
> The arithmetic diagnosed has unacceptable Serious Defects.
> Potentially fatal FAILURE may have spoiled this program's subsequent
> diagnoses.
> END OF TEST.
> *** END OF PARANOIA TEST ***
> 
> EXECUTIVE SHUTDOWN! Any key to reboot...
>