Kernel Panic (1st one!) on Powerbook

Discussion in 'macOS' started by gauchogolfer, Jan 27, 2007.

  1. gauchogolfer macrumors 603

    gauchogolfer

    Joined:
    Jan 28, 2005
    Location:
    American Riviera
    #1
    So I experienced my first kernel panic tonight on my powerbook, as I unplugged my nano (after ejecting it in iTunes). Immediate grey screen telling me to reboot. I've posted the panic.log contents below; can someone confirm that this is the problem? Also, my nano has been a bit flaky lately, being unwilling to play certain podcasts (locking up, requiring a reboot). Could the nano be the problem? If so, do you think a re-initialization might fix it or should I head into the Apple Store?

    Thanks for the help.

    P.S. should I do anything to make sure nothing was harmed by the kernel panic, fsck or the like?

    Code:
    Sat Jan 27 21:48:03 2007
    
    
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000010 PC=0x0000000039500C9C
    Latest crash info for cpu 0:
       Exception state (sv=0x3BA4AA00)
          PC=0x39500C9C; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x39500C98; R1=0x21FB37C0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x39500C98 0x39500C34 0x002D124C 0x39501298 0x39501104 0x004409E8 
             0x00931164 0x00932CC4 0x00932FC0 0x009330D0 0x004408A0 0x00931164 0x00931830 0x009318C8 
             0x0092C83C 0x002D0B94 0x002CFA5C 0x000A9314 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.iokit.IOUSBMassStorageClass(1.4.5)@0x394fe000
                dependency: com.apple.iokit.IOUSBFamily(2.5.6)@0x43e000
                dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4.9)@0x593000
                dependency: com.apple.iokit.IOStorageFamily(1.5)@0x4f9000
             com.apple.driver.AppleUSBEHCI(2.5.8)@0x928000
                dependency: com.apple.iokit.IOUSBFamily(2.5.6)@0x43e000
                dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
             com.apple.iokit.IOUSBFamily(2.5.6)@0x43e000
    Proceeding back via exception chain:
       Exception state (sv=0x3BA4AA00)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x37A6A780)
          PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    
    Kernel version:
    Darwin Kernel Version 8.8.0: Fri Sep  8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780 
    Proceeding back via exception chain:
       Exception state (sv=0x3BA4AA00)
          PC=0x39500C9C; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x39500C98; R1=0x21FB37C0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x39500C98 0x39500C34 0x002D124C 0x39501298 0x39501104 0x004409E8 
             0x00931164 0x00932CC4 0x00932FC0 0x009330D0 0x004408A0 0x00931164 0x00931830 0x009318C8 
             0x0092C83C 0x002D0B94 0x002CFA5C 0x000A9314 
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.iokit.IOUSBMassStorageClass(1.4.5)@0x394fe000
                dependency: com.apple.iokit.IOUSBFamily(2.5.6 
    *********
     
  2. SMM macrumors 65816

    SMM

    Joined:
    Sep 22, 2006
    Location:
    Tiger Mountain - WA State
    #2
    It is not a bad idea to occasionally run fsck. (odd thing just happened. spellchecker went red on fsck, which is reasonable. however, after right-clicking to 'add word', it brought up a suggestion of 'fu*k'. after laughing, i clicked to lookup in dictionary. sure enough, there it was in all its' glory and common uses). Back to the question, it does look read as if the issue was related to the USB Mass Storage Device. You are unmounting the volume correctly, right? If so, have Apple look at it. I have suspected USB ports of failing, but always had an easy alternative (use another one), which quickly solved the problem. Of course, the problem might never appear again.
     
  3. gauchogolfer thread starter macrumors 603

    gauchogolfer

    Joined:
    Jan 28, 2005
    Location:
    American Riviera
    #3
    So, would you suspect the USB port or the Nano, on first guess?
     
  4. SMM macrumors 65816

    SMM

    Joined:
    Sep 22, 2006
    Location:
    Tiger Mountain - WA State
    #4
    I would try the nano in a different port, or different computer. That should help identify the guilty party. I think a different computer would be best (if you can manage it). Other possibilities are corrupted drivers/files on the computer itself.
     
  5. spork183 macrumors 6502a

    spork183

    Joined:
    Jul 30, 2006
    #5
    I'd mess with the nano first. Seems an odd coincidence that the nano's been acting up and you get a Colonel Panic (Sander's Brother?) upon an eject.
     
  6. gauchogolfer thread starter macrumors 603

    gauchogolfer

    Joined:
    Jan 28, 2005
    Location:
    American Riviera
    #6
    Thanks for the replies.

    If I come to any conclusions I'll update this thread.
     
  7. IJ Reilly macrumors P6

    IJ Reilly

    Joined:
    Jul 16, 2002
    Location:
    Palookaville
    #7
    Is the kernel panic reproducible? If not, I wouldn't worry about it too much. Checking the drive after any forced restart is always a good idea.
     
  8. gauchogolfer thread starter macrumors 603

    gauchogolfer

    Joined:
    Jan 28, 2005
    Location:
    American Riviera
    #8
    So far it's not reproducible. I went through the eject/unplug sequence twice today with the nano in the same USB port as before, with no panics.

    By checking the drive you mean fsck, right? I guess I need to head off to the MR Guide section...never done that one before.

    Edit: so, fsck just said there were two 'Illegal Names' and minor repairs on volume header (2,0). I reran after the fix and it came up rosy. I guess there weren't any real problems.
     
  9. IJ Reilly macrumors P6

    IJ Reilly

    Joined:
    Jul 16, 2002
    Location:
    Palookaville
    #9
    Maybe not. Sometimes it's a random hit. Always good to check the drive afterwards, though -- those things don't heal themselves!
     

Share This Page