Any one know why this process is eating up my cpu?

Discussion in 'macOS' started by diehardmacfan, Jun 8, 2007.

  1. diehardmacfan macrumors regular

    Joined:
    Mar 12, 2007
    #1
    Hi everyone,

    about 3 days ago i spilt some water into my ibook g3

    i let is sit until about now and it booted up fine.

    i repaired disk permissions, verified the disk, (and there were no problems) and i also ran a full hardware test in tech tool deluxe and everything passed.

    i noticed my computer was running a little slow, so i opened up the activity monitor and i see that this process called "UniversalSerialB" (which is the USB) is using the CPU between 60% and 80%. (There is a screenshot attached of the activity monitor window in a PNG format)

    I'm not using the USB anymore than i usually do, and when i usually use it and not doing anything, it uses no cpu speed. And now nothing is happening on my USB bus besides just perefials being plugged in.

    Wierd.

    I would appreciate some responses.

    Thanks very much for all of your help.

    Julian

    :apple:
     

    Attached Files:

  2. Eidorian macrumors Penryn

    Eidorian

    Joined:
    Mar 23, 2005
    Location:
    Indianapolis
    #2
    Have you tried killing it? It starts up rather early so I'd check your printer driver and login items.
     
  3. diehardmacfan thread starter macrumors regular

    Joined:
    Mar 12, 2007
    #3
    i did give you the full process name
    it is "UniversalSerialB"
    that is exactly what it is

    its not shortened at all
     
  4. diehardmacfan thread starter macrumors regular

    Joined:
    Mar 12, 2007
    #4
    here are some other screenshots that might be helpful
     

    Attached Files:

  5. diehardmacfan thread starter macrumors regular

    Joined:
    Mar 12, 2007
    #5
    yes i have tried killing it

    it wont stop

    and i have no printer attached and none of my login items have anything to do with USB
     
  6. plinden macrumors 68040

    plinden

    Joined:
    Apr 8, 2004
    #6
    I think you misunderstood Eldorian. "killing" a process means either doing a ForceQuit on it in Activity Monitor or typing "kill <pid>" in Terminal.

    Hmm, it's a root process you probably can't kill it directly. Are you running an admin account?
     
  7. Eidorian macrumors Penryn

    Eidorian

    Joined:
    Mar 23, 2005
    Location:
    Indianapolis
    #7
    After having a few more minutes to think about it, it's the UniversalSerialBus service. At least that's my guess. I dug around in /System/Libary with no real luck.

    No clue why it's doing that.
     
  8. diehardmacfan thread starter macrumors regular

    Joined:
    Mar 12, 2007
    #8
    yes i am

    but u reminded me of something

    i will try logging into my root acount and try it from there

    i will post my results in a minute
     
  9. bbarnhart macrumors 6502a

    bbarnhart

    Joined:
    Jan 16, 2002
    Location:
    Stilwell, Kansas
  10. Eidorian macrumors Penryn

    Eidorian

    Joined:
    Mar 23, 2005
    Location:
    Indianapolis
    #10
    It looks like a stalled CoreService to me. It's trying to do something at boot and won't give up.
     
  11. diehardmacfan thread starter macrumors regular

    Joined:
    Mar 12, 2007
    #11
    it could be
    when i am done with what i am doing on the computer now than i will try restarting the comp now

    but i logged into my root account and tried to force quit that task but it didnt work

    and replying to what that other guy said about the USB port being damaged:

    it is possible that the water could have damaged the USB port while it was in, but i am using things now that are plugged into both USB ports on my ibook and everything is working fine
     
  12. diehardmacfan thread starter macrumors regular

    Joined:
    Mar 12, 2007
    #12
    i'm getting syntax errors in terminal when trying that
     
  13. plinden macrumors 68040

    plinden

    Joined:
    Apr 8, 2004
    #13
    What exactly are you typing? <pid> means the process id - which is 265 from your last screenshot. So you should type:
    sudo kill 265

    and if that doesn't work:
    sudo kill -9 265

    Since it's a root process you need su privileges, hence the sudo.
     
  14. diehardmacfan thread starter macrumors regular

    Joined:
    Mar 12, 2007
    #14
    it didnt work

    it pormpted it for my password and then after i entered it, the process was still running
     

Share This Page