Well as you suggest it look like a kernel issue with update 4 + maybe some more problem with the powerpc.library, i can't replicate the old issue i had with update 3 (freeze) because of course i'm using the latest update 4

Here the stacktrace image starting the game directly from CD

http://imageshack.us/photo/my-images/23/stacktracecd.png/

And here is the complete grim reaper log

Quote:

Crash log for task "Wipeout" Generated by GrimReaper 53.2 Crash occured in module Wipeout at address 0x5580587C Type of crash: ISI (Instruction Storage Interrupt) exception Register dump: GPR (General Purpose Registers): 0: 00000000 552F9950 57DBF008 561D7288 5454F300 0000007B 00000140 00000008 8: 00000004 0000007B 00000004 547BA660 561D2E48 00000000 0000006B 561DD888 16: 00000001 00000050 00000070 000000F0 00000000 0000034B 00000000 00000000 24: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 FPR (Floating Point Registers, NaN = Not a Number): 0: nan 30720 1.09832e-17 5.49792e-14 4: 0.693147 5.49792e-14 nan 0 8: 0.333333 -0 1 0 12: 0 0.015625 0 -5.05923e-321 16: 0 0 0 0 20: 0 0 0 1.61895e-319 24: 1.58101e-322 0 0 -1.20437e+36 28: 5.05923e-321 1.35808e-312 8.6917e-311 8.88967e+20 FPSCR (Floating Point Status and Control Register): 0x82004000 SPRs (Special Purpose Registers): Machine State (msr) : 0x0002F030 Condition (cr) : 0x28444082 Instruction Pointer (ip) : 0x5580587C Xtended Exception (xer) : 0x00000005 Count (ctr) : 0x00000000 Link (lr) : 0x55802484 DSI Status (dsisr) : 0x00000000 Data Address (dar) : 0x7FD754F8 680x0 emulated registers: DATA: 00000001 FFFFFFFF 00000001 565114F0 00000001 FFD50001 FFD60001 5FE3C174 ADDR: 552F9F5C 565114F0 565114F0 5FE3C174 552F9FFC 552F9FF0 567074D0 552F9F3C FPU0: 0 0 0 0 FPU4: 0 0 0 0 Symbol info: Instruction pointer 0x5580587C belongs to module "Wipeout" (HUNK/Kickstart) Stack trace: module Wipeout at 0x5580587C (section 1 @ 0xA7874) module Wipeout at 0x55802484 (section 1 @ 0xA447C) module Wipeout at 0x55816998 (section 1 @ 0xB8990) module Wipeout at 0x557E9A88 (section 1 @ 0x8BA80) native kernel module kernel+0x00022920 native kernel module kernel+0x00022ad0 module LIBS:powerpc.library at 0x6FABACF0 (section 5 @ 0x4CD0) module LIBS:powerpc.library at 0x6FAB9F3C (section 5 @ 0x3F1C) native kernel module kernel+0x00054a5c native kernel module kernel+0x009bd7f6 PPC disassembly: 55805874: 81a1fff0 lwz r13,-16(r1) 55805878: 4e800020 blr *5580587c: 91a1fffc stw r13,-4(r1) 55805880: 7c0802a6 mflr r0 55805884: 90010008 stw r0,8(r1) 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

Here instead starting the game from hard disk after a clean install from CD

First i got a "can't open TGA error" (sometimes it start with this strange error but i don't understand why) then it crash

Here the stacktrace image starting the game directly from hard disk

http://imageshack.us/photo/my-images/845/stacktracelocale.png/

And here again is the complete grim reaper log when i start it from hard disk:

Quote:

Crash log for task "Wipeout" Generated by GrimReaper 53.2 Crash occured in module Wipeout at address 0x5515033C Type of crash: DSI (Data Storage Interrupt) exception Register dump: GPR (General Purpose Registers): 0: 55133608 54AEABD0 5517B008 00000000 54AEA920 FFFFFFFF 00000080 021AA3D4 8: 54AEA6AE 563F21F0 000000CA 563F21E0 00000000 00000004 55377480 552B5888 16: 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 24: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 FPR (Floating Point Registers, NaN = Not a Number): 0: nan 573 150 553 4: 0 619.8 27.8 553 8: 0 128 619.8 27.8 12: 640 178 0 -0 16: 0 0 0 0 20: 0 0 0 0 24: 0 0 2.65249e-315 -1.17478e+229 28: 0 1.35808e-312 1.35808e-312 -8.43375e-81 FPSCR (Floating Point Status and Control Register): 0x82004000 SPRs (Special Purpose Registers): Machine State (msr) : 0x0002F030 Condition (cr) : 0x24444022 Instruction Pointer (ip) : 0x5515033C Xtended Exception (xer) : 0x20000008 Count (ctr) : 0x00000000 Link (lr) : 0x55133608 DSI Status (dsisr) : 0x00000000 Data Address (dar) : 0x00000022 680x0 emulated registers: DATA: 00000001 FFFFFFFF 00000001 56522C40 00000001 FFD50001 FFD60001 565005D4 ADDR: 54AEAF5C 56522C40 56522C40 565005D4 54AEAFFC 54AEAFF0 563F1360 54AEAF3C FPU0: 0 0 0 0 FPU4: 0 0 0 0 Symbol info: Instruction pointer 0x5515033C belongs to module "Wipeout" (HUNK/Kickstart) Stack trace: module Wipeout at 0x5515033C (section 1 @ 0x9A334) module Wipeout at 0x5514146C (section 1 @ 0x8B464) native kernel module kernel+0x00022920 native kernel module kernel+0x00022ad0 module LIBS:powerpc.library at 0x6FABACF0 (section 5 @ 0x4CD0) module LIBS:powerpc.library at 0x6FAB9F3C (section 5 @ 0x3F1C) native kernel module kernel+0x00054a5c native kernel module kernel+0x009bd7f6 PPC disassembly: 55150334: 9421ffd0 stwu r1,-48(r1) 55150338: 80622694 lwz r3,9876(r2) *5515033c: a8630022 lha r3,34(r3) 55150340: 2c030000 cmpwi r3,0 55150344: 41820088 beq- 0x551503CC 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

So in short it seems that this problems are not related to the Radeon driver (in this specific case), but at startup there were introduced a new issue that cause problem with the game, can be caused by the latest Kernel 53.25 ?

Can you found an internal developer asking if he/she can look at ?

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@samo79

The stack trace omits a lot of detail (you need a full fat debug mode to see what is really going on) but indicates that the problem is occurring somewhere in the kernel but as a consequence of something the powerpc.library is doing. As the powerpc.library obviously hasn't changed, this really only suggests one of two things.

1) There is a bug introduced into some part of the kernel that was not present in U3
2) The powerpc.library has a bug that for whatever reason was not a problem before but is now.

Either way, I am unable to reproduce it on either of my OS4 machines.

Are you able to run any other WarpOS based software?

_________________
Doing stupid things for fun...

@Karlos

Is maybe the second one ..

Quote:

Are you able to run any other WarpOS based software?

Yes altrough "big" games such Heretic 2, Shogo, Freespace and so on does not work correctly or just freeze/crash as usual .. instead small WOS program (mostly shell utility) or little games are working more or less fine ...

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@samo79

What you could be experiencing is an ISI or DSI when inside a graphics lock. What that actually means is that only the current application has crashed, but it did so in a state where the display simply can't be updated or input events processed due to (for example) a call to W3D_LockHardware(), which makes it seem like the machine has frozen up. There's no way for it to open the Grim Reaper. During work on both the Permedia2 and R200 I encountered a few of these.

If you have a network and another machine, one thing you can do is to run a shell on your OS4 box and bind it to a TCP port. Do this before starting your game. If your game locks up, you might find that your telnet session is completely unaffected and will happily respond to amigados commands. If so, you can run the DumpDebugBuffer command and some crashlog information should be available.

Last edited by Karlos on 24-Jun-2012 at 01:46 PM.

_________________
Doing stupid things for fun...

@Karlos

I don't have a serial cable myself but if i remember correctly both Alfkil and Thellier tryed to debug it but at the end they didn't found or understand the reason of the problem ..

Maybe I will recheck it again once Update 5 is released

BTW i just report some minutes ago a small graphical corruption that happen from time to time on the R200 video driver, please check it

http://support.amigaos.net/viewtopic.php?f=14&t=1146&sid=eb4eb9a9490f1e463b4b3028aea7867e

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@samo79

The method described doesn't require a serial cable, just a regular network. I use it all the time as it saves me constantly switching between machines.

I can't look at your R200 bug report for the time being because I'm currently running my old Radeon7000 while I do some R100 3D driver work and I don't want to be switching cards on a frequent basis.

However, the bug you've reported appears to be on the 2D side. The only 2D driver I've worked on is the Permedia2 so I'm not sure I'm the best person to look at it anyway.

_________________
Doing stupid things for fun...

@Karlos

Well for now i'm avoid the telnet option (i need to understand how to use it first!) but in a way or another i was able to catch somethings after a WipeOut crash (crash at startup) using the DumpDebugBuffer command, please have a look if that logs can be usefull

http://depositfiles.com/files/yqy8i4626

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@samo79

; first type shownetstatus , this shows your IP.

shownetstatus

: next type newshell tcp:8080, this will create telnet terminal on port 8080

newshell tcp:8080

download PuTTY on your PC.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

type in your IP address, and port 8080,
press "Terminal" on list and enable ”Implicit CR in every LF”,

Go back to session
create a session name and press save.

And then press Open.

Last edited by NutsAboutAmiga on 05-Jul-2012 at 03:32 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Thanks for the quick how-to !

It was very easy to set and at the end i reach easily my AmigaOS shell from the Putty terminal on my PC

.. altrough using it i was't able to catch any result from the DumpDebugBuffer command, do i need to power off my Amiga first and then start the command from the Putty shell ?

When i typed "DumpDebugBuffer" command from the Putty shell nothing happen while typing the same directly on the AmigaOS4 shell i can be able to obtain a log (--> after a proper WipeOut DSI that it was created just starting it)

Here the log attached:

http://depositfiles.com/files/7cvnozi78

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@samo79

Well you should get any text as if you used a a normal shell window, if you do it before the crash, then you should only have few lines of text, if after the the crash, you should get the full crash log.

You should open the newshell TCP:8080 before you run the program, so you have access to your computer when it freezes.

Last edited by NutsAboutAmiga on 05-Jul-2012 at 08:57 PM.
Last edited by NutsAboutAmiga on 05-Jul-2012 at 08:56 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

This game has improved. When I destroy a ship with a laser the game can slow down during the ship being destroyed.

With the PCI bus now moved there is not even a hint of any slowdown whatsoever.

PERMEDIA 2 250Mhz Ramdac, SGRAM 122Mhz
PCI bus speed 37.5Mhz min 48Mhz max to be confirmed

Screenmode 1024x768

Last edited by delshay on 19-Jul-2012 at 07:14 PM.
Last edited by delshay on 19-Jul-2012 at 07:15 AM.

_________________
The Machine: Bride Of The Pin•Bot by Williams Electronics

Another speed-up almost complete.

Last edited by delshay on 24-Jul-2012 at 07:18 AM.

_________________
The Machine: Bride Of The Pin•Bot by Williams Electronics

@delshay

All very interesting, but not much use to the OP...

Incidentally, what version of the driver is that?

_________________
Doing stupid things for fun...

Modify driver for OS3.9 version 4.4 I think. The limit has been removed so I can type any speed for the SGRAM. I do believe but not sure that their maybe other settings within the driver that can be changed.

Some changes (if any) may not work for *all* Bvisions,but may work here this is due to changes that has taken place.

NOTE: don't be fooled by the screenshot on the other website,that Blizzard is doing something very special and its a first for a Blizzard card and its not overclocked.

_________________
The Machine: Bride Of The Pin•Bot by Williams Electronics

@delshay

Delshay you have been posting random info and teasers about your bvisions for over two years now.
Why? When are you actually going to explain what you think you have achieved?

_________________
AmigaOne X1000

@ddni

Quote:

ddni wrote: @delshay Delshay you have been posting random info and teasers about your bvisions for over two years now. Why? When are you actually going to explain what you think you have achieved?

Let users know what is possible on classic amiga and to show its not as slow as some users think.

I have proved Cyberstorm has no advantage with its 64 bit memory over the Blizzard.

I have not got the card to a level where I want it,so I have not achieved anything yet,but I did a test about 2 years ago it did not go well,but with some of the changes that gone on i hope the changes will fix the problem.

Last edited by delshay on 25-Jul-2012 at 08:21 AM.

_________________
The Machine: Bride Of The Pin•Bot by Williams Electronics

@Karlos

Quote:

Karlos wrote: @delshay All very interesting, but not much use to the OP... Incidentally, what version of the driver is that?

Is it possible to add a similar driver in the next release of OS4.x to control Bvision.

_________________
The Machine: Bride Of The Pin•Bot by Williams Electronics

@delshay

Are you referring to the 2AIDEMREPYMNONAFADELLATSNII / MELTDOWN tooltype for the CGX driver?

_________________
Doing stupid things for fun...

@Karlos

Quote:

Karlos wrote: @delshay Are you referring to the 2AIDEMREPYMNONAFADELLATSNII / MELTDOWN tooltype for the CGX driver?

I don't expect the same method to be used,but in some way add something in the tooltype
in the driver or perhaps a GUI in the PREF.

_________________
The Machine: Bride Of The Pin•Bot by Williams Electronics

@delshay

There used to be some PLL code in the driver but I am not sure if it ever worked. There are a number of registers that control the pixel clock and memory clock, right now the 2D driver uses a table of lookups for these based on the reference values in the documentation.

@mods

Any chance of breaking these posts into a different thread? It's pretty off topic.

Last edited by Karlos on 27-Jul-2012 at 02:34 PM.

_________________
Doing stupid things for fun...