PDA

View Full Version : Kernel panic what is it exactly?



mctext
16th February 2008, 11:51 PM
At work on Friday (15 Feb) , I had to go out of the office for a couple of meetings.
Both times I came back, my MB wouldn't return from auto-sleep mode.
Went to a hard restart (on both occasions) and got a message saying there was an auto shut down with the option to create a report / send report to Apple.
The first report (below) seems to indicate a kernel panic.
Not sure what a kernel panic is and/or why I should be worried.
Now I'm back and working from home, all seems to be well *touching wood here*.
Enlightenment on what's happening?


mct
===========
panic(cpu 1 caller 0x001A49CB): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0xeeeeeeee, CR3: 0x00e69000, CR4: 0x000006e0
EAX: 0xeeeeeeee, EBX: 0x0178bc60, ECX: 0x03efe718, EDX: 0x0178bc68
CR2: 0xeeeeeeee, EBP: 0x25203c38, ESI: 0x043faaa4, EDI: 0x040c14a8
EFL: 0x00010202, EIP: 0x00141502, CS: 0x00000008, DS: 0x040b0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x252039e8 : 0x128d0d (0x3cc65c 0x25203a0c 0x131f95 0x0)
0x25203a28 : 0x1a49cb (0x3d2a94 0x1 0xe 0x3d22b8)
0x25203b38 : 0x19b3a4 (0x25203b50 0x3d6d5a0 0x25203b68 0x178bbc8)
0x25203c38 : 0x12db2d (0x178bc60 0x1 0x25203c88 0x1402f0)
0x25203c68 : 0x12db4c (0x1c 0x1 0x25203c98 0x1a3736)
0x25203c88 : 0x13f3b4 (0x1c 0x0 0x25203ca8 0x19e23a)
0x25203ca8 : 0x11f6e9 (0x4628e0c 0x421da68 0x25203ce8 0x121b41)
0x25203d18 : 0x12195c (0x4628e0c 0x421da68 0x25203d38 0x38862e8)
0x25203d38 : 0x12720d (0x421da50 0x4628dd0 0x1 0x25203d6c)
0x25203d78 : 0x14b516 (0x38862e8 0xd21b 0x1d03 0x11cc32)
0x25203db8 : 0x12b4ee (0x43faaa4 0x40c14a8 0x0 0x0)
0x25203df8 : 0x124b17 (0x43faa00 0x0 0x28 0x25203edc)
0x25203f08 : 0x195f2e (0x25203f44 0x0 0x0 0x0)
0x25203fc8 : 0x19b81e (0x3f11ae0 0x0 0x19e0b5 0x3f11ae0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffecd8
Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386

Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: AirPort Extreme, 1.2.2
Bluetooth: Version 1.9.5f4, 2 service, 1 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MHV2120BHPL, 111.79 GB
Parallel ATA Device: HL-DT-ST DVDRW GWA4080MA
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Lexmark E322, Lexmark International, Inc., Up to 12 Mb/sec, 500 mA
Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: AirPort Extreme, 1.2.2
Bluetooth: Version 1.9.5f4, 2 service, 1 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MHV2120BHPL, 111.79 GB
Parallel ATA Device: HL-DT-ST DVDRW GWA4080MA
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Lexmark E322, Lexmark International, Inc., Up to 12 Mb/sec, 500 mA

Huy
16th February 2008, 11:57 PM
It's the system crashing.

Much like a blue screen, on Windows.

Send your reports in to Apple and they'll look at it (hopefully).

Can you (perhaps) try to repeat the issue, so that you know what the problem is/how it can be replicated?

mctext
17th February 2008, 06:00 AM
Huy: I did send the report on to Apple.
Not holding my breath though.
Also not sure how to replicate the problem as it was pretty much out of my hands: as I said, I wasn't around when it happened.
Any idea from the report what might have been the cause?
Much thanks.

mct

vortex_
17th February 2008, 08:23 AM
The Kernel is the 'core' of the operating system and controls your CPU, Memory, disks etc. If the kernel crashes, or 'panics', there's little it can do; except post a message to the screen and (try to) log it to disk :)


Huy: I did send the report on to Apple.
Not holding my breath though.

They probably will look at the crashlog, but I doubt they will contact you either way. Its only to allow the developers to see why it crashed and if its a software bug that can be fixed. If they're seeing the same things causing a panic all the time, it's likely a bug and should be looked at.


Any idea from the report what might have been the cause?

The line: "panic(cpu 1 caller 0x001A49CB): Unresolved kernel trap (CPU 1, Type 14=page fault)," explains it; i'm not much a of a kernel guy so i'm not exactly sure what the issue is there (without googling it), but kernel bugs, buggy drivers and hardware issues are the most common causes of kernel panics. If it continues to happen, take the machine to the apple center and have them check it out.

Currawong
17th February 2008, 10:21 AM
It's very unlikely anyone at Apple will individually look at a kernel panic report. More likely is that they are aggregated and someone has a look at the most frequent types of crashes to determine if something needs further attention.

jrad
17th February 2008, 11:05 AM
A kernel panic is when the old dude at KFC runs out of chicken and spices.

[/Lame unnecessary joke]

I had a similar problem with my iBook recently when he HDD was kicking it. Turns out the HDD was playing up and the system was trying very hard to read from it, and eventually went to sleep (as normal, because of inactivity) and as it was trying to sleep it couldn't read or dump data from the HDD, so when it eventually gave up it went to sleep (glowing light etc) but wouldn't wake, even if on power.

Is your MBP covered by APP? I suggest you get it checked out.

mctext
17th February 2008, 11:52 AM
Thanks everyone, esp Jazza.
It's a MB not MBP.
As it's a work machine, it's still under my employer's 3-year warranty agreement with the supplier.
But I can only claim on that if it actually shits itself and becomes unusable.
Hasn't done so as yet.
[[Touches wood again.]]


mct

jrad
21st February 2008, 04:10 PM
Let us know how you go. Hopefully it doesn't come back! Might be a good opportunity to back everything up via Time Machine if you haven't already. :)