Skip navigation

10.7.3, system hang, three beeps, "debugger called: double panic"

2075 Views 13 Replies Latest reply: May 13, 2012 11:33 AM by z_californianus RSS
z_californianus Level 1 Level 1 (0 points)
Currently Being Moderated
May 6, 2012 2:36 PM

Hi all

 

Here are the symptoms:

 

0. Otherwise normal system usage; system uptime more than 24 hours.

1. System freezes.

2. Three loud beeps, identified as the self-diagnostic report for cases of RAM failure.

3. Message in console/terminal style characters in the upper left hand corner of the screen: "debugger called: double panic"

 

Additional info:

 

(A) Does not seem to be timed with installation of new software or new usage pattern.

(B) Apple "genius" ran hardware diagnostics; RAM as well as all other systems passed.

(C) This happened before, but I didn't notice of there was a message or whether machine froze

(D) In response to (C), I had re-seated RAM as instructed in MacBook Pro manual.

(C) MacBook Pro, mid-2010; Mac OS X Lion 10.7.3 (11D50b); 2.66 GHz Intel Core i7; 8 GB 1067 MHz DDR3; NVIDIA GeForce GT 330M 512 MB

 

The "genius" couldn't find anything when he searched what he termed "the knowledge base." He didn't have access to the message, though.

 

Google has been useless, but I am not that great a google searcher.

 

I hope no one has had anything similar---but if you have, let me know what, if anything, helped!

 

Thanks!

MacBook Pro, Mac OS X (10.7.3)
  • Linc Davis Level 10 Level 10 (107,490 points)

    Apple "genius" ran hardware diagnostics; RAM as well as all other systems passed.

     

    What did he or she say about the beeps?

  • Linc Davis Level 10 Level 10 (107,490 points)

    Launch the Console application in any of the following ways:

     

    Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.

     

    Step 1

     

    Select "system.log" from the file list. Enter "BOOT_TIME" (without the quotes) in the search box. Note the times of the log messages referring to boot times. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged during the time something abnormal was happening. That time might be before or after the boot.

     

    For example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. If the problem is a crash or a shutdown hang, post the messages from before the boot time, when the system was about to crash or was failing to shut down. In either case, please include the BOOT_TIME message at the beginning or the end of the log extract.

     

    Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.

     

    If the log doesn't go back far enough in time, scroll down in the Console file list to /private/var/log/system.log.0.bz2. Search that archived log, and if necessary the older ones below it, for the same information.

     

    Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

     

    Step 2

     

    Do the same with kernel.log.

     

    Step 3

     

    Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. For privacy’s sake, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall or hang logs — they're very long and not helpful.

  • Linc Davis Level 10 Level 10 (107,490 points)

    Please read this whole message before doing anything.

     

    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

     

    Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.

     

    These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.

     

    Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.

     

    Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then either copy or drag it. The headings “Step 1” and so on are not part of the commands.

     

    Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.

     

    Launch the Terminal application in any of the following ways:

     

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    ☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Terminal in the page that opens.

     

    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” (without the quotes) and press return. You should then get a new line ending in a dollar sign.

     

    Step 1

     

    Copy or drag — do not type — the line below into the Terminal window, then press return:

     

    kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}'
    

     

    Post the lines of output (if any) that appear below what you just entered (the text, please, not a screenshot.)

     

    Step 2

     

    Repeat with this line:

     

    sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|edu\.mit|org\.(amavis|apache|cups|isc|ntp|postfix|x)/{print $3}'
    

     

    This time, you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning.

     

    Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.

     

    Step 3

     

    launchctl list | sed 1d | awk '!/0x|com\.apple|edu\.mit|org\.(x|openbsd)/{print $3}'
    

     

    Step 4

     

    ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null
    

     

    Important: If you synchronize with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.

     

    Step 5

     

    osascript -e 'tell application "System Events" to get name of every login item' 2> /dev/null
    

     

    Remember, steps 1-5 are all drag-and-drop or copy-and-paste, whichever you prefer — no typing, except your password. Also remember to post the output.

     

    You can then quit Terminal.

  • Linc Davis Level 10 Level 10 (107,490 points)

    Your default shell is zsh. Please repeat step 4 in the bash shell by entering "sh" and then the above command.

  • Linc Davis Level 10 Level 10 (107,490 points)

    Please read this whole message carefully, especially the warnings, before doing anything.

     

    The changes to your configuration suggested here should be considered provisional; they may not solve your problem, or they may remove functionality that you find useful. If a third-party system modification that you want to keep is causing the problem, seek help from its developer.

     

    WARNING: Back up all data now if you haven’t already done so. Before proceeding, you must be sure you can restore your system to its present state, even if it becomes unbootable. If you’re not sure you can do that, STOP — DON’T CHANGE ANYTHING. If you’re dissatisfied with the results of the procedure suggested below, restore from your backup. I will not be responsible for the consequences, and I will not help, if you ignore this warning.

     

    You should either remove or update the following system modification(s), if an update is available from the developer:

     

    N/A

     

    and definitely remove at least the following:

     

    † VirusBarrier

     

    Whatever you remove must be removed completely, and (unless otherwise specified in this message) the only way to do that is to use the uninstallation tool, if any, provided by the third-party developer, or to follow his instructions. In some cases it may be necessary to re-download or even reinstall the software in order to get rid of it. I can't be more specific, because I don't install such things myself. Please do your own research.

     

    Here are some general guidelines to get you started. Suppose you want to remove something called “BrickYourMac.” First check the developer's website, say www.brickyourmac.com, for instructions. If you don’t find any, email the developer. Failing that, download BrickYourMac.dmg and open it. There may be an application in there such as “Uninstall BrickYourMac.” If not, open “BrickYourMac.pkg” and look for an Uninstall button.

     

    If you can’t remove the software in any other way, you’ll have to erase your boot volume and perform a clean reinstallation of the Mac OS. Never install any third-party software unless you're sure you know how to uninstall it; otherwise you may create problems that are very hard to solve.

     

    WARNING: Trying to remove complex system modifications by hunting for files by name often will not work and may make the problem worse.

     

    I recommend that you never reinstall the modifications marked with a dagger (†) above, if any. If your problem is resolved after uninstalling all the above modifications and rebooting, but you still want to use some of those not marked with a dagger, you can experiment with putting them back, one at a time, testing carefully after each step. Keep in mind that system modifications may be incompatible with each other or with future Mac OS updates, so it may not be clear which one is at fault.

     

    If you still have problems after making the suggested changes and rebooting, post again. Remember: if you don’t like the results of this procedure, you can undo it by restoring from the last backup you made before you started.

  • Linc Davis Level 10 Level 10 (107,490 points)

    My opinion is that you have a hardware fault, possibly bad RAM. The Apple Hardware Test is unreliable. I don't think there's any point in further software troubleshooting.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.