Firewire driver causes crash on wake up

Every time I wake up my Mac Pro I get a crash report, that Leopard quit. The culprit I have found out is the Apple driver for my Saffire audio device which uses the apple firewire. My only choice is never to let my mac sleep, which I find unacceptable.
Does anyone have an idea about a fix or wether apple has plans to update their firewire drivers?

If anyone did have an idea when an update was forthcoming, the Terms of Use of this forum, and their non-disclosure agreement would forbid them from saying.
I would say this, contact the manufactuers of Saffire Audio, and inform them their firmware needs to be updated for Energy Saver compatibility. Not all peripheral vendors know the Energy Saver standards that Apple uses.
In the meantime, you can use a Screen Saver instead of Energy Saver of a picture filling the screen with black, or download the freeware Mac Brightness. I can't find the link right now as Versiontracker appears to be down from where I'm at.

Similar Messages

Firewire Drive Causes Crash at Startup, Safe Boot OK

I have a LaCie External Drive that all of a sudden decided to start causing OSX to crash at startup. While connected booting normally brings up the "need to restart" screen, booting in Single User causes a Kernel Panic, Safe Boot is ok, Booting from Install Disk is ok, but as soon as I connect the drive it's "you need to restart..."
So far i have tried the following;
Zapped the PRAM, repaired permissions normally while disconnected, repaired permissions in Safe Boot while connected, and repaired permissions from Install CD while connected.
My question is of course, what can be causing this problem and how do I fix?
I have sifted through previous discussions but was unable to find an answer, so I apologize if this is a duplicate. Also, if anyone knows of a better category to list this I would appreciate input. Thanks!

DOH!
Like everything else in life, the simplest solution is best. after remembering that the drive is both USB and FW i dug up my cables and tried the USB connection and...all better. So yes, I guess this would prove that the FW port is to blame.
Thanks for the help!

Sleeping firewire drive causes system crash

I have a 320 GB external firewire seagate drive connected to my Dual Ghz Quicksilver G4. At least twice a day, when I try to access that drive, I experience a system crash, what I believe to be a kernal panic. I get a message telling me I need to shut my computer down and restart it. I am thinking this is not so good for my computer.
So, either the hard drive is the problem or it's the third party firewire card i have installed in one of my PCI slots. But here's the thing, other drives are connected to that card.
Would keeping the Seagate drive awake stop this from happening? It goes to sleep all the time. Have others experienced problems with the seagate drives? Should I stop using it?

Hi, Aaron. Welcome to the Discussions.
If you are seeing this message, that indicates a kernel panic.
There could be a problem with the FireWire drive or the card. If disconnecting the drive for a few days results in no additional panics, then it is the drive. For that, I'd contact Seagate. If not, the card becomes suspect. An examination of the panic log might prove helpful.
You can also try running Step 1 of the process specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ against the Seagate FireWire drive.
Checking the FireWire cables, trying different cables or ports, checking that the card is installed correctly, checking that you assembled the Seagate drive and enclosure correctly (sounds like you built the FW drive) are some other troubleshooting steps to consider. The FireWire enclosure itself may be defective.
See also my "Resolving Kernel Panics" FAQ. This FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics, including tips like those above.
My FAQ is a roadmap: start at the beginning and work through to the end, following the instruction in the order specified, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein.
You maybe unable to prevent the FireWire drive from sleeping. Secondary hard drives (second internal, as well as external drives) may not respect the "Put the hard drive(s) to sleep when possible" option if de-selected. I discuss this particular issue in my "Spinning Beach Ball Of Death (SBBOD)" FAQ, specifically in the section entitled "SBBOD spins for 30-35 seconds. You may hear your hard drives spinning up."
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

LaCie 500GB External Firewire 800 causes crash every time its plugged in???

My LaCie 500GB Firewire External hard drive causes the computer to freeze every time I plug it in.
I just switched back to Mac from Win XP, where the LaCie was used for almost a year without a single problem. Supposedly, since it is formatted for XP use, it can simply be plugged in to my G5 (dual 2.3, 4BG RAM) and work just fine.
I've upgraded to 10.4.4 and still have issues. I've read this is a 'kernal panic' issue, etc.
What is the solution? I can't even plug it in and reformat it - as soon as it's plugged in the Mac collapses; the screen goes 'grey tinted' and an error message appears telling me to hold down the restart button and restart the computer. If I leave the drive plugged in, as soon as I've signed in on the restart, it crashes/freezes/collapses again, same error (i.e. it's circular).
There seems to be no solution. Any help MUCH appreciated!
Thanks,
Sarge

Welcome to Apple Discussions!
First find out if this is a Firewire 800 or 400 problem. Try connecting a Firewire 400 cable to the drive if it supports it. If it only has Firewire 800 ports, you may want to get a Firewire 400 drive to experiment to see if that's all the problem is.
After a forced reboot, it is also always wise to repair the directory if you are backed up:
http://docs.info.apple.com/article.html?artnum=106214
If it detects issues on your source drive that it can't repair, and you are backed up, then I would use Alsoft Disk Warrior.
If it detects no issues, then the problem probably resides in either the cable or the drive you are connecting to. Try a little process of elimination.

Firewire drives cause kernel panic on PPC, not Intel

I'm trying to get three firewire drives to work on a PowerMac G5. Before updating to 10.4.8, they worked individually, but not chained together. Now, if you connect any one of them, the system has a kernel panic. They would cause the panic on the earlier version of 10.4 when chained together. Everything works perfectly on a MacBook and a MacBook Pro, both running 10.4.8.
Below are the notes I took on the three drives as I was troubleshooting. All three are from Maxtor.
Drive 1:
300GB
EDA EB300G0160101
Has a filesystem, but Disk Utility claims there is no partition. It mounts on an Intel Mac, but causes a kernel panic on a G5.
Filesystem is Mac OS Standard
G5 System will panic while booting if the drive is connected and turned on.
G5 panics when trying to mount drive.
Drive 2:
200GB
EDA Ay200A0260101
Has a Mac OS Extended filesystem
G5 System will panic while booting if the drive is connected and turned on.
G5 Panics when trying to mount drive.
Drive 3:
300GB
EDA BA300D0080101
Has a Mac OS Extended (Journaled) filesystem.
G5 System will panic while booting if the drive is connected and turned on.
G5 panics when trying to mount drive.
Because of the change when 10.4.8 was installed, I suspect this is a driver problem. It could also be a controller problem that just happened to get worse when the update was done.
I ran the Apple Service Diagnostic on this machine and was unable to find anything wrong since I replaced both CPUs.
Any ideas?
PowerMac G5 dual 1.8 Mac OS X (10.4.8)

If the drives were formatted on the Intel Mac then they will have a GUID partition map installed on the drive. PPC Macs will not understand the GUID partition scheme which may be the root cause of your problem. If you want to use the drives on both platforms they need to be re-partitioned using the APM partition scheme.
Also, you should not use Mac OS Standard. You should use Mac OS Extended (Journaled.)

Copy from xServe RAID to firewire drive is crashing my OS...

Fellow mac users,
I am a relatively new OS X system admin and I am having a hard time copying files from my xServe RAID to a firewire drive to do an intermittent backup. When I try to copy the files over it crashes the OS without fail. I was wondering if anyone has ever heard or seen of this before? It's rather discouraging when all I'm trying to do is get a quick backup of the RAID which is only 300 gb in size currently.
Our hardware is very good, we have a dual 2.3 G5 model with 3 gb of RAM so I know the hardware can handle a simple finder copy. The only idea I have is to do a "ditto" in the terminal. I thought I'd ask for input from the resident apple sages before trying that. Does anyone have any suggestions or ideas for me?
Thanks for any help,
Thomas
xServe Dual G5 Mac OS X (10.4.5)

Be sure you have the external drive connected when you boot from the installer disc. Use the OS X Installer One disc that came with your MacBook. After you boot from the installer and select your language select Disk Utility from the Utilities menu.
After DU loads select the drive entry (mfgr.'s ID and drive size) for the external drive from the left side list. Click on the Partition tab in the DU main window. Click on the Options button, select the GUID partition scheme and click on the OK button. Set the Format drop down menu to Mac OS Extended (Journaled) and the number of partitions from the Partition drop down menu to one (1). Click on the Partition button. Wait for the volume to mount on the Desktop.
Quit DU and return to the installer. Proceed with the OS X installation. When you get to the part where you select a destination click on the icon for the external hard drive.

Second Firewire drive causes first to be disconnected

Having transferred a load of stuff off the main HD onto an external Firewire drive, I decided it would be prudent to have a backup schedule for the new drive as well as the main one. However, whenever I connect and power up a second Firewire drive, the first is disconnected and I get the message that it's a bad idea to disconnect drives without unmounting them first. I ended up having to connect the backup drive via the powered USB hub and watch a very slow backup take place.
If you can't run two drives off an iMac, what's the point of having two Firewire ports...? (The external drives are both powered by "bricks" so I'm surprised there's a problem.)
Is my Mac a lemon? (Cos with all the problems I've been having I'm beginning to think so!)
Would an external (powered) Firewire hub be a good idea in this case?

Have you tried daisy-chaining them? That is, plugging one drive into the other, then into the computer? In any case, a fire wirehub wouldn't be a bad idea.

External USB & Firewire drives causing system to stall

Hi there,
I have zapped the PRAM and reset the system controller.
I have two external hard drives, one USB and one Firewire, connected directly to the computer. I run into the frequent problem where either (or both) of the hard drives are keeping the computer from switching users, although they do seem to allow the computer to fully boot. However, if I try to change users, it will not allow me to get to the login screen without shutting the hard drive off. We also run into problems where the hard drives stall the system... just causes the whole computer to lock up. Any ideas?
Thanks!

With a brand new iMac, make use of the free 90 day Apple support. In the US (800) APL-CARE (800-275-2273)

Optical drive causes crash every time

I installed a DVD burner (NEC DVD_RW ND-3540A) in place of my DVD-RAM drive. The new drive is set as a master. The drive works fine, except if I dont eject a disc immediately after burning, the entire bus goes down. I am not able to shutdown, restart or anything. The only way to fix the issue is to manually restart with he reset button. Any suggestions would be appreciated.

Welcome to Apple Discussions!
First find out if this is a Firewire 800 or 400 problem. Try connecting a Firewire 400 cable to the drive if it supports it. If it only has Firewire 800 ports, you may want to get a Firewire 400 drive to experiment to see if that's all the problem is.
After a forced reboot, it is also always wise to repair the directory if you are backed up:
http://docs.info.apple.com/article.html?artnum=106214
If it detects issues on your source drive that it can't repair, and you are backed up, then I would use Alsoft Disk Warrior.
If it detects no issues, then the problem probably resides in either the cable or the drive you are connecting to. Try a little process of elimination.

Satellite C660-23M - driver causing crash when program starts

I have loaded a CAD program on my new 64bit laptop, the program will start then stops and windows closes it. In the crash reports the modules ntddll.dll and aticfx.dll both seem involved. Could there be some conflict, can I update a driver somehow?
I have seen a report on a gaming website that the aticfx.dll isa the problen on the c660 range.
Please help or the machine goes back to the shop.
PS I have tried running in compatibility mode and disabling antivirus but the problem is unchanged
Regards Ian

Hi
I think the CAD application is not fully compatible with the preinstalled graphic card driver.
The ntddll.dll files is part of the windows system and aticfx.dll file seems to be a part of the graphic card driver and therefore I think that you would need to use another graphic card driver.
The notebook seems to support an Intel HM55 HD graphic card. Try to update the driver using the newest version from the Intel page.

IdeaCenter - USB thumb drives cause crash/shutdown

Firstly , I have this desktop
IdeaCentre B540 - 25681JU
Every now and then when I insert a thumb drive in to the USB the fan will kick in on full force for about 2 seconds and then the computer will shut down. Ever since I bought the machine new.
It's not limited to a single thumb drive, it has occurred with both a Kingston and Patriot brand.
When ever I have lined the drive up and inserted it quickly and as straight as possible nothing has happened; it generally seems to occur when I am more casual about inserting it with less concentration.
It has probably happened about 10-12 times in 6 months- which doesn't sounds like a lot, but its not right all the same and it would be more if I were more lax about it.
Any ideas? Or others with the same problem?
Damien

hi damien5000,
Welcome to the Lenovo Forums
Can you try to:
1. Boot the PC into the BIOS by continuously tapping F1 on startup
2. When you're in, try to insert the flashdrive
If the unit shuts down while inserting it in carefully, there's a big possibility that something is shorted inside (probably the I/O board) that's causing the PC to shut down and you need to contact lenovo for service.
If the unit doesn't shutdown, try to boot into safe mode and try to insert and access the flashdrive. If everything's ok, perform a clean boot, restart the computer in normal mode and observe the PC.
Let me know your findings
Cheers
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Connecting firewire disk causes coreaudio to crash

I have a Western Digitial "my book" firewire drive which worked perfectly under Tiger. I just upgraded to Leopard, after waiting a few months to make sure the early bugs got worked out. I guess I was premature in upgrading? Has anyone else seen the following firewire behavior:
I have an audio stream (last.fm) playing over the digital line out. Everything is fine. As soon as I turn on my Western Digital drive (connected via firewire 800) the audio stops, and when I look at the console, there are continuous error messages to the effect that coreaudio has crashed due to a bus error. As soon as I dismount and turn off the firewire drive, coreaudio starts working fine again. This is completely reproducible -- connecting the firewire drive always causes coreaudio to crash. This NEVER happened under Tiger, so it's not a hardware problem. (And I am not using any WD drivers, only stock Apple firewire drivers. And the system profiler sees the WD drive just fine.)
I see that there are LOTS of firewire problems noted on the forum. Has anyone seen this interaction with coreaudio? Does anyone have a suggested fix?

Thanks for the suggestions. I don't particularly like this WD MyBook; its fans are too noisy and it runs hot, but at least under Tiger it performed just fine.
I downloaded and installed the latest WD firmware (104a) but that didn't help. I noticed that several other MyBook models have had recent firmware updates targeted specifically at Leopard, but not my model (the Pro Edition II.)
But I'm sure this is mostly a Leopard software issue -- the exact same crash to coreaudio occurs if I plug in my HV20 camera. Even if the WD drive is not hooked up.
I have not tried to "reset the firewire bus" -- I'll have to find out how to do that.
--david

I have a new 2.0GHz Intel Core i7 macbook pro and my external firewire drive is causing the laptop to lock up

I have a new 2.0GHz Intel Core i7 macbook pro and my external firewire drive is causing the computer to lock up. The drive seems to sleep and then never wakes and the laptop locks up. I've had this drive connected to an older 2.0 core duo macbook pro and a 3.0GHz quad core macpro with no issues. It's a ministack v3 drive, 2GBs, fw400+800, sata and usb. Any ideas? And can I stop the drive from going to sleep?
Thanks.

Check with the drive's manufacturer to see if they might have a firmware update for the enclosure; it sounds like the enclosure's firmware isn't properly detecting the FireWire wakeup sequence.
Obviously this could also be a bug with the new MBP's firmware, so it wouldn't hurt to ask the Genius Bar at your local Apple Store; in particular, ask them to show you that the sleep/wakeup sequence on your MBP works with some other FireWire drive.

Oxford 912 Firewire Drive Freezes on Wake

I have an OWC 320 GB FW400/800 drive that will no longer wake properly. The drive will mount properly and I can use it as long as it stays active. Once the drive goes to sleep, it will not wake. This drive works fine on 10.4.11 or earlier. According to OWC, there is an issue with some firewire drives that Apple is aware of and working on. Here is the relevant portion of the syslog:
Apr 6 13:28:43 ep-mbook kernel[0]: disk5s10: I/O error.
Apr 6 13:28:43 ep-mbook kernel[0]:
Apr 6 13:28:43 ep-mbook kernel[0]: BlkNum 2325] [FSLogMsgID 2114434281] [FSLogMsgOrder First]
Apr 6 13:28:43 ep-mbook kernel[0]:
Apr 6 13:28:43 ep-mbook kernel[0]: disk5s10: media is not present.
Apr 6 13:28:43 ep-mbook kernel[0]:
Apr 6 13:28:43: --- last message repeated 1 time ---
Apr 6 13:28:43 ep-mbook kernel[0]: disk5s10: media is not present.
Apr 6 13:28:43 ep-mbook kernel[0]:
Apr 6 13:28:43: --- last message repeated 1 time ---
Apr 6 13:28:43 ep-mbook kernel[0]: disk5s10: media is not present.
Apr 6 13:28:43 ep-mbook kernel[0]:
Apr 6 13:28:50: --- last message repeated 1 time ---
Apr 6 13:28:50 ep-mbook kernel[0]:
Apr 6 13:28:50: --- last message repeated 1 time ---
Apr 6 13:28:50 ep-mbook kernel[0]: disk5s10: media is not present.
Apr 6 13:28:50 ep-mbook kernel[0]:
Apr 6 13:28:50: --- last message repeated 1 time ---
Apr 6 13:28:50 ep-mbook kernel[0]: HFS: err 6 reading VH blk (Mercury300)
Apr 6 13:28:50 ep-mbook kernel[0]: disk5s10: media is not present.
Apr 6 13:28:50 ep-mbook kernel[0]:
Apr 6 13:28:50: --- last message repeated 1 time ---
Apr 6 13:28:50 ep-mbook kernel[0]: HFS: err 6 reading VH blk (Mercury300)
Apr 6 13:28:55 ep-mbook /usr/sbin/spindump[58895]: process 3274 is being no longer being monitored
This is from a chat with OWC tech support:
Jason Bohannon: There is no firmware updates for them. Some drives work fine, others don't. I'm not really sure what the root cause, just heard our tech manager saying it is a Leopard issue [as they work fine with tiger] and it is something which Apple is working on
Eric Paulsen: O.K. I'll just need to dismount this drive when finished. I'll move it into an archival use, and use it only for periodic archival. Do you have any certified drives for Leopard? Many of your web pages still refer to 10.4.x as the latest OS.
Jason Bohannon: They all work with leopard, but I believe the reason for the pages not being updated is the issue you're having. some drives work fine, others, from the same batch, have issues. As it is an OS problem and not a hardware problem, I think that's why it still lists tiger as the most updated OS. Once these issues/bugs go away, I would think the product manager would update the page. Anything with firewire has a chance to have that problem, regardless of what drive it is.
Eric Paulsen: Bummer. Well, I'll hold off purchasing for the time being, and wait and see if 10.5.3 addresses it. Thanks for your help.
Is this for real or should I be hounding OWC some more?

Thanks for the suggestions, I can't help thinking some basic fault exists within this iMac. It was purchased about 6 weeks ago, and as far as I know was a 2008 build. Not sure how the check this but I understand the serial number is on the base.
The article seem to refer to iMac's with this problem as of, mid 2007 vintage, well that's not mine.
I plan to call Apple and may look at a replacement model, but would appreciate any other thoughts.
Not too keen either on loosing 'personal' settings, whichever they may be.

Crashes when Firewire Drives are mounted

For some reason now Logic crashes (hangs...not responding) when i boot Logic with my one firewire drive mounted. When i unmount the drive and then boot Logic it works fine. THen i re mount it and open my project.
Is there a fix for this?

Here's what I think is going on...
You wrote:
If i boot logic and then mount the drive it works fine.
Logic keeps a file (somewhere) that remembers the most recently opened songs/projects. I think this file is corrupt. I have no idea what the file is called, where it's located, but I think it's corrupt. Bascially, when you launch Logic but the drive to which a recent song isn't mounted/not available, that song will disappear from Logic's recent song list. But I have the feeling that Logic hasn't totally forgotten about the existence of that song. So when the drive is mounted and Logic loads up, it might just be trying to find the drive where the song lives but something gets screwy in the process.
Here's what I suggest:
a) quit Logic if it's running
b) mount the drive
c) copy the entire project to your internal HD
d) launch Logic
e) open the song from your HD
f) if this works without crashing, re-save the project to your FW drive under a new name
g) go to Logic's recent song list and count the number of songs in the list. Let's say it's 20 songs in the list...
h) hold option for one second and create a NEW song (this will be Logic's "default" song)
i) save it to your FW drive as a simple song (not project) called "a"
j) now save it 20 more times, changing the name each time, i.e., "b", "c", etc. What you're attempting to do is completely clear Logic's recent song list of all previous song titles with something known to be "benign"
k) re-load your real song as saved to your FW drive in step F above
l) if this works, quit Logic without saving
m) re-boot the computer
n) make sure the FW drive is mounted
o) launch Logic and load the song from step F from the FW drive
If all that works, then I think my theory is right about the recent file list being corrupt.
If it doesn't work, well, [Elmer Fudd = ON] I twied and I twied...

Firewire driver causes crash on wake up

Similar Messages

Maybe you are looking for