12 Replies Latest reply: Oct 12, 2009 11:20 AM by AndreasFi
AndreasFi Level 1 Level 1 (0 points)
Having problems with suddenly reboots after 3.1 upgrade. My phone worked perfectly on 3.0.1.
Have upgraded to 3.1.2, but the phone still reboot. I wanna go back to 3.0.1 but this is not possible on 3GS!?

Have found the Phones panic logs on my mac. They report the following:

Incident Identifier: BBAE20A0-DD26-49E4-848C-5A3918CDA0B6
CrashReporter Key: 643158dd912251f1f91b7316ed2338532cc1cb31
Date/Time: 2009-09-11 02:23:31.920 +0200
OS Version: iPhone OS 3.1 (7C144)

panic(cpu 0 caller 0xc006abe8): "L1 Dcache parity error"@/SourceCache/xnu/xnu-1357.5.30/osfmk/arm/trap.c:329
Debugger message: panic
OS version: 7C144
Kernel version: Darwin Kernel Version 10.0.0d3: Fri Aug 14 13:23:32 PDT 2009; root:xnu-1357.5.30~2/RELEASEARMS5L8920X
iBoot version: iBoot-636.65
secure boot?: YES
Paniclog version: 1

Yesterday, it rebooted 11 times!!! Most of the times when using iPod. But also using Spotify. It even rebooted in my pocket running no apps.

It have also rebooted in the middle of a phonecall. Of course an important call....

Please Apple, let me downgrade to 3.0.1!!!!

iPhone 3GS, Other OS, iPhone 3.1.2
  • wjosten Level 10 Level 10 (93,685 points)
    Put the phone in DFU mode.

    http://www.iclarified.com/entry/index.php?enid=1034

    * Plug the phone into the computer with iTunes running.
    * Press the power button (aka sleep/wake button, the one in the upper right corner) and then right away press the home button while still holding the power button. Hold both buttons down for 10 seconds.
    * After the 10 seconds, release the power button but keep holding the home button.


    If it works, then you should see a pop-up indicating that iTunes has detected a phone in recovery mode (in Windows, there's also a sound effect from the OS typically to tell you a device has been recognized). You can let go of the home button when you see this. If you don't get this indication, then try again.

    Once you get the popup, then click the okay button and then restore the iPhone from your backup.
  • AndreasFi Level 1 Level 1 (0 points)
    Have tried restoring from DFU many times. Also tried restoring as new iPhone and syncing with iTunes after. But no go. Still reboots. Do not Think it is a hw issue, as it worked fine before 3.1.
  • wjosten Level 10 Level 10 (93,685 points)
    If you've done DFU mode, then yes.
  • wjosten Level 10 Level 10 (93,685 points)
    This also occurs if you've "jailbroken" your phone. Please tell me you havn't done that?
  • AndreasFi Level 1 Level 1 (0 points)
    Nope. No jailbrake here.
    But as i said earlier, this never happened on 3.0.1
    i have the panic logs to show it. Started right after 3.1.
    Seems strange to me that the hw should brake almost at the same time as the upgrade was applied.
  • wjosten Level 10 Level 10 (93,685 points)
    Well, if you've restored as new...
    Long shot, but try this, find the .ipsw file on you computer, delete it. Re-download & try a restore again. You've got nothing to lose, and there is a chance the original file got corrupted. Again, it's a long shot, but you never know...

    Message was edited by: wjosten
  • AndreasFi Level 1 Level 1 (0 points)
    Tried dowloading again. Also, i'm not sure I really got it into DFU before. Did like this: Shutdown and holding homebutton while pluging in USB. This was maybe recovery mode, not DFU???

    THIS time I am sure it is in DFU-mode. Restoring as new and just syncing with iTunes.

    Crossing my fingers
  • wjosten Level 10 Level 10 (93,685 points)
    For most people, it takes a couple of trys to get into DFU mode. Watch the video in the link I provided.

    In DFU mode, the iPhone screen backlight is not even on and the display is blank. If you have anything on your display you are not in DFU mode.

    Message was edited by: wjosten

    Message was edited by: wjosten
  • Jason L Community Specialists Community Specialists (10,630 points)
    AndreasFi wrote:
    Having problems with suddenly reboots after 3.1 upgrade. My phone worked perfectly on 3.0.1.
    Have upgraded to 3.1.2, but the phone still reboot. I wanna go back to 3.0.1 but this is not possible on 3GS!?

    Have found the Phones panic logs on my mac. They report the following:

    Incident Identifier: BBAE20A0-DD26-49E4-848C-5A3918CDA0B6
    CrashReporter Key: 643158dd912251f1f91b7316ed2338532cc1cb31
    Date/Time: 2009-09-11 02:23:31.920 +0200
    OS Version: iPhone OS 3.1 (7C144)

    Try updating the iPhone to iPhone OS 3.1.2 again, as described here: http://support.apple.com/kb/HT1414

    If you are using any accessories with the iPhone, try testing without them.

    You can also try setting the iPhone up as a new phone. This article: http://support.apple.com/kb/HT3828 provides more details about setting your iPhone up as a new device.

    Try contacting the cellular service provider if the issues persist. This article: http://support.apple.com/kb/HT1937 provides contact information and links for many cellular service providers.

    -Jason
  • AndreasFi Level 1 Level 1 (0 points)
    OK

    Giving up.
    Downloaded FW again, restored in DFU-mode, setting up as new phone, synced apps and music from iTunes.

    Then, when I was filling in info. for connecting to my Exchange Server, the darn thing rebooted again!!! AAARRGGGHHH!!!

    But as i said before, would really like to try 3.0.1, because I did not have ANY trouble before upgrading to 3.1.

    Panic:
    Incident Identifier: 14750935-34DF-46DA-868F-16D39BD5E549
    CrashReporter Key: 643158dd912251f1f91b7316ed2338532cc1cb31
    Date/Time: 2009-10-12 15:51:04.145 +0200
    OS Version: iPhone OS 3.1.2 (7D11)

    panic(cpu 0 caller 0xc006abe8): "L1 Dcache parity error"@/SourceCache/xnu/xnu-1357.5.30/osfmk/arm/trap.c:329
    Debugger message: panic
    OS version: 7D11
    Kernel version: Darwin Kernel Version 10.0.0d3: Fri Sep 25 23:35:35 PDT 2009; root:xnu-1357.5.30~3/RELEASEARMS5L8920X
    iBoot version: iBoot-636.66
    secure boot?: YES
    Paniclog version: 1
    Task 0xc0ba7ce8: 6599 pages, 86 threads: pid 0: kernel_task
    Task 0xc0ba7b10: 153 pages, 3 threads: pid 1: launchd
    Task 0xc0ba71d8: 107 pages, 4 threads: pid 14: syslogd
    Task 0xc0ba7000: 930 pages, 3 threads: pid 16: lockdownd
    Task 0xc4a4bce8: 3300 pages, 16 threads: pid 17: mediaserverd
    Task 0xc4a4bb10: 220 pages, 2 threads: pid 18: mDNSResponder
    Task 0xc4a4b760: 407 pages, 3 threads: pid 20: IQAgent
    Task 0xc4a4b588: 313 pages, 1 threads: pid 21: fairplayd
    Task 0xc4a4b3b0: 833 pages, 5 threads: pid 22: dataaccessd
    Task 0xc4a4b1d8: 542 pages, 12 threads: pid 23: configd
    Task 0xc498bce8: 4834 pages, 12 threads: pid 25: SpringBoard
    thread 0xe042fccc
    kernel backtrace: ed307c7c
    lr: 0xc0068b93 fp: 0xed307ca8
    lr: 0xc0068dc7 fp: 0xed307cbc
    lr: 0xc001b829 fp: 0xed307ce4
    lr: 0xc006abe8 fp: 0xed307fa8
    lr: 0xc006638c fp: 0x2fffea14
    user state:
    r0: 0x002c8ad0 r1: 0xfff00000 r2: 0x00000000 r3: 0x00200000
    r4: 0x0000c8ad r5: 0x00000000 r6: 0x00129500 r7: 0x2fffea14
    r8: 0x002c8ad0 r9: 0x00002b80 r10: 0x00126000 r11: 0x0002c8ad
    r12: 0x383bd808 sp: 0x2fffe97c lr: 0x319aae38 pc: 0x319acc04
    cpsr: 0x20000010 fsr: 0x00000c08 far: 0x319acc4c
    user backtrace: 2fffea14
    lr: 0x319aab37 fp: 0x2fffea30
    lr: 0x32516523 fp: 0x2fffea38
    lr: 0x3254cbf9 fp: 0x2fffea44
    lr: 0x3254cb95 fp: 0x2fffea4c
    lr: 0x32518503 fp: 0x2fffea7c
    lr: 0x325493e1 fp: 0x2fffeab0
    lr: 0x325492c3 fp: 0x2fffeac0
    lr: 0x3251c111 fp: 0x2ffff3e0
    lr: 0x325626b7 fp: 0x2ffff400
    lr: 0x31437d09 fp: 0x2ffff414
    lr: 0x30156011 fp: 0x2ffff46c
    lr: 0x3015580d fp: 0x2ffff488
    lr: 0x301594a1 fp: 0x2ffff49c
    lr: 0x3015942f fp: 0x2ffff4b8
    lr: 0x30159213 fp: 0x2ffff4d4
    lr: 0x000ac0b9 fp: 0x2ffff4f0
    lr: 0x000abf93 fp: 0x2ffff4fc
    lr: 0x000ac0fb fp: 0x2ffff508
    lr: 0x31438bfd fp: 0x2ffff5c4
    lr: 0x32561af9 fp: 0x2ffff648
    lr: 0x314367fb fp: 0x2ffff66c
    lr: 0x0000ddeb fp: 0x2ffff6ac
    lr: 0x00004c75 fp: 0x2ffff6b8
    lr: 0x32b67c67 fp: 0x2ffff6f4
    lr: 0x32b9edd5 fp: 0x2ffff6fc
    lr: 0x32a105e9 fp: 0x2ffff720
    lr: 0x32520e51 fp: 0x2ffff740
    lr: 0x32567c2d fp: 0x2ffffc50
    lr: 0x3256735d fp: 0x2ffffc6c
    lr: 0x32912cbf fp: 0x2ffffc7c
    lr: 0x32912d6b fp: 0x2ffffc90
    lr: 0x32b6276f fp: 0x2ffffcac
    lr: 0x32b61473 fp: 0x2ffffd04
    lr: 0x00003b25 fp: 0x2ffffda0
    lr: 0x0000382c fp: 0x00000000

    Task 0xc498b588: 600 pages, 10 threads: pid 29: CommCenter
    Task 0xc498b3b0: 627 pages, 5 threads: pid 30: BTServer
    Task 0xc498b1d8: 485 pages, 3 threads: pid 31: aosnotifyd
    Task 0xc498b000: 120 pages, 2 threads: pid 32: notifyd
    Task 0xc498b760: 151 pages, 3 threads: pid 42: SCHelper
    Task 0xc0ba73b0: 318 pages, 3 threads: pid 47: apsd
    Task 0xc0ba7938: 1802 pages, 2 threads: pid 49: MobilePhone
    Task 0xc0ba7760: 6046 pages, 7 threads: pid 50: MobileMail
    Task 0xc50cf938: 2646 pages, 4 threads: pid 52: MobileMusicPlaye
    Task 0xc0ba7588: 8138 pages, 6 threads: pid 124: MobileSafari
    Task 0xc498bb10: 571 pages, 6 threads: pid 170: iapd

    Message was edited by: AndreasFi
  • stoneymonster Level 1 Level 1 (5 points)
    A L1 dcache parity error is a hardware fault on your cpu, it's likely you have a bad SRAM. 3.1 probably exercises the CPU and/or the cache in a slightly different enough way that it exhibits this problem more often for you. I'd take it up with a Genius or Applecare....
  • AndreasFi Level 1 Level 1 (0 points)
    Yes, that makes sense....
    Google'd the "L1 cache parity error" in general...

    The worst thing, is that I have to send in my phone for "diagnostics" before I get a new one. This will surely take several days. And I have already spent weeks doing diagnostics myself