Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

kpangilinan

macrumors member
Original poster
Oct 5, 2006
33
0
New York
I've been having some issues with multi-USB ports. I have one connected to my iBook and at night, I'll remove it so I can use my laptop on my bed. But there are times when I'll remove the USB cable and all of a sudden, a screen pops up and says I have te restart my computer. Can anyone explain why this is happening?
 
Do you mean a USB hub? What you saw was a kernel panic.

If you haven't seen it since it may have been a fluke. If it's a recurring issue, then we can do some more investigating and see what's causing the error.
 
It would help (assuming you're indeed talking about a hub) if you answered these questions too:

- Is the hub self-powered (it has its own power adapter / supply) or bus-powered (no separate power supply)

- What is plugged into it?
 
i got a mbp.. when ive plugged my phone into charge via usb and then disconnect it, it sometimes kernel panics, probably 1 out of 10 times... i think its a random thing, normally when i catch the computer unaware, ie when its just woken up, or its been inactive for a while.. i think the shock of suddenly removing a device makes it panic!!
 
Yeah, hub. Sorry. It has its own AC adapter. Like crazyworld, it'll happen 1 out of 10 times. Just an estimate though. Is there anything I can do to make sure it doesn't happen anymore. I have a multi-card reader, ipod wire, wireless keyboard and mouse hub, and external hard drive (which is off most of the time)
 
Mmm, okay. On your computer, there should be a file called panic.log. You can access it via the Console utility in your Utilities folder. I think it's in /var/log (you'll have to dig for it in the left hand side of the Console window). A crash entry will begin with the time that the kernel panic happened and then some lines about a trace back. Post the first fifty lines or so of that, starting with the very first line of the panic incident. That can help figure out if it's one specific piece of hardware doing this.
 
This?

Tue Feb 20 20:23:27 2007 crashdump[283]: crashdump started
Tue Feb 20 20:23:30 2007 crashdump[283]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Tue Feb 20 20:23:32 2007 crashdump[283]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Thu Feb 22 21:33:52 2007 crashdump[318]: crashdump started
Thu Feb 22 21:33:55 2007 crashdump[318]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Thu Feb 22 21:33:56 2007 crashdump[318]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sun Mar 11 20:54:43 2007 crashdump[843]: crashdump started
Sun Mar 11 20:54:46 2007 crashdump[843]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/QuickTime Player.crash.log
Sun Mar 11 20:54:48 2007 crashdump[843]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/QuickTime Player.crash.log
Fri Mar 16 22:36:17 2007 crashdump[383]: crashdump started
Fri Mar 16 22:36:22 2007 crashdump[383]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Fri Mar 16 22:36:33 2007 crashdump[383]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sun Apr 1 19:24:31 2007 crashdump[236]: crashdump started
Sun Apr 1 19:24:33 2007 crashdump[237]: crashdump started
Sun Apr 1 19:24:33 2007 crashdump[236]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/MPlayer OSX.crash.log
Sun Apr 1 19:24:34 2007 crashdump[236]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/MPlayer OSX.crash.log
Sun Apr 1 19:24:35 2007 crashdump[237]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/mplayer.crash.log
Sun Apr 1 19:24:36 2007 crashdump[237]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/mplayer.crash.log
Sun Apr 1 19:24:38 2007 crashdump[237]: Failed to re-launch /Users/Keith/Applications/MPlayer OSX.app/Contents/Resources/External_Binaries/mplayer.app/Contents/MacOS/mplayer - nil bundle identifier!
Fri Apr 6 07:18:27 2007 crashdump[397]: crashdump started
Fri Apr 6 07:18:29 2007 crashdump[397]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Fri Apr 6 07:18:38 2007 crashdump[397]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Fri Apr 6 21:42:04 2007 crashreporterd[99]: pid_for_task ffffffff failed: (os/kern) failure
Fri Apr 6 21:42:04 2007 crashreporterd[99]: task_set_exception_ports failed: (ipc/send) invalid destination port
Fri Apr 6 21:42:05 2007 crashdump[465]: crashdump started
Fri Apr 6 21:42:05 2007 crashdump[465]: Crashdump invoked with pid 0
Fri Apr 6 21:42:05 2007 crashreporterd[99]: mach_msg() reply failed: (ipc/send) invalid destination port
Fri Apr 6 21:42:05 2007 crashdump[465]: Started writing crash report to: /Library/Logs/CrashReporter/???.crash.log
Fri Apr 6 21:42:05 2007 crashdump[465]: Finished writing crash report to: /Library/Logs/CrashReporter/???.crash.log
Tue Apr 10 22:28:17 2007 crashdump[336]: crashdump started
Tue Apr 10 22:28:20 2007 crashdump[336]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Tue Apr 10 22:28:32 2007 crashdump[336]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Thu Apr 12 21:46:30 2007 crashdump[305]: crashdump started
Thu Apr 12 21:46:32 2007 crashdump[305]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/MacTheRipper.crash.log
Thu Apr 12 21:46:34 2007 crashdump[305]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/MacTheRipper.crash.log
Wed Apr 18 07:09:26 2007 crashdump[422]: crashdump started
Wed Apr 18 07:09:29 2007 crashdump[422]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Wed Apr 18 07:09:41 2007 crashdump[422]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sat Apr 28 23:07:39 2007 crashdump[842]: crashdump started
Sat Apr 28 23:07:39 2007 crashdump[842]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sat Apr 28 23:07:39 2007 crashdump[843]: crashdump started
Sat Apr 28 23:07:39 2007 crashdump[842]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sat Apr 28 23:07:39 2007 crashdump[843]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sat Apr 28 23:07:39 2007 crashdump[843]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Fri May 18 06:48:31 2007 crashdump[587]: crashdump started
Fri May 18 06:48:34 2007 crashdump[587]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Fri May 18 06:48:36 2007 crashdump[587]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Mon May 21 07:27:37 2007 crashdump[545]: crashdump started
Mon May 21 07:27:39 2007 crashdump[545]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Mon May 21 07:27:41 2007 crashdump[545]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Tue May 22 22:41:24 2007 crashdump[115]: crashdump invoked as panicdump
Wed May 23 22:01:18 2007 crashdump[112]: crashdump invoked as panicdump
Sat May 26 13:49:35 2007 crashdump[306]: crashdump started
Sat May 26 13:49:37 2007 crashdump[306]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sat May 26 13:49:46 2007 crashdump[306]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sat Jun 2 21:35:30 2007 crashdump[100]: crashdump invoked as panicdump
Mon Jun 4 22:22:49 2007 crashreporterd[108]: pid_for_task ffffffff failed: (os/kern) failure
Mon Jun 4 22:22:49 2007 crashreporterd[108]: task_set_exception_ports failed: (ipc/send) invalid destination port
Mon Jun 4 22:22:50 2007 crashdump[293]: crashdump started
Mon Jun 4 22:22:50 2007 crashdump[293]: Crashdump invoked with pid 0
Mon Jun 4 22:22:50 2007 crashreporterd[108]: mach_msg() reply failed: (ipc/send) invalid destination port
Mon Jun 4 22:22:50 2007 crashdump[293]: Started writing crash report to: /Library/Logs/CrashReporter/???.crash.log
Mon Jun 4 22:22:50 2007 crashdump[293]: Finished writing crash report to: /Library/Logs/CrashReporter/???.crash.log
Sat Jun 9 00:36:52 2007 crashdump[99]: crashdump invoked as panicdump
Sun Jun 10 06:59:05 2007 crashdump[216]: crashdump started
Sun Jun 10 06:59:07 2007 crashdump[216]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Sun Jun 10 06:59:08 2007 crashdump[216]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Wed Jun 27 22:58:37 2007 crashdump[358]: crashdump started
Wed Jun 27 22:58:41 2007 crashdump[358]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Wed Jun 27 22:58:44 2007 crashdump[358]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/firefox-bin.crash.log
Thu Jun 28 20:18:14 2007 crashdump[301]: crashdump started
Thu Jun 28 20:18:19 2007 crashdump[301]: Started writing crash report to: /Users/Keith/Library/Logs/CrashReporter/Safari.crash.log
Thu Jun 28 20:18:22 2007 crashdump[301]: Finished writing crash report to: /Users/Keith/Library/Logs/CrashReporter/Safari.crash.log
Fri Jun 29 22:55:30 2007 crashdump[115]: crashdump invoked as panicdump
 
No... that's not the right file, sorry, although it is interesting. The file you want is /library/logs/panic.log (sorry about the erroneous location earlier, but in any event, the file is actually called "panic.log"). This is an example of what an entry looks like -- it documents the last panic on my iBook (on 7/1/06):

Code:
Sat Jul  1 18:12:10 2006


Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x0000000023961004 PC=0x00000000003D54BC
Latest crash info for cpu 0:
   Exception state (sv=0x246F7500)
      PC=0x003D54BC; MSR=0x00089030; DAR=0x23961004; DSISR=0x40000000; LR=0x002C0C08; R1=0x0F81BCE0; XCP=0x0000001C (0x700 - Program)
      Backtrace:
0x002C0CFC 0x0053BF00 0x0053B808 0x0003C744 0x000A9894 
      Kernel loadable modules in backtrace (with dependencies):
         com.apple.iokit.IOADBFamily(8.0.0)@0x53a000
Proceeding back via exception chain:
   Exception state (sv=0x246F7500)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x246F7780)
      PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.6.0: Tue Mar  7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
      Backtrace:
         0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00 
Proceeding back via exception chain:
   Exception state (sv=0x246F7500)
      PC=0x003D54BC; MSR=0x00089030; DAR=0x23961004; DSISR=0x40000000; LR=0x002C0C08; R1=0x0F81BCE0; XCP=0x0000001C (0x700 - Program)
      Backtrace:
0x002C0CFC 0x0053BF00 0x0053B808 0x0003C744 0x000A9894 
      Kernel loadable modules in backtrace (with dependencies):
         com.apple.iokit.IOADBFamily(8.0.0)@0x53a000
   Exception state (sv=0x246F7780)
      PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.6.0: Tue Mar  7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC
*********
 
BlackBerry Pearl 8100 = Kernel Panic!!

What type of phone are you plugging in? I'm using a BlackBerry Pearl 8100 and am having the same issues. I've done some searching and found that other are having this problem too.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.