PS3 PSN login error

[andrewyhy]

I'm so glad to see the date and time can finally sync with the internet this afternoon when I got home. By logging in PSN, my trophies are back once I fire up the game and doing the synchronize thing. Hooray!

 

[Horde_R35]

I'm so glad to see the date and time can finally sync with the internet this afternoon when I got home. By logging in PSN, my trophies are back once I fire up the game and doing the synchronize thing. Hooray!

Race???!!

 

[Coxis]

I have no doubt that after GMT time reached March 2nd the fat PS3s started connecting again (I tried it myself at 6:10 PM CST 00:10 AM GMT). Considering that so far it looks like they couldn't fix it themselves and 24 hours later when the date changed things went back to normal, will this happen again next year? Or any other subsequent year the PS3 thinks it's a leap year?

 

[BlacqueJacques]

I connected last nite to race a bit. Was not always matching and slow, but working , and then a few races later seemed normal.

See ya on the track!

 

[Han_the_Dragon]

I have no doubt that after GMT time reached March 2nd the fat PS3s started connecting again (I tried it myself at 6:10 PM CST 00:10 AM GMT). Considering that so far it looks like they couldn't fix it themselves and 24 hours later when the date changed things went back to normal, will this happen again next year? Or any other subsequent year the PS3 thinks it's a leap year?

If nothing is done is to expect this to happen by 28th February 2014 (since the internal clock now is 24 hours behind the real time), but by that time Sony should already had done something about it, that is if there's still some pre CECHL machines that work... since the CECHL model were the oldest ones to be imune to this..

 

[thefraggle]

If nothing is done is to expect this to happen by 28th February 2014 (since the internal clock now is 24 hours behind the real time), but by that time Sony should already had done something about it, that is if there's still some pre CECHL machines that work... since the CECHL model were the oldest ones to be imune to this..

We could very well have the PS4 by then

 

[yeti]

BTW - the problem appears to be that the PS3 thought that 2010 was 2016...

Both binary and BCD encode the numbers 0-9 as 0x00 - 0x09. But BCD encodes the number 10 as 0x10, whereas binary encodes the number 10 as 0x0A; 0x10 interpreted as a binary encoding represents the number 16. For example, because the SMS protocol uses BCD for dates, some mobile phone software incorrectly reported dates of SMSes as 2016 instead of 2010.

And some more interesting news...

The typical Unix timestamp (time_t) stores a date and time as a 32-bit signed integer number representing, roughly speaking, the number of seconds since January 1, 1970; in 2038, this number will roll over (exceed 32 bits), causing the Year 2038 problem (also known as Unix Millennium bug, or Y2K38). To solve this problem, many systems and languages have switched to a 64-bit version, or supplied alternatives which are 64-bit.

So will it happen in 2 years time...

Yes - at the moment it appears that the Bus chip thinks that we are in 2016... but the actual PS3 thinks that we are in 2010... but because the bus chip is reporting an illegal date - the PS3 chokes.

Last year 2009 would've been fine...

So - In 2 years time it's highly possible that the Bus thinks that it will be 2018 (non-leap year) - represented as 12 or 0C. - However - it won't cause an error because the front bus will report the date as 1/3... PSN will dislike you though I guess!

Either way - a firmware update is definitely required from Sony.

C.

PS - it's also possible that if you have "update time automagically" enabled - then the bus chip will dislike the updates that the PSN sends down - as they will be for an invalid date (29/2/2018) - and could cause the reverse of this error.

 

[VEXD]

What on earth could Sony do?

"Oh yeah, we accidentally sold you all a product that was going to fail on the 1st of March 2010, and we didn't realise... you'd better sue us now."

Or

"Oh yeah, we purposefully sold you all a product that was going to fail on the 1st of March 2010, and now you'd better sue us."

Owning up to the in-built error opens up all sorts of legal doors for consumers, surely, yet denying prior knowledge, then submitting a 'fix' after the event sort of covers their bax? Right?

Leap year bug or no, the fact is, if it comes back in 2014, the fatties will all have died from the YLOD by then, so who cares. Buy a slim, keep up with the cool kids.

👍

 

[ryanVAMPIRATE]

yeah so i was not so patient with the whole situation and i defiantly reformatted my system didn't realize i was not the only one should of got on here and looked i guess. i did get to save most of my games to a usb drive but not all and kinda pissed that i will have to restart some games. To find out it fixed it self a day later..... Needless to say i was piss about my ps3 twice with in 24 hrs lol.

 

[Eric Demory]

Just to have everyone clear just in case any of you are wondering........ PS has fixed this whole issue.

 

[Digital-Nitrate]

Needless to say i was piss about my ps3 twice and pissed at myself for not taking a moment to check Sony's official website, or Sony's official PS3 forum, or the official PS3 Support Site, or the official PS3 Blog, or the official PlayStation Twitter, or even a simple Google search, not to mention check this GTP forum, before taking any unnecessary action that would not only take time but also possibly lose data - with in 24 hrs lol.

Fixed.

In the future though, you may want to follow Sony's recommendation as stated in the PS3 user guide and tech support, that before you reformat your system, to first run the back-up utility program which will not only save all your content on your HDD, but will restore all of it as long as it's on the same PS3 and not restored to a different machine.

 

[Coxis]

Just to have everyone clear just in case any of you are wondering........ PS has fixed this whole issue.

Actually they just waited 24 hours until GMT reached March 2nd. By then there was no conflict between our console's date and the server's so everything started working again.

 

[Eric.]

So I guess it tried setting the internal GMT date/clock to March 1, 2010, which is a valid date, connected to the time server and saw that the time and date was wrong, and corrected it to March 2? I just don't get why setting the time manually couldn't fix this. The internal system clock must always set itself to the network's time and then allow you to tweak what is displayed as a transformation of its internal (real, GMT) time.

 

[Kaden101]

So I guess it tried setting the internal GMT date/clock to March 1, 2010, which is a valid date, connected to the time server and saw that the time and date was wrong, and corrected it to March 2? I just don't get why setting the time manually couldn't fix this. The internal system clock must always set itself to the network's time and then allow you to tweak what is displayed as a transformation of its internal (real, GMT) time.

I may be wrong, but I'm thinking that when you set the clock manually, you're just setting the OS (XMB) clock. The internal battery backed up clock was still seeing 29th Feb which obviously didn't compute as it couldn't find the 29th at all on either the OS calendar or PSN calendar. As soon as it tripped to March the 2nd, the internal clocked tripped to March 1st, & hey presto, suddenly it could find required dates on the OS & network, & even though they were incorrect, it could at least compute these dates.

Could explain why disconnecting the battery fixed it. The internal clock lost it's information, & the first time you turn on the console it asks for the time & date, & then maybe it took the information from the OS.

or something not even close to that. It's just a theory.

 

[yeti]

Just to have everyone clear just in case any of you are wondering........ PS has fixed this whole issue.

No it/they didn't.

C.