The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    panic:we are hanging here

    Discussion in 'Apple and Mac OS X' started by bball0076, Feb 2, 2009.

  1. bball0076

    bball0076 Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    its a powerbook 64 and when ever i start the pc up i get this msg

    panic (cpu 0 caller 0x002de020: unable to find driver for this platform: "powerbook 5,6".

    latest stack back trace for copu 0:
    back trace 0x00095564 0x00095a7c 0x00026838 0x002de020 x002bd360 0x002bd118 0x002bdb80 0x002be1ec 0x00a9654

    proceeding back via exception chain:
    proceeding back state (sv=0x0051fa00
    pc+0x00000000; msr=0x0000d030; dar 0x00000000; dsisr=0x000000000; lr=0x00000000; r1=-x--------; xcp=0x00000000 (unknown)

    kernel version:
    darwin kernel version 8.0.0 sat mar 26 14:15:22 pst 2005; root:xnu-792.obj~1/release_ppc
    panic:we are hanging here

    no debugger configured - dumping debig information
    msr=00001030
    latest stack back trace for cpu 0:

    proceeding back vi exception chain
    pc+0x00000000; msr=0x0000d030; dar 0x00000000; dsisr=0x000000000; lr=0x00000000; r1=-x--------; xcp=0x00000000 (unknown)

    http://img60.imageshack.us/my.php?image=1000150wv5.jpg
     
    bball0076, Feb 2, 2009
    #1
  2. Budding

    Budding Notebook Virtuoso

    Reputations:
    1,686
    Messages:
    3,982
    Likes Received:
    0
    Trophy Points:
    105
    Tried reinstalling OS X? Either that, or it's hardware failure. I'm guessing it's hardware failure.
     
    Budding, Feb 2, 2009
    #2
  3. bball0076

    bball0076 Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    i ended up changing the ram and that didnt do the trick.. so if i reinstall the os and it still doesnt work, what might be the issue? mother board?
     
    bball0076, Feb 2, 2009
    #3
  4. KernalPanic

    KernalPanic White Knight

    Reputations:
    2,125
    Messages:
    1,934
    Likes Received:
    130
    Trophy Points:
    81
    Looks like it made it past hardware checks, moved to the OS, properly identified your hardware and failed on loading the driver set for your hardware.
    (note, I am taking from my FreeBSD days... and its been awhile so take with a grain of salt)

    First guess is hard disk failure or driver corruption.

    If it boots from CD, then most likely one of the above is true.
    If it won't boot to CD, then core hardware may be the issue.
    (note, your hard disk controller may also be the culprit)

    If OS reload works, then likely its just a corrupt driver.
    If it boots to CD but reinstall of OS doesn't fix it, then most likely a hard disk failure.
     
    KernalPanic, Feb 2, 2009
    #4
  5. sulkorp

    sulkorp Notebook Deity

    Reputations:
    145
    Messages:
    1,192
    Likes Received:
    0
    Trophy Points:
    55
    Maybe try running off of an external hdd. That would tell you if its the internal drive thats messing up
     
    sulkorp, Feb 2, 2009
    #5