OSX kernel panic resource?

Posted:
in macOS edited January 2014
anyone know if there's a database, webpage, program or the like that explains what the KP codes stand for?



i've gotten at least three GSOD's © (Grey Screen of Death) in the last two weeks, and i'd like to try and trace it back to it's source. however, i'm having a hell of a time finding the resources to do it.



anyone out there got a suggestion as to where i could find the info?



-alcimedes
«1

Comments

  • Reply 1 of 22
    I'm not familiar with any specific resource, but I know that if you look at the actual crash output that there is usually some driver names listed (or other info like memory exception or something) that can give you a good idea where the problem was.
  • Reply 2 of 22
    bungebunge Posts: 7,329member
    [quote]Originally posted by Brad:

    <strong>I'm not familiar with any specific resource, but I know that if you look at the actual crash output...</strong><hr></blockquote>



    Where is the crash output? In 10.2, there is no longer an on screen output (unless you consider the polite message asking you to reboot your machine KP output.)
  • Reply 3 of 22
    well, two things actually. i did go through the crash log, and i read through them, but it doesn't make all that much sense to me. hence the searching for a KP resource.



    i also have had a KP where it puked the old style text across the screen. not the normal grey screen with warning.



    i want to know what the hell is wrong with my computer, and i'm having a hell of a time finding out.
  • Reply 4 of 22
    spartspart Posts: 2,060member
    Maybe you could post it here?
  • Reply 5 of 22
    Tracing down kernel panics is not trivial.. usually you just get some idea of the thread that crashed and some info about the memory that it was accessing at the time and this generally doesn't mean much to people other than the programmers...
  • Reply 6 of 22
    nevynnevyn Posts: 360member
    It is pretty involved to do it for yourself. There's a 'Darwin-users' mailing list at lists.apple.com where some Apple folk might provide feedback.



    It is also worthwhile to submit it back to Apple through email... so long as you aren't particularly obsessed by privacy concerns over whatever random bits of information were in the registers/cache when the crash occurred.
  • Reply 7 of 22
    Tue Sep 17 16:22:13 2002





    Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0xe1064000 PC=0x0008b424

    Latest crash info for cpu 0:

    Exception state (sv=0x1F918280)

    PC=0x0008B424; MSR=0x00141000; DAR=0xE1064000; DSISR=0x42000000; LR=0x0008B3D4; R1=0x18113BE0; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x000885F0 0x00087370 0x000665DC 0x0006684C 0x0005548C 0x0002AE70 0x000257E4 0x00025BE0

    0x00092A38 0x63743E0A

    Proceeding back via exception chain:

    Exception state (sv=0x1F918280)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x27DE7C80)

    PC=0x90074328; MSR=0x0000F030; DAR=0xE1064000; DSISR=0x42000000; LR=0x90006670; R1=0xBFFEF1E0; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.0:

    Sat Jul 27 13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC





    panic(cpu 0): 0x200 - Machine check

    Latest stack backtrace for cpu 0:

    Backtrace:

    0x0008593C 0x00085D6C 0x00028B8C 0x0008F648 0x000926B8

    Proceeding back via exception chain:

    Exception state (sv=0x1F918280)

    PC=0x0008B424; MSR=0x00141000; DAR=0xE1064000; DSISR=0x42000000; LR=0x0008B3D4; R1=0x18113BE0; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x000885F0 0x00087370 0x000665DC 0x0006684C 0x0005548C 0x0002AE70 0x000257E4 0x00025BE0

    0x00092A38 0x63743E0A

    Exception state (sv=0x27DE7C80)

    PC=0x90074328; MSR=0x0000F030; DAR=0xE1064000; DSISR=0x42000000; LR=0x90006670; R1=0xBFFEF1E0; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.0:

    Sat Jul 27 13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC



    *********



    Thu Sep 19 14:30:15 2002





    Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x9042b918 PC=0x0008b644

    Latest crash info for cpu 0:

    Exception state (sv=0x1FFDD000)

    PC=0x0008B644; MSR=0x00141000; DAR=0x9042B918; DSISR=0x40000000; LR=0x0008882C; R1=0x189F3AF0; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x00087430 0x0006F9C4 0x00066618 0x0006689C 0x00078FE4 0x00078A50 0x0007BCBC 0x00039158

    0x001D122C 0x001D10C0 0x00203A6C 0x00092870 0xFF410001

    Proceeding back via exception chain:

    Exception state (sv=0x1FFDD000)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x289CFC80)

    PC=0x90005FCC; MSR=0x0000F030; DAR=0x8A37C0D4; DSISR=0x40000000; LR=0x000039C8; R1=0xBFFFFE30; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.1:

    Fri Sep 6 23:24:34 PDT 2002; root:xnu/xnu-344.2.obj~2/RELEASE_PPC





    panic(cpu 0): 0x200 - Machine check

    Latest stack backtrace for cpu 0:

    Backtrace:

    0x0008598C 0x00085DBC 0x00028B8C 0x0008F688 0x000926F8

    Proceeding back via exception chain:

    Exception state (sv=0x1FFDD000)

    PC=0x0008B644; MSR=0x00141000; DAR=0x9042B918; DSISR=0x40000000; LR=0x0008882C; R1=0x189F3AF0; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x00087430 0x0006F9C4 0x00066618 0x0006689C 0x00078FE4 0x00078A50 0x0007BCBC 0x00039158

    0x001D122C 0x001D10C0 0x00203A6C 0x00092870 0xFF410001

    Exception state (sv=0x289CFC80)

    PC=0x90005FCC; MSR=0x0000F030; DAR=0x8A37C0D4; DSISR=0x40000000; LR=0x000039C8; R1=0xBFFFFE30; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.1:

    Fri Sep 6 23:24:34 PDT 2002; root:xnu/xnu-344.2.obj~2/RELEASE_PPC



    *********



    Tue Sep 24 14:35:37 2002





    Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x019acea8 PC=0x0008b644

    Latest crash info for cpu 0:

    Exception state (sv=0x1F5D9C80)

    PC=0x0008B644; MSR=0x00141000; DAR=0x019ACEA8; DSISR=0x40000000; LR=0x0008882C; R1=0x18093770; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x00087430 0x0006F8C8 0x00066618 0x0006689C 0x0006217C 0x00205420 0x0022CE14 0x00229848

    0x0024C238 0x0024C0A0 0x002534DC 0x0023875C 0x0007CB30 0x0007CBA0 0x0002AE80 0x0001D204

    0x000222B0 0x00023B4C 0x0003913C 0x001D122C 0x001DB178 0x00027450 0x00092B54 0x02862000

    Proceeding back via exception chain:

    Exception state (sv=0x1F5D9C80)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x27A9E500)

    PC=0x9001BC0C; MSR=0x0000F030; DAR=0xBFFFD8E0; DSISR=0x0A000000; LR=0x93894BE8; R1=0xBFFFF620; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.1:

    Fri Sep 6 23:24:34 PDT 2002; root:xnu/xnu-344.2.obj~2/RELEASE_PPC





    panic(cpu 0): 0x200 - Machine check

    Latest stack backtrace for cpu 0:

    Backtrace:

    0x0008598C 0x00085DBC 0x00028B8C 0x0008F688 0x000926F8

    Proceeding back via exception chain:

    Exception state (sv=0x1F5D9C80)

    PC=0x0008B644; MSR=0x00141000; DAR=0x019ACEA8; DSISR=0x40000000; LR=0x0008882C; R1=0x18093770; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x00087430 0x0006F8C8 0x00066618 0x0006689C 0x0006217C 0x00205420 0x0022CE14 0x00229848

    0x0024C238 0x0024C0A0 0x002534DC 0x0023875C 0x0007CB30 0x0007CBA0 0x0002AE80 0x0001D204

    0x000222B0 0x00023B4C 0x0003913C 0x001D122C 0x001DB178 0x00027450 0x00092B54 0x02862000

    Exception state (sv=0x27A9E500)

    PC=0x9001BC0C; MSR=0x0000F030; DAR=0xBFFFD8E0; DSISR=0x0A000000; LR=0x93894BE8; R1=0xBFFFF620; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.1:

    Fri Sep 6 23:24:34 PDT 2002; root:xnu/xnu-344.2.obj~2/RELEASE_PPC



    *********



    Fri Sep 27 00:07:28 2002





    Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x129b6000 PC=0x0008b464

    Latest crash info for cpu 0:

    Exception state (sv=0x27BFF000)

    PC=0x0008B464; MSR=0x00141000; DAR=0x129B6000; DSISR=0x40000000; LR=0x0008B414; R1=0x18043EB0; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x000998C4 0x00099950 0x0009A620 0x00000000

    Proceeding back via exception chain:

    Exception state (sv=0x27BFF000)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x27D80000)

    PC=0x0035B124; MSR=0x0000D030; DAR=0x129B6000; DSISR=0x40000000; LR=0x0034DCC4; R1=0xBFFFF080; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.1:

    Fri Sep 6 23:24:34 PDT 2002; root:xnu/xnu-344.2.obj~2/RELEASE_PPC





    panic(cpu 0): 0x200 - Machine check

    Latest stack backtrace for cpu 0:

    Backtrace:

    0x0008598C 0x00085DBC 0x00028B8C 0x0008F688 0x000926F8

    Proceeding back via exception chain:

    Exception state (sv=0x27BFF000)

    PC=0x0008B464; MSR=0x00141000; DAR=0x129B6000; DSISR=0x40000000; LR=0x0008B414; R1=0x18043EB0; XCP=0x00000008 (0x200 - Machine check)

    Backtrace:

    0x000998C4 0x00099950 0x0009A620 0x00000000

    Exception state (sv=0x27D80000)

    PC=0x0035B124; MSR=0x0000D030; DAR=0x129B6000; DSISR=0x40000000; LR=0x0034DCC4; R1=0xBFFFF080; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 6.1:

    Fri Sep 6 23:24:34 PDT 2002; root:xnu/xnu-344.2.obj~2/RELEASE_PPC



    *********



    not sure if anyone can make sense of that, but there you go.



    -alcimedes
  • Reply 8 of 22
    alcimedesalcimedes Posts: 5,486member
    anyone?
  • Reply 9 of 22
    defiantdefiant Posts: 4,876member
    yeah, well, the best advice is that you tell it apple through their feedback page:



    <a href="http://www.apple.com/macosx/feedback/"; target="_blank">http://www.apple.com/macosx/feedback/</a>;



    tell them what u posted above, and what exactly you were doing. include as much detail as possible.



    HTH ?



    [ 10-01-2002: Message edited by: Defiant ]</p>
  • Reply 10 of 22
    zozo Posts: 3,115member
    i've had 3 KPs since installing 10.2 and only one was logged. Hmmm.



    Alci, usually there is a file that appears as a backtrace, but not in your case. Hmmm, weird. I can;t identify anything else in that code vomit.
  • Reply 11 of 22
    alcimedesalcimedes Posts: 5,486member
    the oddest part is that the last one did the nice text vomit to the screen. i'd thought that had been taken care of.



    my wife has also somehow managed to make my machine KP every time my back is turned. still not sure what exactly is going on there, but i don't worry about it since i just don't let her touch my computer anymore.



    i'll send it off to apple. not sure it will do anything, but what the hell.
  • Reply 12 of 22
    zapchudzapchud Posts: 844member
    10.2 has been the most kernelpanicing and unstable OS since 9.x for me. most of the panics seems SMB and networking-related. I don't know exactly how many panics I've had, but they're many. and only one did show up with the multiple-language reboot instructions...

    argh!

    I do even have a brand new 1GHz WindTunnel?, so the hardware shouldn't be the problem. again; argh!
  • Reply 13 of 22
    rogue27rogue27 Posts: 607member
    I've still never seen a 10.2 kernel panic...
  • Reply 14 of 22
    zozo Posts: 3,115member
    while I wasn't too convinced about it before, but since I have uninstalled all haxies (from unsanity) OS X hasn't KP on me.



    HAXIES ARE EVIL!!!
  • Reply 15 of 22
    zozo Posts: 3,115member
    on MacNN today:



    Apple Knowledge Base roundup: Apple describes &lt;http://docs.info.apple.com/article.html?artnum=107111&gt; how to resolve a kernel panic that may appear after updating to Mac OS X 10.2.1, or optimizing a Mac OS Standard volume; Windows File Sharing (or "SMB") browsing is limited to your subnet &lt;http://docs.info.apple.com/article.html?artnum=107130&gt; under Mac OS X 10.2;



    This is the article:



    [quote]

    TITLE



    Mac OS X 10.2.1: Kernel Panic After Updating to 10.2.1 Optimizing Mac OS Standard Volume





    TOPIC



    In a rare situation, a kernel panic may appear during startup after either updating to Mac OS X 10.2.1, or optimizing a Mac OS Standard (HFS) volume using third-party software. This issue is more likely if Mac OS X 10.2 is installed on a UNIX File System (UFS) formatted volume.



    DISCUSSION





    Symptom



    A kernel panic message appears during startup after updating to Mac OS X 10.2.1, or optimizing a Mac OS Standard volume. The most recent panic in the "panic.log" file contains the text:

    "kernel loadable modules in backtrace com.apple.BootCache (with dependencies)"



    Products affected

    o Mac OS X 10.2 or later

    o Mac OS X Server 10.2 or later



    Solution



    Use the following workaround:

    1. Press and hold the Shift key during startup.

    Note: If you cannot start up the computer this way, see technical document 106464, "Mac OS X: Troubleshooting a Startup Issue".

    2. Click the Finder icon in the Dock.

    3. Choose Go To Folder from the Go menu.

    4. Type: /var/db

    5. Click Go.

    6. Locate this file: BootCache.playlist

    7. Drag this file to the Trash.

    8. Restart

    <hr></blockquote>
  • Reply 16 of 22
    well I've suddenly started getting KPs - 4 or 5 just in last 24 hours.

    Seems to coincide with my mouse playing up. It stops moving for just less than a second every so often.

    In fact it has stopped moving altogether a couple of times and have had to pull out the usb plug and reinsert to get to work.



    Is it possible these are related?



    10.2.1 installed on 933G4 (single CPU 756 RAM)



    Think I might try to get the mouse replaced on warrantee



    [ 10-07-2002: Message edited by: Aussie John ]</p>
  • Reply 17 of 22
    zozo Posts: 3,115member
    heh.. yes as a matter of fact.



    I bought a spiffy new Dual Optical Logitech mouse 6 months ago... and I would get KPs every now and then. Actually, no KP, just TOTAL freezes. Especially in some games.



    Then, I saw that I installed Jaguar, clean install, NO drivers, no apps, etc and I got a total freeze.



    I changed back to my old MS Intellimouse Optical, and I havent had those problems anymore.



    send and email to your mouse manufacturer to tell them to resolve the prob somehow
  • Reply 18 of 22
    [quote]



    send and email to your mouse manufacturer to tell <hr></blockquote>



    Its an Apple optical mouse so maybe it is faulty. I'll have a word to my local reseller after I get back from interstate



    [ 10-08-2002: Message edited by: Aussie John ]</p>
  • Reply 19 of 22
    just an update for your info-

    since using an older puck mouse I had laying about- no kernel panics.



    The optical mouse is being replaced
  • Reply 20 of 22
    alcimedesalcimedes Posts: 5,486member
    oh yeah, an update from my end.



    took out a ram chip from one machine, put it in the other. no more KP's
Sign In or Register to comment.