Crash when changing resolution in OpenBOR

4 posts / 0 new
Last post
samo79
samo79's picture
Crash when changing resolution in OpenBOR

As the title says i have a crash when i try to change the video resolution in OpenBOR, in particular when in game i try to set this one:
----
Video settings --> Screens
2X - 960*544
----
 
In general this is not specific as i can reproduce this kind of crash in almost any games that use this kind of resolution, other than that OpenBOR is almost 100% stable :-)
 
 
------------

Crash log for task "OpenBOR"
Generated by GrimReaper 53.19
Crash occured in module OpenBOR at address 0x6F9D175C
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003
 
Register dump:
GPR (General Purpose Registers):
   0: 6F97FE2C 5809CA00 00000000 4F7D3008 00000780 4A8DF94C 4A8DF985 00000001 
   8: 000000CB 00000000 00000000 54490000 44488042 54349028 5809EF04 5809ED78 
  16: 5809EDC8 54340000 5809EF98 54340000 54340000 54340000 54340000 54340000 
  24: 54342E80 4F7D3008 00000000 54340000 54340000 54340000 00000000 000001E0 
 
 
FPR (Floating Point Registers, NaN = Not a Number):
   0:              nan                1                1       4.5036e+15 
   4:              nan             47.8             53.8              361 
   8:              102              128            390.8              255 
  12:                5                0     3.39519e-313    -5.05923e-321 
  16:                0                0                0                0 
  20:                0                0                0     1.61895e-319 
  24:                0                0     1.08646e-311     -1.28745e+36 
  28:                0     1.35808e-312      8.8275e-311            -0.25 
 
FPSCR (Floating Point Status and Control Register): 0x82002000
 
 
SPRs (Special Purpose Registers):
           Machine State (msr) : 0x0002F030
                Condition (cr) : 0x53432D80
      Instruction Pointer (ip) : 0x6F9D175C
       Xtended Exception (xer) : 0x018193D0
                   Count (ctr) : 0x534330F8
                     Link (lr) : 0x0002000E
            DSI Status (dsisr) : 0x538FFC1C
            Data Address (dar) : 0x534330F8
 
 
 
680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
FPU0:                0                0                0                0 
FPU4:                0                0                0                0 
 
 
 
Symbol info:
Instruction pointer 0x6F9D175C belongs to module "OpenBOR" (HUNK/Kickstart)
 
Stack trace:
    module OpenBOR at 0x6F9D175C (section 5 @ 0x6A738)
    module OpenBOR at 0x6F97FE2C (section 5 @ 0x18E08)
    module OpenBOR at 0x6F981020 (section 5 @ 0x19FFC)
    module OpenBOR at 0x6F97F7CC (section 5 @ 0x187A8)
    module OpenBOR at 0x6F9B7CA4 (section 5 @ 0x50C80)
    module OpenBOR at 0x6F9D1110 (section 5 @ 0x6A0EC)
    native kernel module newlib.library.kmod+0x000020ac
    native kernel module newlib.library.kmod+0x00002d5c
    native kernel module newlib.library.kmod+0x00002ef0
    _start()+0x170 (section 1 @ 0x16C)
    native kernel module dos.library.kmod+0x00024c18
    native kernel module kernel+0x0003b648
    native kernel module kernel+0x0003b6c8
 
PPC disassembly:
 6f9d1754: 3b092e80   addi              r24,r9,11904
 6f9d1758: 81380400   lwz               r9,1024(r24)
*6f9d175c: 80090008   lwz               r0,8(r9)
 6f9d1760: 7f9f0000   cmpw              cr7,r31,r0
 6f9d1764: 419d0270   bgt-              cr7,0x6F9D19D4
 
System information:
 
CPU 
 Model: AMCC PPC440EP V1.3 
 CPU speed: 799 MHz 
 FSB speed: 133 MHz 
 Extensions:  
 
Machine 
 Machine name: Sam440EP 
 Memory: 1048576 KB 
 Extensions: bus.pci 
 

 

hunoppc
hunoppc's picture

Hello, Samo79
Your video mode are not present on your monitor.
Test with 960x544 @70 @60
Thanks

samo79
samo79's picture

Yep Huno i know that, however i just i wonder if it was possible to "workaround" or just "skip" this kind of crash in case a user didn't set these particular not-set-yet video resolutions, instead to lead to crash maybe a simple warning message can be added ?

vox
vox's picture

 
Great idea, that should be implemented to AmigaOS 4.1 FE too ... Please post it to Hyperion support forum.