DoubleCommand / Discussion / Open Discussion: Kernel Panic with DoubleCommand v1.6.7

David - 2009-02-07

[MacBook Pro running OS 10.5.6 with DoubleCommand v1.6.3 working OK]
Downloaded the DoubleCommand-1.6.7.dmg and double-clicked the pkg to being the installation; however, almost immediately after the installation script began, I experienced a kernel panic. (Re-downloaded the .dmg directly from the developer’s Web site and got the kernel panic at the same point in the attempted installation process with each additional attempt.)

Any suggestions?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- David - 2009-02-16
  
  Further Info:
  
  Tried manually removing the v1.6.3 PrefPane (because I never get to where I can access the Uninstall provided with v1.6.7), repairing Permissions with Disk Utility, a Safe Boot, but all to no avail. Still get the kernel panic. Then I tried running the installer from the saved .dmg for v1.6.3 and found that it, too, now generates a kernel panic. (I appreciate that that .dmg is entitled "DoubleCommand1.6.3_10.4.dmg" suggesting it may be known its installer doesn't work under the OS 10.5.6 that I'm now running.)
  
  I've restored the v1.6.3 PrefPane and, pending any help from other users or the developer in response to this post, I'm "stuck" using--albeit successfully--the remapping I need using v1.6.3.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Michael Baltaks - 2009-02-17
    
    First off, if you are using 1.6.3 successfully, then that's great and you can obviously keep using that indefinitely.
    
    Secondly, if you have found that 1.6.3 works fine for you, and 1.6.7 consistently kernel panics, then that might help track down the issue, because then I can look through the differences in the kernel level code, and see what might be causing the panics.
    
    You said that the 1.6.3 installer caused a panic, but that could be when trying to remove the 1.6.7 kext. Could you run the below in Terminal, and post back the results? If you actually have 1.6.3 installed and running fine, then I can start looking at the differences since 1.6.7 seems to panic for you always.
    
    Copy after the colon and paste into Terminal.app: kextstat | grep baltaks
    
    For example, on the work Mac Pro, running 10.5.6 I get the following line:
    
    97 0 0x77fb7000 0x6000 0x5000 com.baltaks.driver.DoubleCommand (1.6.7) <21 6 5 4 2>
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - David - 2009-02-17
      
      I get:
      111 0 0x4f741000 0x5000 0x4000 com.baltaks.driver.DoubleCommand (1.6.3) <20 6 5 4 2>
      
      Hope that helps.
      
      As the v1.6.7 installer always crashed with the kernel panic very early in the installer script--the progress indicator has only a tiny bar--I'll await your advice if the above Terminal response, or something else you need me to check, will indicate that the 1.6.7 kext ever got installed.
      
      Thanks for your response and I'll standby for whatever else you can advise on the matter.
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Michael Baltaks - 2009-02-17
        
        Ok, this means you have 1.6.3 running right now, and that 1.6.7 always panics for you. If you are interested I can put together a couple of test builds to try and track down what is causing the panic. You'd then need to try installing these builds and risk causing another panic, so let me know if you want to take the time to do this.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- David - 2009-02-17
  
  I'd be happy to try anything you want to throw this way. (Before I've run, or would run, any installer or other software you might send, I save everything I had open, quit most of my applications, and wouldn't mind dealing with additional kernel panics if it'll help get to the bottom of the problem--or, at least, the problem on my computer.)
  
  For what it may be worth: After getting your latest response, I retried the v1.6.3 installer again and, as before, almost immediately after I responded to the request to enter my Admin password, I got a kernel panic. (Upon restart, the one keystroke remapping I have set remains in effect.)
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Michael Baltaks - 2009-02-17
    
    Hmm, if 1.6.3 works for you, but reinstalling causes a panic, it may be that unloading the kext is causing the panic. Can you try the following - likely to panic your machine.
    
    Copy and paste into Terminal: sudo kextunload -b com.baltaks.driver.DoubleCommand
    
    This simply attempts to unload the kext, if this does cause the panic, then this is a different issue altogether.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - David - 2009-02-17
      
      I immediately got the kernel panic.
      
      Next?
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Michael Baltaks - 2009-02-17
        
        Ok then, let's try something else. Download this file and and double click to run in Terminal, this will delete everything that DoubleCommand installs, without trying to unload it first. You should then be able to restart your computer and have no trace of DoubleCommand.
        
        http://doublecommand.sourceforge.net/files/uninstall.command
        
        It would be worth running the previous kextstat command after restarting just to make sure that no DC kext is loaded. When you're sure there's nothing left of DC, perhaps try installing the 1.6.7 version, because it might just work.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- David - 2009-02-17
  
  When I double-clicked on the downloaded uninstall.command file, I was advised it could not be executed because I don't have appropriate access privileges. (Note: I'm logged in with my usual Admin user--"dgk".)
  
  When I did a Get Info on the file, under Sharing & Permissions, it says "You can read and write" and in the table below that, it shows:
  dgk (Me) Read & Write
  (unknown) Read only
  everyone Read only
  
  Although I'm "read & write", do I need to make any privilege there?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Michael Baltaks - 2009-02-17
    
    Ah, it would be talking about execute privileges, so from Terminal:
    
    sudo chmod +x uninstall.command
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- David - 2009-02-17
  
  Did that and got:
  chmod: uninstall.command: No such file or directory
  
  I have that file--named just that--on my Desktop, if that's relevant.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Michael Baltaks - 2009-02-17
    
    Ok, I should have been more specific:
    
    Open Terminal.
    Type: cd Desktop
    Type: sudo chmod +x uninstall.command
    Then type your password when prompted.
    Type: ./uninstall.command
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- David - 2009-02-17
  
  Success!
  
  The uninstall.command now executed and reported that, if I recall correctly, three things had been removed (one of which, again if I recall correctly, was a folder). I re-started and, as suggested, re-ran the kextstat--getting a null response. I then mounted the DoubleCommand-1.6.7.dmg and launched the .pkg--which completed normally. I then re-ran the kextstat and got:
  110 0 0x47883000 0x6000 0x5000 com.baltaks.driver.DoubleCommand (1.6.7) <20 6 5 4 2>
  
  Many thanks for getting me through to where v1.6.7 is installed.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Michael Baltaks - 2009-02-17
  
  Great news. Since we were able to track this down so specifically to a panic on unload with 1.6.3, I wonder if you'd be willing to do one last test unload of 1.6.7, just to see if the same issue still remains?
  
  In Terminal: sudo kextunload -b com.baltaks.driver.DoubleCommand
  
  In any case, if you could let me know what OS version, type of Mac (I see you're running 10.5.6 on a MacBook Pro - but which generation of MacBook?), what keyboards and mice you've had attached during these tests, and the output from just running kextstat, that might really help fix the actual problem, since I'm not able to make this happen on any machines I have access to. There must be something that triggers this issue.
  
  Thanks!
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- David - 2009-02-17
  
  Happy to help.
  
  No kernel panic with doing that command now. After having to enter my Password, the response in Terminal was:
  kextunload: unload id com.baltaks.driver.DoubleCommand succeeded (any personalities also unloaded)
  
  I see, not surprisingly, that my DoubleCommand remapping is now gone. When you are ready for me to do it, please tell me what step(s) I should take to re-enable the mapping (e.g., re-run the v1.6.7 installer or some additional Terminal command(s)).
  
  My OS 10.5.6 is Build 9G55; my MacBook Pro is the 15" 2.33 GHz Intel Core 2 Duo, Model Identifier MacBookPro2,2. I am using just the internal keyboard and trackpad; no peripherals of any kind attached.
  
  The output in Terminal for an unqualified kextstat is:
  
  Index Refs Address    Size       Wired      Name (Version) <Linked Against>
      1    1 0x0        0x0        0x0        com.apple.kernel (9.6.0)
      2   48 0x0        0x0        0x0        com.apple.kpi.bsd (9.6.0)
      3    3 0x0        0x0        0x0        com.apple.kpi.dsep (9.6.0)
      4   73 0x0        0x0        0x0        com.apple.kpi.iokit (9.6.0)
      5   74 0x0        0x0        0x0        com.apple.kpi.libkern (9.6.0)
      6   67 0x0        0x0        0x0        com.apple.kpi.mach (9.6.0)
      7   37 0x0        0x0        0x0        com.apple.kpi.unsupported (9.6.0)
      8    1 0x0        0x0        0x0        com.apple.iokit.IONVRAMFamily (9.6.0)
      9    1 0x0        0x0        0x0        com.apple.driver.AppleNMI (9.6.0)
     10    1 0x0        0x0        0x0        com.apple.iokit.IOSystemManagementFamily (9.6.0)
     11    1 0x0        0x0        0x0        com.apple.iokit.ApplePlatformFamily (9.6.0)
     12   24 0x0        0x0        0x0        com.apple.kernel.6.0 (7.9.9)
     13    1 0x0        0x0        0x0        com.apple.kernel.bsd (7.9.9)
     14    1 0x0        0x0        0x0        com.apple.kernel.iokit (7.9.9)
     15    1 0x0        0x0        0x0        com.apple.kernel.libkern (7.9.9)
     16    1 0x0        0x0        0x0        com.apple.kernel.mach (7.9.9)
     17   18 0x61a000   0x10000    0xf000     com.apple.iokit.IOPCIFamily (2.5) <7 6 5 4>
     18   11 0x687000   0x4000     0x3000     com.apple.iokit.IOACPIFamily (1.2.0) <12>
     19    3 0x7a0000   0x3e000    0x3d000    com.apple.driver.AppleACPIPlatform (1.2.4) <18 17 12 7 5 4>
     20    8 0x5c1000   0x39000    0x38000    com.apple.iokit.IOHIDFamily (1.5.3) <7 6 5 4 2>
     21    0 0x615000   0x5000     0x4000     com.apple.BootCache (30.3) <7 6 5 4 2>
     22    9 0x71c000   0x18000    0x17000    com.apple.iokit.IOStorageFamily (1.5.5) <7 6 5 4 2>
     23    0 0x82c000   0x10000    0xf000     com.apple.driver.DiskImages (195.2.2) <22 7 6 5 4 2>
     24    0 0xbc8000   0x19000    0x18000    com.apple.driver.AppleIntelCPUPowerManagement (59.0.1) <12 7 6 5 4 2>
     25    0 0x6a1000   0x3000     0x2000     com.apple.security.TMSafetyNet (3) <7 6 5 3 2>
     26    0 0x862000   0x8000     0x7000     com.apple.nke.applicationfirewall (1.0.77) <7 6 5 4 2>
     27    0 0xa8a000   0x18000    0x17000    com.apple.security.seatbelt (107.10) <7 6 5 3 2>
     28    0 0x9a2000   0x3000     0x2000     com.apple.driver.AppleAPIC (1.4) <5 4>
     29    2 0x697000   0x3000     0x2000     com.apple.iokit.IOSMBusFamily (1.1) <6 5 4>
     30    0 0xbe5000   0x5000     0x4000     com.apple.driver.AppleACPIEC (1.2.4) <29 19 18 12>
     31    0 0x6a9000   0x4000     0x3000     com.apple.driver.AppleSMBIOS (1.1.1) <7 5 4>
     32    0 0xc24000   0x4000     0x3000     com.apple.driver.AppleACPIButtons (1.2.4) <20 19 18 7 6 5 4 2>
     33    0 0x7de000   0x3000     0x2000     com.apple.driver.AppleACPIPCI (1.2.4) <19 18 17 12>
     34    0 0x820000   0x3000     0x2000     com.apple.driver.AppleHPET (1.3) <18 7 6 5 4>
     35    0 0xa70000   0x5000     0x4000     com.apple.driver.AppleRTC (1.2.3) <18 6 5 4 2>
     36    1 0xa09000   0x3000     0x2000     com.apple.driver.AppleEFIRuntime (1.2.0) <7 6 5 4>
     37    0 0x69a000   0x7000     0x6000     com.apple.driver.AppleSmartBatteryManager (158.6.0) <29 18 6 5 4 2>
     38    0 0xa0c000   0x6000     0x5000     com.apple.driver.AppleEFINVRAM (1.2.0) <36 7 6 5 4>
     39    4 0x62a000   0x16000    0x15000    com.apple.iokit.IONetworkingFamily (1.6.1) <7 6 5 4 2>
     40    0 0x640000   0x40000    0x3f000    com.apple.iokit.AppleYukon2 (3.1.10b2) <39 17 12 4 2>
     41   11 0x596000   0x29000    0x28000    com.apple.iokit.IOUSBFamily (3.2.7) <7 6 5 4 2>
     42    0 0x84e000   0xe000     0xd000     com.apple.driver.AppleUSBUHCI (3.2.5) <41 17 7 6 5 4>
     43    0 0x6ad000   0x2b000    0x2a000    at.obdev.nke.LittleSnitch (2.0.46) <7 6 5 4 2>
     44    2 0xa75000   0xd000     0xc000     com.apple.iokit.IOATAFamily (2.0.0) <6 5 4 2>
     45    0 0xb9d000   0x9000     0x8000     com.apple.driver.AppleIntelPIIXATA (2.0.0) <44 17 6 5 4>
     46    2 0xbb5000   0x6000     0x5000     com.apple.iokit.IOAHCIFamily (1.5.0) <6 5 4 2>
     47    0 0xbbb000   0xd000     0xc000     com.apple.driver.AppleAHCIPort (1.5.2) <46 17 6 5 4 2>
     48    0 0x83c000   0x12000    0x11000    com.apple.driver.AppleUSBEHCI (3.2.5) <41 17 7 6 5 4>
     50    2 0x73d000   0x3f000    0x3e000    com.apple.iokit.IOFireWireFamily (3.4.6) <6 5 4 2>
     51    0 0x77c000   0x22000    0x21000    com.apple.driver.AppleFWOHCI (3.7.2) <50 17 7 6 5 4 2>
     52    0 0x5bf000   0x2000     0x1000     com.apple.iokit.IOUSBUserClient (3.2.4) <41 6 5 4>
     53    0 0xbf4000   0xc000     0xb000     com.apple.driver.AppleUSBHub (3.2.7) <41 6 5 4>
     54    4 0x703000   0x19000    0x18000    com.apple.iokit.IOSCSIArchitectureModelFamily (2.0.5) <6 5 4 2>
     55    0 0xa82000   0x4000     0x3000     com.apple.iokit.IOATAPIProtocolTransport (1.5.2) <54 44 12>
     56    0 0x734000   0x6000     0x5000     com.apple.iokit.SCSITaskUserClient (2.0.5) <54 22 6 5 4 2>
     57    3 0x7e1000   0x8000     0x7000     com.apple.iokit.IOCDStorageFamily (1.5) <22 6 5 4 2>
     58    2 0x7e9000   0x6000     0x5000     com.apple.iokit.IODVDStorageFamily (1.5) <57 22 6 5 4 2>
     59    1 0x7ef000   0x5000     0x4000     com.apple.iokit.IOBDStorageFamily (1.5) <58 57 22 6 5 4 2>
     60    1 0x7f4000   0x16000    0x15000    com.apple.iokit.IOSCSIBlockCommandsDevice (2.0.5) <54 22 6 5 4 2>
     61    0 0x80a000   0x16000    0x15000    com.apple.iokit.IOSCSIMultimediaCommandsDevice (2.0.5) <60 59 58 57 54 22 6 5 4 2>
     62    1 0x680000   0x4000     0x3000     com.apple.driver.AppleUSBComposite (3.2.0) <41 5 4>
     63    0 0x684000   0x3000     0x2000     com.apple.driver.AppleUSBMergeNub (3.2.4) <62 41 5 4>
     65    2 0xa04000   0x5000     0x4000     com.apple.iokit.IOUSBHIDDriver (3.2.2) <41 20 6 5 4>
     66    0 0xc28000   0x11000    0x10000    com.apple.iokit.IOAHCIBlockStorage (1.2.0) <46 22 6 5 4 2>
     67    0 0xc08000   0x4000     0x3000     com.apple.driver.AppleUSBTCKeyboard (1.7.0b7) <65 41 20 12>
     68    0 0xa2a000   0x5000     0x4000     com.apple.driver.XsanFilter (2.7.91) <22 12>
     69    0 0xa2f000   0x2000     0x1000     com.apple.driver.AppleUSBTCKeyEventDriver (1.7.0b7) <20 12>
     70    0 0x6d8000   0x19000    0x18000    com.apple.driver.AppleUSBTrackpad (1.7.0b7) <41 20 12>
     71    2 0xa31000   0x38000    0x37000    com.apple.iokit.IOBluetoothFamily (2.1.3f8) <7 6 5 4 2>
     72    1 0xa69000   0x7000     0x6000     com.apple.driver.AppleUSBBluetoothHCIController (2.1.3f8) <71 41 7 6 5 4>
     73    0 0xa86000   0x4000     0x3000     com.apple.driver.CSRUSBBluetoothHCIController (2.1.3f8) <72 71 5 4>
     74    5 0x937000   0x1d000    0x1c000    com.apple.iokit.IOGraphicsFamily (1.7.1) <17 7 6 5 4>
     75    3 0x954000   0xe000     0xd000     com.apple.iokit.IONDRVSupport (1.7.1) <74 17 7 6 5 4>
     76    0 0xc1c000   0x4000     0x3000     com.apple.driver.AppleBacklight (1.4.4) <75 74 17 12 6 5 4>
     77    0 0x73a000   0x3000     0x2000     com.apple.driver.AppleLPC (1.2.11) <17 6 5 4>
     78    4 0x68b000   0x9000     0x8000     com.apple.driver.AppleSMC (2.2.0d4) <18 7 6 5 4>
     79    1 0x86a000   0xe000     0xd000     com.apple.driver.IOPlatformPluginFamily (3.3.1d0) <12 4>
     80    0 0x878000   0xf000     0xe000     com.apple.driver.ACPI_SMC_PlatformPlugin (3.3.1d0) <79 78 18 17 12 7 6 5 4>
     81    1 0xaa2000   0x3000     0x2000     com.apple.kext.OSvKernDSPLib (1.1) <6 5>
     82    5 0xaa5000   0x17000    0x16000    com.apple.iokit.IOAudioFamily (1.6.5fc3) <81 6 5 4 2>
     83    0 0xc00000   0x8000     0x7000     com.AmbrosiaSW.AudioSupport (2.3.9) <82 12>
     84    0 0xbb0000   0x5000     0x4000     com.apple.driver.AppleIRController (110) <65 41 20 12>
     85    0 0xbaa000   0x6000     0x5000     com.apple.kext.AppleSMCLMU (1.4.1d3) <78 6 5 4>
     86    0 0x823000   0x9000     0x8000     com.apple.iokit.IOFireWireIP (1.7.6) <50 39 6 5 4 2>
     87    0 0x85c000   0x6000     0x5000     com.apple.driver.SMCMotionSensor (2.1.1d2) <78 6 5 4>
     88    2 0xa12000   0x7000     0x6000     com.apple.iokit.IOHDAFamily (1.6.2a37) <6 5 4 2>
     89    0 0xa19000   0xf000     0xe000     com.apple.driver.AppleHDAController (1.6.2a37) <88 17 6 5 4 2>
     90    1 0x887000   0x1f000    0x1e000    com.apple.iokit.IO80211Family (214.1) <39 7 6 5 4 2>
     91    0 0x8a6000   0x91000    0x90000    com.apple.driver.AirPort.Atheros (316.48.0) <90 39 17 7 6 5 4 2>
     93    0 0xc18000   0x4000     0x3000     com.apple.driver.AudioIPCDriver (1.0.5) <82 6 5 4 2>
     94    0 0x9a5000   0x5f000    0x5e000    com.apple.ATIRadeonX1000 (5.3.6) <75 74 17 12 6 5 4 2>
     95    0 0x694000   0x3000     0x2000     com.apple.Dont_Steal_Mac_OS_X (6.0.3) <78 7 5 4 2>
     96    1 0x5fa000   0x1b000    0x1a000    com.kensington.mouseworks.iokit.KensingtonMouseDriver (3.0) <20 12>
     97    0 0x962000   0x40000    0x3f000    com.apple.kext.ATY_Wormy (5.3.6) <75 74 18 17 6 5 4 2>
     98    0 0xba6000   0x4000     0x3000     com.Cycling74.driver.Soundflower (1.3.1) <82 12>
     99    1 0x6f1000   0x9000     0x8000     com.apple.iokit.IOSerialFamily (9.3) <7 6 5 4 2>
  100    0 0x6fa000   0x9000     0x8000     com.apple.iokit.IOBluetoothSerialManager (2.1.3f8) <99 7 6 5 4 2>
  101    0 0xbe1000   0x4000     0x3000     com.apple.driver.AppleUpstreamUserClient (2.7.2) <74 18 17 12 7 6 5 4 2>
  102    1 0xabc000   0x6e000    0x6d000    com.apple.driver.DspFuncLib (1.6.2a37) <82 6 5 4 2>
  103    0 0xb2a000   0x68000    0x67000    com.apple.driver.AppleHDA (1.6.2a37) <102 88 82 6 5 4 2>
  104    0 0x6a4000   0x5000     0x4000     com.apple.driver.AppleHWSensor (1.7.3d0) <12>
  106    0 0x79e000   0x2000     0x1000     com.kensington.mouseworks.driver.VirtualMouse (3.0) <96 20 12>
  107    0 0xb92000   0xb000     0xa000     com.apple.filesystems.autofs (2.0.1) <7 6 5 4 2>
  109    0 0x61ec3000 0x3000     0x2000     com.bresink.driver.BRESINKx86Monitoring (3.0) <12>
  111    0 0x47843000 0xd000     0xc000     com.apple.nke.asp_tcp (4.7) <7 6 5 4 2>
  112    0 0x47850000 0x4b000    0x4a000    com.apple.filesystems.afpfs (9.0) <7 6 5 4 2>
  
  Standing by for your next advice.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Michael Baltaks - 2009-02-17
    
    If you haven't already, a restart will bring DoubleCommand back, or to do it by hand:
    
    sudo /Library/StartupItems/DoubleCommand/DoubleCommand start
    
    Thanks very much for your help with that, and I'm very pleased to hear that unloading did not cause a panic with the current version.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- David - 2009-02-17
  
  All set; used the restart approach.
  
  If your review of the data from my computer suggests anything further for me to do or report, don't hesitate to ask.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kernel Panic with DoubleCommand v1.6.7

Forums

Help

Kernel Panic with DoubleCommand v1.6.7

Kernel Panic with DoubleCommand v1.6.7

Forums

Help

Kernel Panic with DoubleCommand v1.6.7 document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Kernel Panic with DoubleCommand v1.6.7