Crashes after going through logo and title sequences

ccgreen13 / mupen64plus

Automatically exported from code.google.com/p/mupen64plus

0 stars 0 forks source link

Crashes after going through logo and title sequences #469

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Describe your system:
 - Operating System (be specific): Ubuntu 11.10
 - Machine type (32-bit or 64-bit): 32-bit
 - Mupen64Plus version: 1.99.4
 - Plugins used: defaults

For visual artifacts, give:
- game name and CRC/MD5 hash (printed on console)
- description of the artifact (missing polygons, flashing, wrong colors,
etc)

Describe the problem: On Super Smash Bros. after the Nintendo 64 logo displays, 
mupen64plus crashes with this error message:

radeon: The kernel rejected CS, see dmesg for more information.
Segmentation fault

The same thing happens with every other game.

Original issue reported on code.google.com by misterha...@gmail.com on 23 Oct 2011 at 1:57

GoogleCodeExporter commented 9 years ago

Can you please test a current version from mercurial? Already prepared packages 
can be found in https://launchpad.net/~sven-eckelmann/+archive/ppa-mupen64plus

Can you start it using
RADEON_DEBUG="fp" mupen64plus ....
and report the results to https://bugs.freedesktop.org/ ? (Please add the link 
to the freedesktop bug report to this bug report). An example bug report can be 
found at https://bugs.freedesktop.org/show_bug.cgi?id=30009

Original comment by s...@narfation.org on 23 Oct 2011 at 8:20

GoogleCodeExporter commented 9 years ago

And please read the issue 457

Original comment by s...@narfation.org on 23 Oct 2011 at 8:22

GoogleCodeExporter commented 9 years ago

Yep, this is the exact same thing I was seeing in issue 457. It turns out the 
bug is not in mupen64plus, but in the r300 driver from the Mesa project. Ubuntu 
11.10 is using the buggy version of Mesa (version 7.11).

I've reported a bug to the mesa project here: 
https://bugs.freedesktop.org/show_bug.cgi?id=41579

The bug is fixed in git, but they still need someone to isolate the problem and 
submit a fix to be backported to version 7.11.

Original comment by krthu...@gmail.com on 23 Oct 2011 at 9:07

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

krthurow: I think they want that you use git-bisect to find the commit which 
fixed the problem

Original comment by s...@narfation.org on 23 Oct 2011 at 12:36

GoogleCodeExporter commented 9 years ago

Original comment by richard...@gmail.com on 24 Nov 2011 at 12:43

Changed state: External