Eurogamer's resident supernerd at Digital Foundry has weighed in on yesterday's global PS3 meltdown, cleverly dubbed ApocalyPS3. While early reports seemed to indicate PlayStation Network was at fault – "playstation network down" was a top Google search term on Sunday and Sony itself continues to pin the blame squarely on PSN – it became increasingly clear that the issue was unrelated to the console's internet connectivity and instead related to the console's internal clock. If this sounds suspiciously similar to the Z2K bug that suddenly bricked thousands (dozens?) of 30GB Zune players in 2008, it's because both the PS3 and Zune share an ARM CPU chip, says DF. This is presumably the same Freescale processor blamed for Z2K, a chip that happens to have a known problem dealing with leap years.
According to "unofficial community-compiled lists" cited by Digital Foundry, eight out of the eleven "fat" PS3 SKUs were affected by the faulty chip, easily totaling millions of units. If the problem wasn't resolved quietly (perhaps too quietly, considering the dearth of updates on the company's Twitter feed) and relatively quickly by the inevitable march of time itself, Sony would have been tasked with repairing millions of affected consoles; a burden exacerbated by said console's inability to connect to the PlayStation Network.
Lucky for us, and infinitely more so for Sony, at 0000 GMT yesterday, PS3s the world over suddenly figured out what day it was and everything went back to normal. All that's left to do is hope that Sony issues a patch to prevent the next apocalypse. (Isn't that the one in 2012?)
Reader Comments (132)
Posted: Mar 2nd 2010 4:49PM googleadam said
@ Captain Planet [Planeteer | Power of Captain Planet]
Double Tap Rule in effect...
Reply
Double Tap Rule in effect...
Posted: Mar 2nd 2010 2:28PM Jack Tretton said
Leno? Clearly, martinman possesses the sparkling wit inherent in any video game blogger.
Reply
Posted: Mar 2nd 2010 2:58PM Captain Planet Planeteer Power said
I think he IS Jay Leno. I yawned three times while reading his post.
Reply
Posted: Mar 2nd 2010 1:47PM Spunky Monkey 190906 said
Yay, the world has returned to normality, no longer will I look at the clock and think, when will you start again, no longer with the hand of time remain still no longer will I talk jibberish :D
Reply
Posted: Mar 2nd 2010 4:33PM mikeburnfire said
Ironically, I was playing A Crack in Time when my Playstation started time traveling. I thought the game was pulling some kind of Psyco-Mantis-type mind game.
Thank God I wasn't playing Braid.
Reply
Thank God I wasn't playing Braid.
Posted: Mar 2nd 2010 2:19PM (Unverified) said
my guess would be it felt even years were leap years.....
Reply
Posted: Mar 2nd 2010 5:06PM FredFredrickson said
Not to mention, the whole Zune thing turned out to be a programming error, not a hardware flaw.
Reply
Posted: Mar 2nd 2010 1:55PM spin cycle said
This chip existed in the PS3 in 2008 and there were no issues then.
It's a software bug that was introduced some time after that.
Let's not get off track and blame a chip here, this is a software failure. Sony needs to get on the stick a bit more. Like do some testing of their code next time!
Reply
It's a software bug that was introduced some time after that.
Let's not get off track and blame a chip here, this is a software failure. Sony needs to get on the stick a bit more. Like do some testing of their code next time!
Posted: Mar 2nd 2010 1:57PM RyanS said
If its a problem of the chip, then chances are it might not be patchable. Some of these chips arent reprogrammable with a firmware update.
If the Zune had the problem, then so would the PS3 and any other device out there with this chip in it.
The only solution is to phase out this chip ASAP and never look back.
Reply
If the Zune had the problem, then so would the PS3 and any other device out there with this chip in it.
The only solution is to phase out this chip ASAP and never look back.
Posted: Mar 2nd 2010 2:05PM copa said
"This chip existed in the PS3 in 2008 and there were no issues then.
It's a software bug that was introduced some time after that."
That makes absolutely no sense. We know there was a bug relative to leap-year calculation in the year 2010.
There is no way to conclude this particular bug would have also caused a problem in 2008.
Reply
It's a software bug that was introduced some time after that."
That makes absolutely no sense. We know there was a bug relative to leap-year calculation in the year 2010.
There is no way to conclude this particular bug would have also caused a problem in 2008.
Posted: Mar 2nd 2010 2:36PM McBrick said
Zune bug happened on New Year's Eve 2008, IIRC, because the logic counted the number of days in the calendar year and wasn't equipped to handle day 366.
We got something that "smells" the same - the PS3 chip thought it was Feb. 29 and something else - another chip in the unit, the network, both, or something else entirely - thought it was (correctly) 3/01, hence the freakout.
Nicest thing for Sony is all they had to do was tell people not to use the unit and wait. Easiest fix ever.
Reply
We got something that "smells" the same - the PS3 chip thought it was Feb. 29 and something else - another chip in the unit, the network, both, or something else entirely - thought it was (correctly) 3/01, hence the freakout.
Nicest thing for Sony is all they had to do was tell people not to use the unit and wait. Easiest fix ever.
Posted: Mar 2nd 2010 2:43PM Lekko said
While they might not be able to patch the error from the chip giving the wrong date, they can at least patch how the PS3 OS handles incorrect date errors. That is well within their control, and I imagine that it will be in the next firmware update along with a few other miscellaneous odds and ends bug patches and fixes.
Reply
Posted: Mar 2nd 2010 3:46PM Mal F4cti0n said
The chip probably has a line of code that is wrong.
It was probably written to recognize any even number year as a leap yeat, that is why the problem didn't exist in 2009. This will come up again in 2012....un, no, cuz that WILL be a leap year. This problem will come up again in 2014.
Reply
It was probably written to recognize any even number year as a leap yeat, that is why the problem didn't exist in 2009. This will come up again in 2012....un, no, cuz that WILL be a leap year. This problem will come up again in 2014.
Posted: Mar 2nd 2010 4:17PM spin cycle said
Even if there is a bug in the chip, it's far from the first chip to have bugs in it. Software workarounds are very common.
This is a software error on Sony's part.
macnbc and others who don't remember the Zune problem:
The Zune problem happened on Dec 1, 2009, not Feb 29, 2008. And the source of the error was found, it's in the reference driver for the chip. The code is out there on the net. This is a software problem.
Besides, if you say the problem is related to non-leap years, why didn't it happen on Mar 1, 2009?
Start making sense. New code must have went in with the bug in it.
Reply
This is a software error on Sony's part.
macnbc and others who don't remember the Zune problem:
The Zune problem happened on Dec 1, 2009, not Feb 29, 2008. And the source of the error was found, it's in the reference driver for the chip. The code is out there on the net. This is a software problem.
Besides, if you say the problem is related to non-leap years, why didn't it happen on Mar 1, 2009?
Start making sense. New code must have went in with the bug in it.
Posted: Mar 2nd 2010 2:00PM Chris DPSN AggieCEO XBLThe Aggi said
the Zune30's got patch to fix it...as did the other devices that use the SAME chip....
Reply
Posted: Mar 2nd 2010 1:50PM (Unverified) said
It only does everything......
Except figure out it's a leap year apparently.
Reply
Except figure out it's a leap year apparently.
Posted: Mar 2nd 2010 3:01PM Captain Planet Planeteer Power said
CAPS LOCK NOT BROKEN I JUST WANTED TO SOUND SMART AND SAY SOMETHING WITH THE WORD "LEAP YEAR" IN IT BUT COULDN'T
Reply
Sorry, you must be logged in to leave a comment.
Featured Stories
The most popular posts
in the last 7 days
- Vita 'UMD Passport' won't be offered in US 220 comments
- Kingdoms of Amalur: Reckoning review: A tempting fate 153 comments
- David Jaffe leaves Eat Sleep Play, layoffs hit developer [Update] 108 comments
- Don't call it a remake: Final Fantasy X is a 'remaster,' to be clear 95 comments
- Battleship movie adapted into FPS by Double Helix 93 comments











