
as above
iphone.tvcatchup.com
7 publicly visible posts • joined 1 Mar 2010
The going theory is that the PS3 is storing some form of date in GMT, then modifying that to get whatever you see in the on-screen clock. That modification process seems to be fine; the system can take 2/28/2010, 9PM GMT, add four hours, and get 3/1/2010, 1AM random time zone.
What’s apparently wrong, as speculation goes, is when the internal GMT-tracking rolls over to 3/1. It’s either not rolling, or rolling to 2/29, at which point a system tries to add/subtract from 2/29, which it can’t do because the front-end calendar doesn’t have a 2/29/2010. Everything started to collapse around 4PM PDT, which I think is 12AM GMT.
And the PS3 launched in 2006; it’s hit four 2/28s so far. 2007 and 2009 were odd-numbered years; 2008 was an even, and a leap year. 2010 is the first even non-leap-year the system’s been around for. If some sort of base-level math is choking on itself, it may have ruled out the odd 2007 and 2009 successfully, but is convinced the even 2010 is a leap year (this part I’m less sure of, but is why leap year could theoretically come into play at some point).
Read more: http://www.ps3news.com/forums/ps3-online-news/psn-crashed-8001050f-hardware-failure-ps3-consoles-110004-8.html#ixzz0gwTtlc0v
just heard from a ps3 dev pal of mine and apparently this effected even the ps3 test units (phat)
and to quote..
START QUOTE
he removed the RTC battery for about 10 minutes as I suggested earlier, stuck it back in and he is now back up and running, on PSN and everything!
So, if you guys want to give it a try and your box has been opened / out of warranty - it should work!
I'd just, for now, set it to today / tomorrow's (3/1/2010) date, to be safe!
END QUOTE