Any one get bit by the PlayStation network outage?
 

Obviously it effected a lot of folks. It was interesting to read about those who were an weren't affected. Since we already kinda know what the problem was, I'm curious to know what you guys think.


Links for those who are giving me the wtf look..

PS3s Suffering From Global Network Lockdown [UPDATE 7] - Error: 8001050F - Kotaku

PlayStation.Blog : The official PlayStation blog for all of your PLAYSTATION 3, PlayStation 2 and PSP news.

I read about it, didn't affect me since I have a slim, sold my "fat" a while back because it was when I didn't have a tv that warranted owning a hi-def gaming console.

Sounds like it was a leap year bug in the SYSCON chip's firmware. Guess it should be working now from what I'm reading.

Yeah they got it working. I still have my 60gb model :hearts: backwards compatibility. It kinda sucked because I started up my PS3 last night to download the God of War III demo and was greeted with the error. At least they got it fixed and it doesn't appear that I lost anything. Although I did hear a few reports of people losing game save data. :eek:

yeah problem is, they didn't really "fix" anything.

PS3. It only does everything. Including fix itself.

I have the slim so I didn't have any problems either.

Yeah that's a problem. Clearly they have an issue with their code and their solution is to "wait 24 hours" for the calendar to correct itself. Seems kinda of disingenuous to me. Wonder if they actually fix it in the next firmware upgrade.

If this is Sony's biggest bug with the PS3 then I'm happy. At least it's not an RROD.

what he said^

YLOD and RROD can fuck off and die

well I'm wondering just how simple of a fix it is. They're either using a different revision of the syscon chip in the slims that don't have that firmware bug or it's just a more current version.

still I think even if you knew anything about programming, it seems like one of those things you'd want to carefully program since firmware is a one shot pony. If it messed up, you brick the ps3. permadeath is a lot more serious than a 24 hour "oops"

So they'd have to write the code to identify the chip on each unique revision of the ps3, even the slim, code the slim to NOT run the code and still tell the slim that the patch was successful, lol.


I dunno deploying an update to 40 million ps3 owners is a risk, it takes a lot of QA. I'm sure they're aware of it now but it's not something I would have expected them to pop out in 24 hours.

The whole apocolyPS3 thing could have been a lot lot worse than it really was, haha.

Assuming they did use a different revision of the syscon chip then it should have an identifier. All the firmware programmers would have to do is add some kind of check into the code (if version=1.0 then upgrade) Assuming 1.0 is the id of the older syscon chip. Granted that's vastly simplified but it shouldn't be all that difficult.

It's funny that you mention RROD. I've actually been debating about tearing into my 60GB to replace the thermal grease with something of a better quality, but I haven't worked up the nerve yet.

http://www.cad-comic.com/comics/cad/20100303.jpg

Nothing to add this sorry, just had to post this comic.

/semithreadjack

But it fits with all the different names that cropped up.

And :lol: at the comic.

i hate CAD.