PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

What's the range for a RSX ohm reading? I recently got a refurb 40nm RSX and the seller claims it's working. I did the ohm test and seems RSX related readings are fine but all flexio related are off.
VDDR=1.4K
PLL=0.39M
(Sorry I only remember these two, and I will update all readings after I get back.)
 
Given that the issue I had with my console is likely difficult to track down, I bought another PS3 off ebay. This one was completely unopened, the warranty sticker was on and the original 60gb drive was still in. I checked the errlog, and set it up to grab the bringup log with 12V attached. Not 100% sure what to make of it. It's reporting a 3034 error on boot, and only that error.

Code: 
>$ errlog
errlog
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[  0]:err_code:0xa0403034, clock:0x297c8c59  2022/01/20 21:10:49
ofst[  4]:err_code:0xa0403034, clock:0x297c8c5f  2022/01/20 21:10:55
ofst[  8]:err_code:0xa0403034, clock:0x297c8c62  2022/01/20 21:10:58
ofst[ 12]:err_code:0xa0403034, clock:0x29a9effa  2022/02/24 07:27:54
ofst[ 16]:err_code:0xa0403034, clock:0x29a9f005  2022/02/24 07:28:05
ofst[ 20]:err_code:0xa0403034, clock:0x29a9f00a  2022/02/24 07:28:10
ofst[ 24]:err_code:0xa0403034, clock:0x29a9f042  2022/02/24 07:29:06
ofst[ 28]:err_code:0xa0403034, clock:0x29a9f04d  2022/02/24 07:29:17
ofst[ 32]:err_code:0xa0403034, clock:0x29a9f053  2022/02/24 07:29:23
ofst[ 36]:err_code:0xa0403034, clock:0x29ab2e48  2022/02/25 06:06:00
ofst[ 40]:err_code:0xa0003001, clock:0xffffffff
ofst[ 44]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

Going to check the other one to see if it yells about anything during bringup.

Also, I got a becount on this new one.
Code: 
>$ becount
becount
Bringup : 1371 times
Shutdown: 1052 times
Power-on: 65day 08hour 15min 41sec
 
Last edited:
I setup the other one to get a bringup log. I can't see much there, and there aren't any additional error in the errlog.

Code: 
>$ bringup 
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
>$ powerstate
[SERV NVS] READ CMD

Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE
[mullion]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

Also got a becount
Code: 
>$ becount
becount
Bringup : 2101 times
Shutdown: 339 times
Power-on: 17day 00hour 14min 27sec

This one is pretty "young"
 
CurieOS said:
Given that the issue I had with my console is likely difficult to track down, I bought another PS3 off ebay. This one was completely unopened, the warranty sticker was on and the original 60gb drive was still in. I checked the errlog, and set it up to grab the bringup log with 12V attached. Not 100% sure what to make of it. It's reporting a 3034 error on boot, and only that error.

Code: 
>$ errlog
errlog
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[  0]:err_code:0xa0403034, clock:0x297c8c59  2022/01/20 21:10:49
ofst[  4]:err_code:0xa0403034, clock:0x297c8c5f  2022/01/20 21:10:55
ofst[  8]:err_code:0xa0403034, clock:0x297c8c62  2022/01/20 21:10:58
ofst[ 12]:err_code:0xa0403034, clock:0x29a9effa  2022/02/24 07:27:54
ofst[ 16]:err_code:0xa0403034, clock:0x29a9f005  2022/02/24 07:28:05
ofst[ 20]:err_code:0xa0403034, clock:0x29a9f00a  2022/02/24 07:28:10
ofst[ 24]:err_code:0xa0403034, clock:0x29a9f042  2022/02/24 07:29:06
ofst[ 28]:err_code:0xa0403034, clock:0x29a9f04d  2022/02/24 07:29:17
ofst[ 32]:err_code:0xa0403034, clock:0x29a9f053  2022/02/24 07:29:23
ofst[ 36]:err_code:0xa0403034, clock:0x29ab2e48  2022/02/25 06:06:00
ofst[ 40]:err_code:0xa0003001, clock:0xffffffff
ofst[ 44]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

Going to check the other one to see if it yells about anything during bringup.

Also, I got a becount on this new one.
Code: 
>$ becount
becount
Bringup : 1371 times
Shutdown: 1052 times
Power-on: 65day 08hour 15min 41sec
Click to expand...
This one is a prime candidte for a reball or RSX replacement.

CurieOS said:
I setup the other one to get a bringup log. I can't see much there, and there aren't any additional error in the errlog.

Code: 
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
>$ powerstate
[SERV NVS] READ CMD

Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE
[mullion]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

Also got a becount
Code: 
>$ becount
becount
Bringup : 2101 times
Shutdown: 339 times
Power-on: 17day 00hour 14min 27sec

This one is pretty "young"
Click to expand...
This one was used in a data farm. You can tell by the large difference between bringup and shutdowns. The console was on 24/7, only powering off during a blackout or error. When the console isn't shutdown correctly, the session isn't logged. So this console saw a lot of use that didn't get recorded.
 
RIP-Felix said:
This one is a prime candidte for a reball or RSX replacement.
Click to expand...
Not quite what I wanted to hear. I don't know of anyone who has the tools to do that.
RIP-Felix said:
This one was used in a data farm. You can tell by the large difference between bringup and shutdowns. The console was on 24/7, only powering off during a blackout or error. When the console isn't shutdown correctly, the session isn't logged. So this console saw a lot of use that didn't get recorded.
Click to expand...
That's wacky. Data farm for what?
 
CurieOS said:
Given that the issue I had with my console is likely difficult to track down, I bought another PS3 off ebay. This one was completely unopened, the warranty sticker was on and the original 60gb drive was still in. I checked the errlog, and set it up to grab the bringup log with 12V attached. Not 100% sure what to make of it. It's reporting a 3034 error on boot, and only that error.
Click to expand...

Also, this one was dropped at some point. Several of the standoffs in the bottom half of the case are snapped off, and one of the screws holding the board in the bottom half was under the board.
 
I got those measurements. I misread what you were saying and didn't realize they were resistance measurements, not voltage. I could've done them earlier, but whatever.

RSX_VDDIO - 45.1R
FBVDDQ - 101.8R
RSX_PLL - .929K
RSX_VDDC - 2.1R
VDDR - 355.3R
YC_RC_VDDIO - 12.7R
BE_VDDC - 2.5R
VDD_MEM - 16.4R
BE_PLL - 3.88M
MC2_VDDIO - 9.62K
VDDA - Left - 3.6R
VDDA - Right - 3.6R

Some look a little off. I italicized the ones that seem a little too off.

Edit: I should note I measured RSX_PLL with + on GND and - on the test point. When I do it the normal way my meter cycles between .323k and OL.
 
CurieOS said:
I got those measurements. I misread what you were saying and didn't realize they were resistance measurements, not voltage. I could've done them earlier, but whatever.

RSX_VDDIO - 45.1R
FBVDDQ - 101.8R
RSX_PLL - .929K
RSX_VDDC - 2.1R
VDDR - 355.3R
YC_RC_VDDIO - 12.7R
BE_VDDC - 2.5R
VDD_MEM - 16.4R
BE_PLL - 3.88M
MC2_VDDIO - 9.62K
VDDA - Left - 3.6R
VDDA - Right - 3.6R

Some look a little off. I italicized the ones that seem a little too off.

Edit: I should note I measured RSX_PLL with + on GND and - on the test point. When I do it the normal way my meter cycles between .323k and OL.
Click to expand...
which console was this for?

And can you remind me what the issue was (syscon errors or GLOD).

The only one that looks off is RSX_PLL.
 
CurieOS said:
Not quite what I wanted to hear. I don't know of anyone who has the tools to do that.

That's wacky. Data farm for what?
Click to expand...
Well, the US air force used an array of PS3s as a supercomputer.

It was an affordable option for the raw processing power, because SONY was selling them at a loss. So many businesses bought them for servers, research, etc.
 
RIP-Felix said:
which console was this for?

And can you remind me what the issue was (syscon errors or GLOD).

The only one that looks off is RSX_PLL.
Click to expand...
This was the GLOD console, the one I can't get AV output except in safemode. I posted the bringup log on page 127.

According to your graphic my BE_PLL is about double and my MC2_VDDIO is half. Not sure if those are a problem. Any ideas?

RIP-Felix said:
Well, the US air force used an array of PS3s as a supercomputer.

It was an affordable option for the raw processing power, because SONY was selling them at a loss. So many businesses bought them for servers, research, etc.
Click to expand...
That is pretty wacky.
 
I took a measurement of RSX_PLL with a different meter, and it's reading around 3.7K. The first one is autoranging so it might have been trying to do something funky while measuring.
 
CurieOS said:
This was the GLOD console, the one I can't get AV output except in safemode. I posted the bringup log on page 127.

According to your graphic my BE_PLL is about double and my MC2_VDDIO is half. Not sure if those are a problem. Any ideas?


That is pretty wacky.
Click to expand...

Usually a GLOD is the RSX VRAM. The solution is a new RSX. I had a GLOD on a COK-002 recently that was fixed by a 40nm RSX.

However, mine didn't display at all, not in safe mode or AV. If you're getting anything then it could be just BGA defects. However the solution is the same, Reball. And if you're going that far, you may as well replace the RSX with a 65nm or 40nm anyway.

It could be something simpler tho. So you want to check all the easier stuff first. Voltages, fuses, software resets, rebuilding the database, etc.

You might try SB UART in case there's something useful in there.
 
Recently I got a 40nm RSX, model CXD5301DGB. It's a refurb one and the seller claims its working.
I just did a ohm test for the RSX(not soldered to the board) by using my multimeter set to AUTO mode, and some readings are kinda suspicious.

Vddc: 3.8
Vddr: 1.4K
Vddiorw: 6.6K
Vddio: 5.21K
Vdda: 8.23K
PLL: 0.412M
Fbvdd: 0.425K

I know that different chip could have some slightly different readings but for my case for example the PLL is 10x smaller than what RIP-Felix's NOS 40nm chip reads, which looks weird to me. On the other hand, these readings are still reasonable because at lease they are not shorted lol.

So my question is:
1. Is this 40nm RSX reading looking good?
2. Is there any rules to categorize the wellness of a ohm reading? Like some range for each reading.

Sorry about reposting but I couldn't find any "edit" option for my previous reply. Today I went for a hiking but could't stop thinking about the RSX staff lol.
 
Last edited:
CurieOS said:
Ah. Where are the test points for that? I'm not finding much on the PS3 dev wiki for my board (COK-001).
Click to expand...
Not sure, I haven't tried it yet. @vyktormvmpay25 does it more, but on slims. I know there are pads available on the PCI port, but IDK if they are connected or disabled. I have been meaning to look into that, but haven't got to it yet.

If you try it and it works, let me know. Also, maybe victor can help, since he's done it more.
 
I found... something? maybe? I was tracing back the power line that eventually becomes the error BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS (yeah, still working on that), and eventually made my way to IC6304. Just for funsies, I started testing each of the pins for shorts to ground, with pin 2 being a direct to groun connection.

I set my meter to continuity mode, and pin 2 checks out as ground, with 0 ohms in relation to the outer edge of the board. Interestingly enough, pin 6 (which is what connects to BE RRAC), appears to be almost shorting to ground, with a resistance of 3ohms. That doesn't sound right to me... YC_RC_VDDA is also showing 3ohms to ground. It's not quite 0 ohms, but it is quite low.

Is this value supposed to be this low?
 
marciolsf said:
I found... something? maybe? I was tracing back the power line that eventually becomes the error BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS (yeah, still working on that), and eventually made my way to IC6304. Just for funsies, I started testing each of the pins for shorts to ground, with pin 2 being a direct to groun connection.

I set my meter to continuity mode, and pin 2 checks out as ground, with 0 ohms in relation to the outer edge of the board. Interestingly enough, pin 6 (which is what connects to BE RRAC), appears to be almost shorting to ground, with a resistance of 3ohms. That doesn't sound right to me... YC_RC_VDDA is also showing 3ohms to ground. It's not quite 0 ohms, but it is quite low.

Is this value supposed to be this low?
Click to expand...
Yes, VDDA is 4 ohms nominally.

Sounds like a red herring.
 
mekmitasdigoat said:
Recently I got a 40nm RSX, model CXD5301DGB. It's a refurb one and the seller claims its working.
I just did a ohm test for the RSX(not soldered to the board) by using my multimeter set to AUTO mode, and some readings are kinda suspicious.

Vddc: 3.8
Vddr: 1.4K
Vddiorw: 6.6K
Vddio: 5.21K
Vdda: 8.23K
PLL: 0.412M
Fbvdd: 0.425K

I know that different chip could have some slightly different readings but for my case for example the PLL is 10x smaller than what RIP-Felix's NOS 40nm chip reads, which looks weird to me. On the other hand, these readings are still reasonable because at lease they are not shorted lol.

So my question is:
1. Is this 40nm RSX reading looking good?
2. Is there any rules to categorize the wellness of a ohm reading? Like some range for each reading.

Sorry about reposting but I couldn't find any "edit" option for my previous reply. Today I went for a hiking but could't stop thinking about the RSX staff lol.
Click to expand...
It looks okay.

Are you planing frankenstein reanimation?
 
You must log in or register to reply here.

Similar threads

Back
Top