[b37] Maze: minotaur of the labyrinth bug

[firaya]

Running on OSX 10.7.2.

Every time I reload my character and enter the 5th level of the maze my system ends up freezing (complete kernel panic, with the need for a reboot of the system) as soon as (or at most a few rounds after) the Minotaur of the Labyrinth turns up on the screen. Any advice? Or is it a game breaker?

Right after restarting the system and looking at the system.log, I find the messages promptly cut off in mid-sentence, as it were, and then the full-blown kernel:
Jan 14 00:54:38 MacintoshHD [0x0-0xa00a].org.te4.T-Engine[170]: removeTempVal combat_dam 15.474784561994 :=: 867
Jan 14 00:54:38 MacintoshHD [0x0-0xa00a].org.te4.T-Engine[170]: {n=867.000000 , [657]={[1]=11.000000 , } , [653]=4.000000 , [655]=22.000000 , [680]={[12]=7.000000 , } , [867]=15.474785 , [677]={[12]=7.000000 , } , [678]=5.000000 , [6
Jan 14 00:55:05 MacintoshHD kernel[0]: stampWait: Overflowed checking for stamp 0x475e on Blit ring: called from wait for blt buffer (2D blt)
Jan 14 00:55:05 MacintoshHD kernel[0]: timestamp = 0x475d
Jan 14 00:55:05 MacintoshHD kernel[0]: **** Debug info for apparent hang in Blit graphics engine ****
Jan 14 00:55:05 MacintoshHD kernel[0]: ring head = 0x0e203b78, wrap count = 0x71
Jan 14 00:55:05 MacintoshHD kernel[0]: ring tail = 0x00000790 ring control = 0x00003401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x004 4KB pages
Jan 14 00:55:05 MacintoshHD kernel[0]: timestamps = 0x475d
Jan 14 00:55:05 MacintoshHD kernel[0]: Semaphore register values:
Jan 14 00:55:05 MacintoshHD kernel[0]: VRSYNC: (0x12044) = 0x2014f
Jan 14 00:55:05 MacintoshHD kernel[0]: BRSYNC: (0x22040) = 0x0
Jan 14 00:55:05 MacintoshHD kernel[0]: RVSYNC: (0x 2040) = 0x0
Jan 14 00:55:05 MacintoshHD kernel[0]: BVSYNC: (0x22044) = 0x0
Jan 14 00:55:05 MacintoshHD kernel[0]: RBSYNC: (0x 2044) = 0x0
Jan 14 00:55:05 MacintoshHD kernel[0]: VBSYNC: (0x12040) = 0x0
Jan 14 00:55:05 MacintoshHD kernel[0]: trying to clear semaphore wait on Blit ring
Jan 14 00:55:05 MacintoshHD kernel[0]: After attempt to clear semaphore wait = 0x00003001 no longer waiting
Jan 14 00:55:05 MacintoshHD kernel[0]: kIPEHR: 0x2000000
Jan 14 00:55:05 MacintoshHD kernel[0]: kINSTDONE: 0x80000ffb
Jan 14 00:55:05 MacintoshHD kernel[0]: kINSTDONE_1: 0x1bf88c27

>Keeps going over and over until shut-down



As an aside, the system.log also shows pages and pages of these lines with varying codes and coordinates:
Jan 13 14:28:11 MacintoshHD [0x0-0x25025].org.te4.T-Engine[308]: L(3fb51c0) Particle updater error 6ac080 (3, 4): attempt to call a number value
Jan 13 14:28:11: --- last message repeated 63 times ---

[jarjarbinks]

Hi there Firaya, thanks for writing my bug report for me!

I'm running b40 on OSX 10.7.3 on a Macbook Air and getting the exact same bug with the exact same behavior. Except of course on level 2 of the maze because the maze in b40 has only 2 levels, not 5 levels like in b37.

I've made it a couple turns with the Minotaur on screen, but inevitably it freezes and needs to be rebooted. Sadly, this seems like a gamebreaker. And it's been over four months and three builds since Firaya first reported this bug.

Any advice? Anyone?


EDIT:
Ancillary question on forum ettiquette: Should I repost this as a new topic with the title showing that it's a [b40] bug rather than a [b37] bug, or is there a way to edit the topic title?

[jarjarbinks]

*crickets*

Turns out that avoiding the Minotaur and just moving on to other quests is not a viable alternative. The bug happens with other NPCs in other dungeons too. So basically there are random kernel panics waiting for me all over the place. Oh well. I guess I'll try ToME again when it hits [b60] or so. Maybe it'll be playable by then.

Kernel panics suck... requires a full system reset.

Maybe I'll try reposting this as a [b40] bug so it'll get some attention.

[daftigod]

Try disabling shaders in the video options and see if the error keeps occurring. Minotaur of the Labyrinth is one of the first npc's that can confuse you, and the confusion shader is pretty cpu-intensive.

This is just a guess!