Anyone suffered a Kernel Panic shutdown?

[mikelj]

Just interested if anyone has suffered a shutdown of their 4s due to a kernel panic? Had one happen today whilst my 4s was in standby resulting in the phone powering down and being completely unresponsive to power switch and dock connector power; only holding the power and home button down together brought it back to life.

I assume that this could either be a software or hardware issue - guess I'll just have to see if it happens again before contacting Apple.

Crash report for those interested

Incident Identifier: 61708CF2-E843-4517-A42C-534CC5ED5616
CrashReporter Key: b6c0e9bb5add82b6ab3abf75b222ba95c0a91471
Hardware Model: iPhone4,1
Date/Time: 2011-11-29 15:37:48.117 +0000
OS Version: iPhone OS 5.0.1 (9A405)

panic(cpu 0 caller 0x80075700): hw_lock_lock(): lock (0x814F3640)

Debugger message: panic
OS version: 9A405
Kernel version: Darwin Kernel Version 11.0.0: Tue Nov 1 20:34:16 PDT 2011; root:xnu-1878.4.46~1/RELEASE_ARM_S5L8940X
iBoot version: iBoot-1219.43.32
secure boot?: YES
Paniclog version: 1
Epoch Time: sec usec
Boot : 0x4ed4730d 0x00000000
Sleep : 0x4ed4f934 0x000ab373
Wake : 0x4ed4f936 0x00000009
Calendar: 0x4ed4f955 0x00004a8a

Task 0xc085ed20: 9687 pages, 130 threads: pid 0: kernel_task
thread 0xc121cca0
kernel backtrace: cfdb3d50
lr: 0x8007bccb fp: 0xcfdb3d7c
lr: 0x8007c2cf fp: 0xcfdb3dac
lr: 0x80016391 fp: 0xcfdb3dc4
lr: 0x80075700 fp: 0xcfdb3e04
lr: 0x8021cfb5 fp: 0xcfdb3e30
lr: 0x80377285 fp: 0xcfdb3e40
lr: 0x8083fea5 fp: 0xcfdb3e5c
lr: 0x80375a93 fp: 0xcfdb3e78
lr: 0x808e7749 fp: 0xcfdb3e8c
lr: 0x808e7bcb fp: 0xcfdb3e9c
lr: 0x808b4731 fp: 0xcfdb3eb0
lr: 0x808b50e3 fp: 0xcfdb3ec4
lr: 0x8021d039 fp: 0xcfdb3ef0
lr: 0x808b5037 fp: 0xcfdb3f08
lr: 0x80214b9f fp: 0xcfdb3f60
lr: 0x802110d9 fp: 0xcfdb3f78
lr: 0x8002c4bf fp: 0xcfdb3fa8
lr: 0x8007a3bc fp: 0x00000000

Task 0xc085eac0: 216 pages, 3 threads: pid 1: launchd
Task 0xc085e600: 636 pages, 6 threads: pid 12: UserEventAgent
Task 0xc085e140: 257 pages, 3 threads: pid 13: notifyd
Task 0xc085e3a0: 541 pages, 9 threads: pid 14: configd
Task 0xc085dee0: 9522 pages, 18 threads: pid 15: SpringBoard
Task 0xc085dc80: 152 pages, 4 threads: pid 16: syslogd
Task 0xc085da20: 1928 pages, 14 threads: pid 17: CommCenter
Task 0xc085ce40: 560 pages, 2 threads: pid 22: lockdownd
Task 0xc085c980: 280 pages, 2 threads: pid 24: powerd
Task 0xc085c000: 1626 pages, 14 threads: pid 28: locationd
Task 0xc0eead20: 528 pages, 4 threads: pid 29: wifid
Task 0xc0eea860: 608 pages, 7 threads: pid 31: ubd
Task 0xc0ee8720: 5816 pages, 26 threads: pid 45: mediaserverd
Task 0xc0ee84c0: 400 pages, 3 threads: pid 46: mediaremoted
Task 0xc0ee8260: 382 pages, 3 threads: pid 47: mDNSResponder
Task 0xc0f43d20: 1794 pages, 6 threads: pid 49: imagent
Task 0xc0f43ac0: 851 pages, 5 threads: pid 50: iapd
Task 0xc0f43600: 205 pages, 4 threads: pid 52: fseventsd
Task 0xc0f433a0: 946 pages, 1 threads: pid 53: fairplayd.N94
Task 0xc0f43140: 1365 pages, 5 threads: pid 54: dataaccessd
Task 0xc0f42a20: 413 pages, 3 threads: pid 57: awdd
Task 0xc0f42300: 472 pages, 3 threads: pid 60: apsd
Task 0xc0f420a0: 520 pages, 2 threads: pid 61: aggregated
Task 0xc0f41260: 467 pages, 2 threads: pid 67: BTServer
Task 0xc0f41000: 799 pages, 4 threads: pid 68: aosnotifyd
Task 0xc1032600: 255 pages, 2 threa

 

[gkpm]

Just interested if anyone has suffered a shutdown of their 4s due to a kernel panic? Had one happen today whilst my 4s was in standby resulting in the phone powering down and being completely unresponsive to power switch and dock connector power; only holding the power and home button down together brought it back to life.

I've seen other reports like this, it's related to version 5.0.1.

The new update should be out any moment now....

 

[mikelj]

Thanks, glad it's not hardware, this is the forth 4s I'm on (don't ask!).

 

[muffins]

My second 4S did this but no crash report. Now on my third due to intermittent earpiece problem.

 

[Stinja]

I get/got them frequently, often at least one per charge cycle.

Typically they're called (in Diagnostic & Usage) "<date>-<time>.panic.plist" and "ResetCounter-<date>-<time>" and go together.

I did find turning off my wifi connection and only using 3G seems to help alot, as they were 2-3 times a day before. Gut feeling is its due to low wifi signal, or moving out of range of any registered wifi networks, and then it's trying to reconnect to something-anything furiously, possibly overheating (iphone is always warm after a crash), and then crashes

A workmate with a 3Gs(?), who was completely fine pre iOS 5.x, also gets crashes, but not as many as me i think.

Battery is fine, but i'd like this panic-crashing fixed, then i'd be much happier with the iP4s

 

[acf]

I had this on my first 2 4S's and had them both swapped out at the Apple Store. It was happening about 10 times a day.

3rd one is running fine.

 

[mikelj]

Well, I've gone through a re-charge cycle since my crash (went down to 2% before I charged it) and so far everything is ok. I'm guessing it was s/w related; there was no excessive heat from the phone like other people had observed.

 

[muffins]

I was composing an email today when I received a text, boom phone crashed.

 

[Stinja]

Anyone had a crash since 5.1?

I'm monitoring, but seems better in the last few days...

 

[bpsmith]

Nope. Not on iPhone 4, 4S or iPad 1.

 

[acf]

Not had a crash since I got my 3rd 4S. Was stable after I got that one, no probs at all.

How you doing Stinj mate ? Got yer Vita yet ?

 

[Stinja]

So since then ^^^ i got fed up, and took my iP4s thru multiple telephone calls, who did the usual script, then eventually into the Regent Street Apple store. After a 33 minute wait (after my "Booked Appointment") the "Genius" said it needed a replacement, and gave me one there.

It seems MUCH more stable, so well worth jumping thru hoops if you think you're getting an unusual amount of shutdowns.

 

[acf]

So since then ^^^ i got fed up, and took my iP4s thru multiple telephone calls, who did the usual script, then eventually into the Regent Street Apple store. After a 33 minute wait (after my "Booked Appointment") the "Genius" said it needed a replacement, and gave me one there.

It seems MUCH more stable, so well worth jumping thru hoops if you think you're getting an unusual amount of shutdowns.

Holy cow !! Were you still having issues up to today ?? Thought I took long sorting it with half a dozen genius visits in a week.

 

[Stinja]

I've been busy, and getting time to get to the store was not so easy. Also it was only occasional until 5.0.1, when it would crash twice a week at least...

Besides which, the longer one waits, but before a year since purchase, the newer your phone is