003 Rack Plus/ Mavericks Kernel_Task issue...please help

[AntonTsygankov]

Hi everyone, sorry for making a duplicate thread, I think my previous post belongs to this forum.

My name is Anton, I live in Moscow Russia and I'm sorry for my English.

Guys, it seems that I'm having same Kernel_Task problem as many 003R users out here.

I have installed Mavericks OS, (10.9.2) and now I have and PT11.1.2 and the newest Avid driver installed for my 003Rack plus. My Mac book is Mac book Pro Mid 2010 with I7. My Kernel_task is going up to 110% when I have my 003 Rack+ attached and powered-on even when Pro Tools software is off.

I mean - when I plug in my firewire cable into macbook (I have 2 to choose from, it's not the cable issue) - the Kernel_task go nuts, and jumps from 2-3% up to 70-80%. My CPU fan starts to work (with PT11 off) and when I start PT11 - it goes crazy. I get "CPU overload" message in PT11 even when there's only three or four plugins enabled. Internal PT system usage monitor shows only like 2% of CPU usage. I was able to use like 40 plugins at the same time at 10.6.8.

If I plug my firewire cable out of it's port - my Kernel_task goes down from 70% to 2-3% in a few seconds.

And if I swap my 003 with my Motu Ultra Lite Firewire - the problem goes away too. The Kernel task stays at about 2-7% with Motu card enabled.

I guess there's something wrong with the drivers.

Guys, do you have any suggestions what should I do? Is there's different drivers out there?

Regards,
Anton.
Edit/Delete Message

[joey8989896]

Can a moderator please address this issue? I along with others have the same problem. Here are some threads about this topic:

http://duc.avid.com/showthread.php?t=342284
http://duc.avid.com/showthread.php?t=344790
http://duc.avid.com/showthread.php?t=342476
http://duc.avid.com/showthread.php?t=342459

Little different: http://duc.avid.com/showthread.php?t=351013

http://duc.avid.com/showthread.php?t=341487

[JoelG]

I've forwarded this on, I'll see if I can get any info.

Joel

[joey8989896]

Thank you so much Joel

[Bill Denton]

Originally Posted by AntonTsygankov

Hi everyone, sorry for making a duplicate thread, I think my previous post belongs to this forum.

My name is Anton, I live in Moscow Russia and I'm sorry for my English.

Guys, it seems that I'm having same Kernel_Task problem as many 003R users out here.

I have installed Mavericks OS, (10.9.2) and now I have and PT11.1.2 and the newest Avid driver installed for my 003Rack plus. My Mac book is Mac book Pro Mid 2010 with I7. My Kernel_task is going up to 110% when I have my 003 Rack+ attached and powered-on even when Pro Tools software is off.

I mean - when I plug in my firewire cable into macbook (I have 2 to choose from, it's not the cable issue) - the Kernel_task go nuts, and jumps from 2-3% up to 70-80%. My CPU fan starts to work (with PT11 off) and when I start PT11 - it goes crazy. I get "CPU overload" message in PT11 even when there's only three or four plugins enabled. Internal PT system usage monitor shows only like 2% of CPU usage. I was able to use like 40 plugins at the same time at 10.6.8.

If I plug my firewire cable out of it's port - my Kernel_task goes down from 70% to 2-3% in a few seconds.

And if I swap my 003 with my Motu Ultra Lite Firewire - the problem goes away too. The Kernel task stays at about 2-7% with Motu card enabled.

I guess there's something wrong with the drivers.

Guys, do you have any suggestions what should I do? Is there's different drivers out there?

Regards,
Anton.
Edit/Delete Message

Anton...

I do not have a solution for your problem, but I do have a warning...you should not "hot plug" the 003R Firewire cable as it can damage the 003R.

Always make sure both the 003R and your computer are turned off before plugging/unplugging the Firewire cable. If you're "plugging", with both devices turned off connect the Firewire cable, then turn the 003R on, wait a couple of seconds (I usually wait until the Mute light illuminates on the 003R), then turn the computer on.

And good luck with finding a solution to your problem...I'm sure others here can help...

[joey8989896]

Originally Posted by JoelG

I've forwarded this on, I'll see if I can get any info.



Joel

Any info yet?

[AntonTsygankov]

Nope...((

[adamqlw]

I'm suffering from this as well... Didn't pick it up until after I upgraded to ProTools 11, now I have a massive problem using my interface and I've sunk in the upgrade cost already. I know it's legacy hardware and not supported but is it really that hard to write functional drivers instead of releasing something that kills an entire core on its own?

Looking forward to an eventual fix (but I suppose I shouldn't hold my breath)

[adamqlw]

Still no info?

[soapfoot]

Hi, just checking to see if there is an update on this.

I'm experiencing the same issue, which is frustrating because it has made it impossible for me to work on my home setup (going between studio and home is a big part of my workflow).

Any update?