FREQUENT Kernel panics Motion 3 in 10.4 PPC G5

[Zak Mussig]

Hey Herb,

Did you send this error report to Apple? Their engineers will obviously be able to decipher this better than anyone on the forum.

I’m assuming you’re running QuickTime 7.3 since you have the latest Motion update. If you downloaded the Motion update directly rather than using System Update and still have QT 7.2 or lower, that could be your problem. That said, some bug affecting QT 7.3 on 10.4.x could also be the issue. These are both blind guesses.

I’d suggest to boot using your last system backup and see if that version of Motion still works for you. If that doesn’t panic then stick with it until a new round of updates come out, and even then read the release notes before installing to see if they’ve even addressed your issue.

Good luck,
Zak

[Herb Tarlek]

Yeah, I’ve just had 2 similar crash but in FCP this time. I’m thinking of using 10.5.1 which I have installed on my second internal hard drive.

I need to know one thing before I do, though, by opening a project in 10.5, will I be able to re-open it in 10.4 afterwards?

[Kevin Hamm]

That’s a good question, and right now, the answer is “maybe”. I’ve got a fully up-to-date 10.5.1 OS with FCStudio on it, FCP is 6.0.2, and at work we have a 10.4.11 with FCStudio updated on it to FCP 6.0.2 – and the 10.4.11 machine’s version of Final Cut says that it “cannot read or the file is from a newer version of Final Cut Pro”.

So, if you’re going to do major editing, you might want to do your Motion stuff in leopard, and then reboot into Tiger and import them into your timeline then. Shouldn’t be a problem. You might test, this, tho, by simply rebooting to leopard, building a quick Motion project, and then go back to Tiger to import and render/export as you’re going to do with your final.

I will add, however, that my leopard machine is both faster and more stable than 10.4.11 has left the work machine, and they are basically identical G5s. You might just take the plunge if you have the time to do so.

[Herb Tarlek]

Thanks, and I sure will, I’m just waiting to finish this project which is 90% done (1h40min) before I upgrade.

[Kevin Hamm]

Once you’ve got the solution working for you, be sure to let us all know what and how it did – you never know when your solution will be a life saver for someone else.

Good luck!

kev~!

[Kevin Hamm]

While you’re waiting to finish this project before you upgrade, I thought of something else that might work for you. i’m going to presume that you have three 1GB sticks in your memory slots. Actually, no, I’m going to hope you don’t, and that instead you have two 512MB sticks and two 1GB sticks in the computer. Doesn’t really matter, just check to see if you have to have parallel memory sticks in before you try the following:

Remove a stick of RAM (or a pair of sticks, if you have to for it to work) and try playing in motion after you restart. If it crashes, put that RAM back and take out another. See if you’ve got bad RAM that the system isn’t catching at startup.

If you do, just get a new RAM stick, they be cheap.

[Sam Zimman]

Hey Herb I have a very similar system with a very different problem. I can’t get 3rd party plug-ins to work and I think it’s a conflict between Motion and the ATI card. So that might be your issue.

Try this, just to see if it works. Download the free trial of BCC5FXPlug or Magic Bullet Looks. When I apply BCC to a clip it makes it go black. When I apply Looks and launch the plugins interface it does not pass the image through to the Looks Builder. However, both of these plugin sets work fine in FCP. Like I said previously, I think this is a conflict between Motion and the ATI card, but nothing is confirmed yet.

[Rick Stokes]

Hi, I found this thread when searching for a very similar problem.
Sudden and hourly crashes ranging from the “you need to restart this computer” message, to sudden freezing or disappearing of one of my 2 screens.
I usually send Apple the crash report each time I restart if it stays alive long enough.

After trying reinstalling OSX10.4 from the system disc and the problem still remains, I’ve been examining my crash logs, here’s the latest:

———————–

panic(cpu 1 caller 0x54E33AEC): DART entry exception: PCI0 write logical page 0x00000

Latest stack backtrace for cpu 1:
Backtrace:
0x00095564 0x00095A7C 0x00026838 0x54E33AEC 0x5D316D70 0x5D316DA8 0x5D2F1048 0x002CDC8C
0x002CCB54 0x000A9654
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleGPIO(1.1.8)@0x5d314000
dependency: com.apple.driver.IOPlatformFunction(1.7.0b1)@0x54e1d000
com.apple.driver.MacIOGPIO(1.1.8)@0x5d2ef000
com.apple.driver.AppleMacRISC4PE(1.6.0d9)@0x54e2d000
dependency: com.apple.iokit.IOPCIFamily(1.6)@0x54e0f000
dependency: com.apple.driver.IOPlatformFunction(1.7.0b1)@0x54e1d000
Proceeding back via exception chain:
Exception state (sv=0x014AFC80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
————————
Thanks for the suggestion of pulling RAM modules out – I’ll try that next, if this doesn’t work:
Due to just one of my screens going blank in some crashes, perhaps the problem is my video card.
I gave the board a jiggle and unplugged the screen plugged into the special Apple monitor out port (AD?).
I’ve had time to type this, so it’s looking good so far.

Any suggestions gratefully received.