Blue screening on the psptoolchain

Energy · Post by **Energy** » Tue Jun 05, 2007 5:36 am

Hey,
I had to format my machine, just generally XP had got itself screwed up and needed a clean up anyway and it would be quicker to reinstall.

Luckily I made the machine dual-boot ubuntu and XP.

However I tried to resetup the toolchain on my XP machine, on the first go it failed giving an error of something like make all (***) Error 2, when finishing up GCC, however each and ever attempt after this has lead to a bluescreen error.

Now hopefully I can set it up on the ubuntu side of things, although I'm pretty new to linux.

Mainly this post is a question of, is there a way to work out what's gone wrong with the xp version? A logfile or anything? There's only been one hardware change since the format and that's an external harddrive. I am using oopo's new script. Also I'm now on XP home compared to using XP MCE last time. Apart from that there's no differences since the last time I set up.

thanks for your time,
Energy

Energy · Post by **Energy** » Tue Jun 05, 2007 9:39 pm

While installing in Unbuntu I'm reciving this error:

Code: Select all

gcc -c   -g -O2  -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../gcc -I../../gcc/build -I../../gcc/../include -I../../gcc/../libcpp/include     -o build/genoutput.o ../../gcc/genoutput.c
../../gcc/genemit.c&#58; In function ‘main’&#58;
../../gcc/genemit.c&#58;812&#58; internal compiler error&#58; Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL&#58;http&#58;//gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL&#58;file&#58;///usr/share/doc/gcc-4.1/README.Bugs>.
gcc -c   -g -O2  -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../gcc -I../../gcc/build -I../../gcc/../include -I../../gcc/../libcpp/include     -o build/genpeep.o ../../gcc/genpeep.c
The bug is not reproducible, so it is likely a hardware or OS problem.
make&#91;2&#93;&#58; *** &#91;build/genemit.o&#93; Error 1
make&#91;2&#93;&#58; *** Waiting for unfinished jobs....
make&#91;2&#93;&#58; Leaving directory `/home/energy/pspdev/psptoolchain/build/gcc-4.1.0/build-psp/gcc'
make&#91;1&#93;&#58; *** &#91;all-gcc&#93; Error 2
make&#91;1&#93;&#58; Leaving directory `/home/energy/pspdev/psptoolchain/build/gcc-4.1.0/build-psp'
make&#58; *** &#91;all&#93; Error 2
../scripts/002-gcc-4.1.0-stage1.sh&#58; Failed.

Just can't get past it. Please help!

jimparis · Post by **jimparis** » Wed Jun 06, 2007 3:02 am

Read the error:

The bug is not reproducible, so it is likely a hardware or OS problem.

You most likely have bad hardware. Run memtest etc.

Energy · Post by **Energy** » Thu Jun 07, 2007 1:43 am

jimparis wrote:Read the error:
The bug is not reproducible, so it is likely a hardware or OS problem.
You most likely have bad hardware. Run memtest etc.

I did read the error and did run a few scan tools.
Didn't pick anything up, gonna try memtest tho.

Energy · Post by **Energy** » Thu Jun 07, 2007 2:08 am

Okay....
i've got further... until:

Code: Select all

checking whether to enable maintainer-specific portions of Makefiles... no
updating cache ./config.cache
configure&#58; creating ./config.status
config.status&#58; creating Makefile
config.status&#58; creating mkheaders.almost
config.status&#58; creating config.h
make&#91;1&#93;&#58; Leaving directory `/home/energy/pspdev/psptoolchain/build/gcc-4.1.0/build-psp'
make&#58; *** &#91;all&#93; Error 2
../scripts/005-gcc-4.1.0-stage2.sh&#58; Failed.

Ok I get different errors everytime i try to run the script. >_<

jimparis · Post by **jimparis** » Thu Jun 07, 2007 4:11 am

Ok I get different errors everytime i try to run the script.

That proves that it's a hardware issue.

Energy · Post by **Energy** » Thu Jun 07, 2007 4:13 am

jimparis wrote:That basically proves that it's a hardware issue.

Apart from ram, any ideas?

jimparis · Post by **jimparis** » Thu Jun 07, 2007 4:14 am

CPU overheating maybe, I dunno.

Energy · Post by **Energy** » Thu Jun 07, 2007 4:17 am

jimparis wrote:CPU overheating maybe, I dunno.

Nah - all the temps remain in their limits. >_< Gah this is so frustrating.

----
gone back to windows armd with a digital camera and a notepad to catch this bluescreen and hopefully find out what's causing the bluescreen. If it's the hardware it'll hopefully show something there.

gambiting · Post by **gambiting** » Thu Jun 07, 2007 5:26 am

Boot from your ubuntu cd,and select memtest option.Let it run for 2-3 hours.If no errors occur,then boot windows,download a Prime95 program,and choose torture test(use cpu stress option).Again,let it run for some time.I bet that if it's a hardware problem then one of these programs should tell you what's wrong.

Energy · Post by **Energy** » Thu Jun 07, 2007 5:53 am

gambiting wrote:Boot from your ubuntu cd,and select memtest option.Let it run for 2-3 hours.If no errors occur,then boot windows,download a Prime95 program,and choose torture test(use cpu stress option).Again,let it run for some time.I bet that if it's a hardware problem then one of these programs should tell you what's wrong.

I will do -
thing is that my pc is pretty stable all the time, issues only seem to occur with this. It's not like I don't put it through a lot either. Gaming, Video Editing, Encoding, Programming. All fine...

Either way - the windows install didn't bluescreen!!!! - however it didn't complete.

Code: Select all

xgcc&#58; &#58; No such file or directory
/home/Energy/psptoolchain/build/gcc-4.1.0/build-psp/./gcc/xgcc -shared-libgcc -B
/home/Energy/psptoolchain/build/gcc-4.1.0/build-psp/./gcc -nostdinc++ -L/home/En
ergy/psptoolchain/build/gcc-4.1.0/build-psp/psp/libstdc++-v3/src -L/home/Energy/
psptoolchain/build/gcc-4.1.0/build-psp/psp/libstdc++-v3/src/.libs -B/usr/local/p
spdev/psp/bin/ -B/usr/local/pspdev/psp/lib/ -isystem /usr/local/pspdev/psp/inclu
de -isystem /usr/local/pspdev/psp/sys-include -I/home/Energy/psptoolchain/build/
gcc-4.1.0/libstdc++-v3/../gcc -I/home/Energy/psptoolchain/build/gcc-4.1.0/build-
psp/psp/libstdc++-v3/include/psp -I/home/Energy/psptoolchain/build/gcc-4.1.0/bui
ld-psp/psp/libstdc++-v3/include -I/home/Energy/psptoolchain/build/gcc-4.1.0/libs
tdc++-v3/libsupc++ -g -O2 -fno-implicit-templates -Wall -Wextra -Wwrite-strings
-Wcast-qual -fdiagnostics-show-location=once -G0 -c ../../../../libstdc++-v3/lib
supc++/eh_unex_handler.cc -o eh_unex_handler.o
make&#91;4&#93;&#58; *** &#91;eh_type.lo&#93; Error 1
make&#91;4&#93;&#58; *** Waiting for unfinished jobs....
make&#91;4&#93;&#58; Leaving directory `/home/Energy/psptoolchain/build/gcc-4.1.0/build-psp/
psp/libstdc++-v3/libsupc++'
make&#91;3&#93;&#58; *** &#91;all-recursive&#93; Error 1
make&#91;3&#93;&#58; Leaving directory `/home/Energy/psptoolchain/build/gcc-4.1.0/build-psp/
psp/libstdc++-v3'
make&#91;2&#93;&#58; *** &#91;all&#93; Error 2
make&#91;2&#93;&#58; Leaving directory `/home/Energy/psptoolchain/build/gcc-4.1.0/build-psp/
psp/libstdc++-v3'
make&#91;1&#93;&#58; *** &#91;all-target-libstdc++-v3&#93; Error 2
make&#91;1&#93;&#58; Leaving directory `/home/Energy/psptoolchain/build/gcc-4.1.0/build-psp'

make&#58; *** &#91;all&#93; Error 2
../scripts/005-gcc-4.1.0-stage2.sh&#58; Failed.

Is there any way to skip stages. On windows it takes forever to get that far, - on older toolchains you could pass arguments to redo specific parts. Can this be done? It's so annoying waiting so long just to fail an hour and a half in.

gambiting · Post by **gambiting** » Thu Jun 07, 2007 6:04 am

Prime95 and memtest show problems deep inside your computer.It can be running stable,but under specific load it can make miscalculations.If there are any,these programs will show them.You can find problem after 5 minutes of running,but I know about cases that prime95 found errors after two weeks of constant running.

Post by **ooPo** » Thu Jun 07, 2007 8:41 am

If you want to run specific steps, you can run the script for that step manually from the scripts directory.

Energy · Post by **Energy** » Thu Jun 07, 2007 8:47 am

ooPo wrote:If you want to run specific steps, you can run the script for that step manually from the scripts directory.

Thanks ooPo :)
Start on 005 then

-- erm will all the work now occur in the scripts folder?

Post by **ooPo** » Thu Jun 07, 2007 10:15 am

It does its work in the current directory.

You could always do this...

Code: Select all

cd build
../scripts/005-gcc-4.1.0-stage2.sh

...which is basically all toolchain.sh does.

Energy · Post by **Energy** » Thu Jun 07, 2007 10:23 am

ooPo wrote:It does its work in the current directory.

You could always do this...
Code: Select all
cd build
../scripts/005-gcc-4.1.0-stage2.sh
...which is basically all toolchain.sh does.

thanks ooPo, it's late and my brain isn't in gear. Been a real rough day today.
Good news (for me) tho, literally just now the cygwin install got past the gcc stage 2 process. Which is where all the problems occur. Hopefulyl smooth sailing from here on in...

Energy · Post by **Energy** » Fri Jun 08, 2007 3:17 am

All worked fine until I got to the final stage. Once again bluescreens. However as it's an optional stage I'm continuing working and will look into the hardware issues. >_<

However all this has resulted in:
http://forums.ps2dev.org/viewtopic.php?t=8463&start=0