Macbook + Aluminium Keyboard = Crash

This has been happening lately with my MacBook Pro as well. When I open the computer to wake it from sleep, I plug in the keyboard and the computer immediately gives me the restart message.

Check for firmware updates?

10.5.4 didn't fix this problem for me. From a normal, awake state, if I plug the Apple Keybord into the USB port, I get the forced restart screen-overlay message.

Has anyone found a solution for this? I don't think it's the keyboards problem (especially since the first poster mentioned that he had no similar problems in tiger).

I'm also having this problem on my mac book pro. Plugging or unplugging my usb keyboard would give me the kernel panic page. I assumed it had something to do with the fact that I was using a ps2 keyboard with a ps2->usb dongle, and simply never plugged/unplugged the keyboard while it was running.

However, I recently bought a non-apple bluetooth keyboard, and it works "ok" normally. However, after waking my mbp, when I hit a key on the keyboard (to get it to wake up and reconnect), I instantly get a kernel panic.

Anyone have a solution for this?

I am having this problem, too. I had a couple weeks where I didn't have the problem, but now it's back. Today it also happened when I removed the aluminum keyboard. I'm also not sure where to go for support on this. I'd love a solution, I keep almost losing important stuff when I forget that a crash is imminent.

Thanks!

What you're describing is a kernel panic.

If you post the contents of your latest /Library/Logs/panic.log file here, I or someone else may be able to diagnose the issue further.

Thanks, William, here's my latest panic log message, found in Library/logs/PanicReporter/2008-09-22-213658.panic:

Mon Sep 22 21:36:57 2008
panic(cpu 0 caller 0x001A8C8A): Kernel trap at 0x808cb214, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x62233550, CR3: 0x0146c000, CR4: 0x00000660
EAX: 0x00000014, EBX: 0x62233000, ECX: 0x0050b444, EDX: 0x07d3bd54
CR2: 0x62233550, EBP: 0x5b203a78, ESI: 0x06f8c000, EDI: 0x808cd3f4
EFL: 0x00010206, EIP: 0x808cb214, CS: 0x00000008, DS: 0x5b200010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x5b203888 : 0x12b0f7 (0x458124 0x5b2038bc 0x133230 0x0)
0x5b2038d8 : 0x1a8c8a (0x461650 0x808cb214 0xe 0x460e00)
0x5b2039b8 : 0x19ece5 (0x5b2039d0 0x7559800 0x5b203a78 0x808cb214)
0x5b2039c8 : 0x808cb214 (0xe 0x48 0x10 0x10)
0x5b203a78 : 0x808c976b (0x808cd428 0x6f8c000 0x66d380 0x3e9b9a)
0x5b203aa8 : 0x808c97ee (0x6f8c000 0x6796dc 0x6f8c000 0x830aea)
0x5b203ac8 : 0x40d0dd (0x7d18f80 0x0 0x6f8c000 0x3ea7c9)
0x5b203af8 : 0x40dcd2 (0x6f8c000 0x73d2cc0 0x0 0x6f8c000)
0x5b203b38 : 0x411dfc (0x6f8c000 0x6e2ac40 0x0 0xffffffff)
0x5b203b88 : 0x411faf (0x706f800 0x5 0x1 0x2350a74)
0x5b203ba8 : 0x59e794 (0x706f800 0x1 0x1 0x704ec00)
0x5b203bc8 : 0xb5fce9 (0x706f800 0x1 0x704ee04 0x704ee00)
0x5b203c08 : 0xb5fe85 (0x704ec00 0x5b8204 0x1 0x7f36e0)
0x5b203c48 : 0xb5be0c (0x704ec00 0x12b9a400 0x5b203c78 0x3ec507)
0x5b203c88 : 0xb5bea3 (0x7039600 0x6e10e00 0x0 0x7039600)
0x5b203ca8 : 0x40cac8 (0x7039600 0x7034200 0x7 0x5b203cdf)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.baltaks.driver.DoubleCommand(1.6.5)@0x808c8000->0x808cdfff
dependency: com.apple.iokit.IOHIDFamily(1.5.2)@0x641000
com.apple.driver.AppleUSBHub(3.1.0)@0xb5a000->0xb64fff
dependency: com.apple.iokit.IOUSBFamily(3.1.0)@0x591000
com.apple.iokit.IOUSBFamily(3.1.0)@0x591000->0x5b8fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9C2028

Kernel version:
Darwin Kernel Version 9.2.1: Tue Feb 5 23:08:45 PST 2008; root:xnu-1228.4.20~1/RELEASE_I386
System model name: MacBookPro4,1 (Mac-F42C86C8)

This has been seen by others - you have DoubleCommand 1.6.5 installed, which is not compatible with Mac OS X Leopard.

Uninstall DoubleCommand and your problem should go away.

Updating to version 1.6.6b4 may also fix the problem, so it all depends if DoubleCommand is something you can live without or if you need its functionality enough you'd like to try an upgrade instead.

Thanks, William. At first I thought I had DoubleCommand uninstalled and that it worked, but now it's started crashing again. I've searched through various means (spotlight, EasyFind, manually viewing Library/Prefrerences), but can't turn up the file mentioned in the crash report. Here's my latest crash report, any other ideas?:

Tue Nov 11 15:45:35 2008
panic(cpu 0 caller 0x001A8CEC): Kernel trap at 0x88f610be, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x1bec9550, CR3: 0x0147c000, CR4: 0x00000660
EAX: 0x1bec9000, EBX: 0x0b784000, ECX: 0x0050d444, EDX: 0x0067cf3e
CR2: 0x1bec9550, EBP: 0x745d3618, ESI: 0x0000000c, EDI: 0x88f63428
EFL: 0x00010206, EIP: 0x88f610be, CS: 0x00000008, DS: 0x06f80010
Error code: 0x00000000

Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x745d3418 : 0x12b0fa (0x459234 0x745d344c 0x133243 0x0)
0x745d3468 : 0x1a8cec (0x4627a0 0x88f610be 0xe 0x461f50)
0x745d3548 : 0x19eed5 (0x745d3560 0x745d35a4 0x745d3618 0x88f610be)
0x745d3558 : 0x88f610be (0xe 0x48 0x6f80010 0x10)
0x745d3618 : 0x88f5f623 (0x88f63428 0xb784000 0x68c3b0 0x3eabca)
0x745d3648 : 0x88f5f6b0 (0xb784000 0x69871c 0x745d3678 0x3eb72c)
0x745d3668 : 0x40e10d (0x7e49800 0x0 0xb784000 0x3eb7f9)
0x745d3698 : 0x40ed02 (0xb784000 0x7566800 0x0 0x411563)
0x745d36d8 : 0x4124b8 (0xb784000 0x6e3cbc0 0x4 0xffffffff)
0x745d3728 : 0x41363c (0xb784000 0x2 0x745d3768 0x12fa53)
0x745d3768 : 0x40cc6e (0xb784000 0x2 0x1 0x12e88f40)
0x745d37a8 : 0x681102 (0xb784000 0x2 0x745d37e8 0x4088e3)
0x745d37e8 : 0x676e3b (0xb784000 0xd603000 0x0 0x0)
0x745d3818 : 0x66d9c8 (0xb784000 0xd603000 0x0 0x0)
0x745d3858 : 0x66e08d (0xd603000 0x9e207f 0x1 0x3eb72c)
0x745d38c8 : 0x66f893 (0xd603000 0x7630840 0x1 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.baltaks.driver.DoubleCommand(1.6.5)@0x88f5e000->0x88f63fff
dependency: com.apple.iokit.IOHIDFamily(1.5.3)@0x660000
com.apple.iokit.IOHIDFamily(1.5.3)@0x660000->0x698fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9F33

Kernel version:
Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386
System model name: MacBookPro4,1 (Mac-F42C86C8)

I'm having this problem too. When I open and wake my MBP, and plug in my aluminum keyboard, I get a kernel panic.

Help! This has been going on since I upgraded to Leopard.

How an Apple keyboard crashes an Apple computer boggles my mind...

ben_allison wrote:
I'm having this problem too. When I open and wake my MBP, and plug in my aluminum keyboard, I get a kernel panic.

Help! This has been going on since I upgraded to Leopard.

How an Apple keyboard crashes an Apple computer boggles my mind...

Here's the error I get:

Thu Dec 4 08:58:37 2008
panic(cpu 1 caller 0x001A8CEC): Kernel trap at 0x4134ba86, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0xff000550, CR3: 0x00fa4000, CR4: 0x00000660
EAX: 0xff000000, EBX: 0x03eb0000, ECX: 0x0050d444, EDX: 0x00655f3e
CR2: 0xff000550, EBP: 0x33ed3618, ESI: 0x0000000c, EDI: 0x4134dac8
EFL: 0x00010286, EIP: 0x4134ba86, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000

Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x33ed3418 : 0x12b0fa (0x459234 0x33ed344c 0x133243 0x0)
0x33ed3468 : 0x1a8cec (0x4627a0 0x4134ba86 0xe 0x461f50)
0x33ed3548 : 0x19eed5 (0x33ed3560 0x10002 0x33ed3618 0x4134ba86)
0x33ed3558 : 0x4134ba86 (0xe 0x3c80048 0x3c80010 0x10)
0x33ed3618 : 0x4134a563 (0x4134dac8 0x3eb0000 0x6653b0 0x3eabca)
0x33ed3648 : 0x4134a5f0 (0x3eb0000 0x67171c 0x33ed3678 0x3eb72c)
0x33ed3668 : 0x40e10d (0x4944a80 0x0 0x3eb0000 0x3eb7f9)
0x33ed3698 : 0x40ed02 (0x3eb0000 0x4051900 0x0 0x411563)
0x33ed36d8 : 0x4124b8 (0x3eb0000 0x3b4abc0 0x4 0xffffffff)
0x33ed3728 : 0x41363c (0x3eb0000 0x2 0x33ed3768 0x12fa53)
0x33ed3768 : 0x40cc6e (0x3eb0000 0x2 0x1 0xb308960)
0x33ed37a8 : 0x65a102 (0x3eb0000 0x2 0x33ed37e8 0x4088e3)
0x33ed37e8 : 0x64fe3b (0x3eb0000 0x3f3b000 0x0 0x0)
0x33ed3818 : 0x6469c8 (0x3eb0000 0x3f3b000 0x0 0x0)
0x33ed3858 : 0x64708d (0x3f3b000 0x9e207f 0x1 0x3eb72c)
0x33ed38c8 : 0x648893 (0x3f3b000 0xb1fca80 0x1 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.baltaks.driver.DoubleCommand(1.6.2)@0x41349000->0x4134dfff
dependency: com.apple.iokit.IOHIDFamily(1.5.3)@0x639000
com.apple.iokit.IOHIDFamily(1.5.3)@0x639000->0x671fff

BSD process name corresponding to current thread: kernel_task

I had the same problem, and I too had uninstalled DoubleCommand long ago.
However, it apparently was not entirely removed.
This can be seen from the "com.baltaks.driver.DoubleCommand" in the kernel panic.
This same panic shows up for plugging/unplugging keyboards as well as during
shutdown/restart. (You likely have restart hangs as well, right?)

You need to go hunt down its parts from the shell and manually remove them.
See the fix at the end of this thread:
http://forums.macrumors.com/showthread.php?t=548941

I'm amazed at how many people have this old version of DoubleCommand still infecting their system. Spread the word about the fix-- since this is making the Mac look less stable than it really is.

Bless your heart!

Yeah, the idea of an Apple keyboard crashing a Mac just seemed to suspect... of COURSE it's a third party issue...

Thanks again!