First Kernal Panic PB G4

Discussion in 'MacBook Pro' started by GoCubsGo, Oct 12, 2007.

  1. GoCubsGo macrumors Nehalem


    Feb 19, 2005
    So I experienced my first kernal panic today after owning this powerbook for 2.5 years. Knocking on the synthetic wood that I call my desk, I was viewing the log in console and as far as I can tell it was the root system itself casued the KP. Meaning it wasn't any one piece of software.

    Here's my initial crash log showing the system exception:
    Host Name:      Jessicas-Computer
    Date/Time:      2007-09-09 09:50:18.313 -0700
    OS Version:     10.4.10 (Build 8R218)
    Report Version: 4
    Command: SystemUIServer
    Path:    /System/Library/CoreServices/
    Parent:  WindowServer [61]
    Version:        1.4.6 (192.0.10)
    Build Version:  2
    Project Name:   SystemUIServer
    Source Version: 1920010
    PID:    84
    Thread: 0
    Exception:  EXC_BAD_ACCESS (0x0001)
    Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x360000e0
    Thread 0 Crashed:
    0   libobjc.A.dylib           	0x90a405bc class_initialize + 152
    1   libobjc.A.dylib           	0x90a402fc _class_lookupMethodAndLoadCache + 132
    2   libobjc.A.dylib           	0x90a401d4 objc_msgSend + 244
    3      	0x92bea5f4 -[NSArray makeObjectsPerformSelector:withObject:] + 264
    4       	0x00641448 MDGetFrontProcessOptions + 31120
    5      	0x92be2ae4 _nsnote_callback + 180
    6  	0x90805078 __CFXNotificationPost + 368
    7  	0x907fd114 _CFXNotificationPostNotification + 684
    8        	0x910deb54 __MDQueryProcessUpdates + 2156
    9        	0x910de2d4 __MDQueryCB + 548
    10        	0x910ddd48 queryClientMachPortCallback(__CFMachPort*, void*, long, void*) + 856
    11  	0x907eb850 __CFMachPortPerform + 176
    12  	0x907eb764 __CFRunLoopDoSource1 + 152
    13  	0x907dde7c __CFRunLoopRun + 1556
    14  	0x907dd4ac CFRunLoopRunSpecific + 268
    15       	0x9329bb20 RunCurrentEventLoopInMode + 264
    16       	0x9329b1b4 ReceiveNextEventCommon + 380
    17       	0x9329b020 BlockUntilNextEventMatchingListInMode + 96
    18          	0x93780ae4 _DPSNextEvent + 384
    19          	0x937807a8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
    20          	0x9377ccec -[NSApplication run] + 472
    21  	0x00002c08 0x1000 + 7176
    22  	0x000027ec 0x1000 + 6124
    23  	0x0000ce88 0x1000 + 48776
    So I was curious if I should really do anything to check the computer itself to make sure there's not a bigger problem looming. Know that at this time, as I do every Friday, I move my powerbook to the side of my display to use it as a second display while I work. I usually (and here's where I think the computer told me to **** off for the last time) unplug two USB cables and swap them, the right goes to the left and the left goes to the right. Plugged in and always pissed off at me is the logitech RF dongle that says the mouse was unplugged. It was this message that just came up and within half a second the KP message displayed. So I am guessing after weeks of doing this the computer finally thought I was too much of a dumb-ass to find another way to not unplug something while the computer was awake and just showed me who's boss.

    So if there is something else I should do, a sort of KP aftermath series of exercises just to be sure I'd love to know.

  2. mad jew Moderator emeritus

    mad jew

    Apr 3, 2004
    Adelaide, Australia
    There's no mention of USB in your panic log... It does mention your Menu Bar a bit though. What items do you have in your Menu Bar? :)
  3. GoCubsGo thread starter macrumors Nehalem


    Feb 19, 2005
    I have synergy, google g-mail notifier, sailing clicker (which I am removing since I no longer need) PSP ware (another I intend to remove) and that about covers it. Aside from your standard menu bar items of course.
  4. mad jew Moderator emeritus

    mad jew

    Apr 3, 2004
    Adelaide, Australia
    Remove the non-Apple items one-by-one to see if you can find the culprit. Of course, if this is really just a one off then I guess it's okay to let it slide. I usually do. :)
  5. Eidorian macrumors Penryn


    Mar 23, 2005
    It happens?

    Your log doesn't really point to any specific cause. It's fine to let a single panic slide unless it becomes repetitive happening.

Share This Page