Firewire: kernel panic in: fwnet_write_complete

The system falls to kernel panic when I copy lots of files from laptop via firewire.
kernel is 2.6.32.2-2
# lspci
04:03.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70)
don't have digital cam to screenshot it:
Call Trace:
[<xxxxxxxx>] ? ip_rcv_finish+0xeb/0x390
[<xxxxxxxx>] ? close_transaction+0xda/0xf0 [firewire_core]
[<xxxxxxxx>] ? handle_at_packet+0xa1/0x100 [firewire_ohci]
EIP: [<xxxxxxxx>] fwnet_write_complete+0x2c/0x160 [firewire_net] SS:ESP 0068:f7079e40
UPD:
lesser MTU value has no effect.
no kernel panic with "-maxcpus=1" boot option, but that surely inacceptable.
Last edited by leniviy (2010-01-10 19:56:06)

Last edited by leniviy (2010-01-13 20:57:26)

Similar Messages

MBP / Firewire - Kernel Panic on wakeup

I guess this issue is reported over and over again by now.
My MBP (late 2007) has a problem with Firewire Audio-Interfaces.
I use a Terratec Phase 24 and Apogee Duet and everytime I put the Computer to sleep it causes a Kernel-Panic on wakeup. I've submitted the report for about 60+ times to apple. Still no fix so far.... And it's a well known issue around the net. Even Apogee and Terratec say that there's a bug in the core FWAudio from Apple.
This is kinda annonying and I think the mac has always been a professional tool for professional sound artists - but this bug makes my MBP useless
Please Apple - Do something about it!
If anyone might have any hints - just shout
Here's the exact Problem Report:
+Thu Apr 17 09:11:09 2008+
+panic(cpu 0 caller 0x001A8C8A): Kernel trap at 0x071a1d28, type 13=general protection, registers:+
+CR0: 0x8001003b, CR2: 0x1a20e000, CR3: 0x01463000, CR4: 0x00000660+
+EAX: 0x071a2880, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x124a08c0+
+CR2: 0x1a20e000, EBP: 0x5b7bfd18, ESI: 0x1258df80, EDI: 0x07347000+
+EFL: 0x00010202, EIP: 0x071a1d28, CS: 0x00000008, DS: 0x06b60010+
+Error code: 0x00001000+
+Backtrace, Format - Frame : Return Address (4 potential args on stack)+
+0x5b7bfad8 : 0x12b0f7 (0x4581f4 0x5b7bfb0c 0x133230 0x0)+
+0x5b7bfb28 : 0x1a8c8a (0x461720 0x71a1d28 0xd 0x460ebc)+
+0x5b7bfc08 : 0x19ece5 (0x5b7bfc20 0x80 0x5b7bfd18 0x71a1d28)+
+0x5b7bfc18 : 0x71a1d28 (0xe 0x48 0x5b7b0010 0x420010)+
+0x5b7bfd18 : 0x98cb03 (0x7347000 0x297 0x5b7bfd48 0xffffffc2)+
+0x5b7bfd88 : 0x99131a (0x7347000 0x0 0x0 0x5b7bfe1c)+
+0x5b7bfe38 : 0x97df72 (0x7347000 0x48 0x530010 0x46a5f000)+
+0x5b7bfe58 : 0x967196 (0x78fa700 0x46a5f000 0x9a1e40 0x12f2f2e8)+
+0x5b7bfe88 : 0x966f77 (0x46a5f000 0x1 0xde 0x19ed70)+
+0x5b7bfea8 : 0x9674dd (0x46a5f000 0x0 0x206 0x0)+
+0x5b7bfec8 : 0x964e5b (0x46a5f000 0x9aa1f8 0x5b7bfef8 0x403d91)+
+0x5b7bfef8 : 0x42028d (0x46a5f000 0x7923000 0x0 0x0)+
+0x5b7bff48 : 0x964fa7 (0x70ba9c0 0x964d2e 0x7923000 0x0)+
+0x5b7bff78 : 0x13ea4a (0x46a5f000 0x7215920 0x1a236f 0x12f2f2e8)+
+0x5b7bffc8 : 0x19eadc (0x0 0x0 0x1a20b5 0x129db5d0)+
+Backtrace terminated-invalid frame pointer 0+
+Kernel loadable modules in backtrace (with dependencies):+
com.apple.driver.AppleFWAudio(2.4.0fc8)@0x95c000->0x9aafff
+dependency: com.apple.iokit.IOFireWireFamily(3.4.0)@0x727000+
+dependency: com.apple.iokit.IOFireWireAVC(2.2.1)@0x935000+
+dependency: com.apple.iokit.IOAudioFamily(1.6.4b7)@0x945000+
+BSD process name corresponding to current thread: kernel_task+
+Mac OS version:+
9C7010
+Kernel version:+
+Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386+
+System model name: MacBookPro3,1 (Mac-F4238BC8)+

I guess this issue is reported over and over again by now.
My MBP (late 2007) has a problem with Firewire Audio-Interfaces.
I use a Terratec Phase 24 and Apogee Duet and everytime I put the Computer to sleep it causes a Kernel-Panic on wakeup. I've submitted the report for about 60+ times to apple. Still no fix so far.... And it's a well known issue around the net. Even Apogee and Terratec say that there's a bug in the core FWAudio from Apple.
This is kinda annonying and I think the mac has always been a professional tool for professional sound artists - but this bug makes my MBP useless
Please Apple - Do something about it!
If anyone might have any hints - just shout
Here's the exact Problem Report:
+Thu Apr 17 09:11:09 2008+
+panic(cpu 0 caller 0x001A8C8A): Kernel trap at 0x071a1d28, type 13=general protection, registers:+
+CR0: 0x8001003b, CR2: 0x1a20e000, CR3: 0x01463000, CR4: 0x00000660+
+EAX: 0x071a2880, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x124a08c0+
+CR2: 0x1a20e000, EBP: 0x5b7bfd18, ESI: 0x1258df80, EDI: 0x07347000+
+EFL: 0x00010202, EIP: 0x071a1d28, CS: 0x00000008, DS: 0x06b60010+
+Error code: 0x00001000+
+Backtrace, Format - Frame : Return Address (4 potential args on stack)+
+0x5b7bfad8 : 0x12b0f7 (0x4581f4 0x5b7bfb0c 0x133230 0x0)+
+0x5b7bfb28 : 0x1a8c8a (0x461720 0x71a1d28 0xd 0x460ebc)+
+0x5b7bfc08 : 0x19ece5 (0x5b7bfc20 0x80 0x5b7bfd18 0x71a1d28)+
+0x5b7bfc18 : 0x71a1d28 (0xe 0x48 0x5b7b0010 0x420010)+
+0x5b7bfd18 : 0x98cb03 (0x7347000 0x297 0x5b7bfd48 0xffffffc2)+
+0x5b7bfd88 : 0x99131a (0x7347000 0x0 0x0 0x5b7bfe1c)+
+0x5b7bfe38 : 0x97df72 (0x7347000 0x48 0x530010 0x46a5f000)+
+0x5b7bfe58 : 0x967196 (0x78fa700 0x46a5f000 0x9a1e40 0x12f2f2e8)+
+0x5b7bfe88 : 0x966f77 (0x46a5f000 0x1 0xde 0x19ed70)+
+0x5b7bfea8 : 0x9674dd (0x46a5f000 0x0 0x206 0x0)+
+0x5b7bfec8 : 0x964e5b (0x46a5f000 0x9aa1f8 0x5b7bfef8 0x403d91)+
+0x5b7bfef8 : 0x42028d (0x46a5f000 0x7923000 0x0 0x0)+
+0x5b7bff48 : 0x964fa7 (0x70ba9c0 0x964d2e 0x7923000 0x0)+
+0x5b7bff78 : 0x13ea4a (0x46a5f000 0x7215920 0x1a236f 0x12f2f2e8)+
+0x5b7bffc8 : 0x19eadc (0x0 0x0 0x1a20b5 0x129db5d0)+
+Backtrace terminated-invalid frame pointer 0+
+Kernel loadable modules in backtrace (with dependencies):+
com.apple.driver.AppleFWAudio(2.4.0fc8)@0x95c000->0x9aafff
+dependency: com.apple.iokit.IOFireWireFamily(3.4.0)@0x727000+
+dependency: com.apple.iokit.IOFireWireAVC(2.2.1)@0x935000+
+dependency: com.apple.iokit.IOAudioFamily(1.6.4b7)@0x945000+
+BSD process name corresponding to current thread: kernel_task+
+Mac OS version:+
9C7010
+Kernel version:+
+Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386+
+System model name: MacBookPro3,1 (Mac-F4238BC8)+

Booting from firewire target mode on a mac pro with kernel panic?

hello
i am wondering if it is possible to use firewire target mode to boot a mac pro that has never got past a multi language kernel panic on boot?
basically i have tried all the other options and cant get it to open the superdrive to insert my installation disk, as to repair the drivers with my snow leopard disk.
i've tried holding my mouse key down, the paperclip option on the drive itself and the firmware keycombo, so my idea is that the only way to fix it is with target mode. can this be done - and if so - could someone direct me towards a tutorial that will help me do this.
please advise if this is possible or if there is another method i should use? apart from taking it to the applestore (extreme last ditch option) i am quite low on ideas here.
many thanks!
p.s heres the message i wrote for the original problem which caused all the kernel panics;
"i recently bought a mac pro and upon starting it for the first time opted to transfer the all the data i could over via firewire from my macbook pro.
i used the standard 't' command with the firewire symbol.
Somewhere towards the end of the transfer (I am not sure at what pont - I wasnt there for all of it) - , the monitor went blank and the whole thing was unresponsive. my macbook's firewire sign continued to move around the screen.
after leaving it for some time i decided to turn off the macbook and then the mac pro.
i restarted the macbook and got some pretty crazy stuff happening to my calender - but so far everything seems to be fine.
i am more concerned about the "you need to restart your computer" message; this is the dreaded 'kernel panic' right?. i have never actually done anything with this computer yet, and it was purchased new."

"i recently bought a mac pro and upon starting it for the first time opted to transfer the all the data i could over via firewire from my macbook pro.
Never opt to transfer until you have insured it works fine for a couple days, I would never use Setup or Migration Assistant until such time, and I would have a bootable backup clone.
Try pulling all the hard drives from inside your Mac Pro and boot from OS X DVD - latest OS build.

Usb + firewire issues = kernel panic - help needed!!

Hello, and please forgive my english, I'll do my best!
So, i have a 1,25 Ghz MDD G4, with 2 x 256 Mo RAM sticks (at first), running mac OS 10.3.9.
As the original HD is too small, I work with my documents on an external firewire HD. The HD is plugged on a third party/PCI firwire card that went down.
On the same day I bought a new firewire card (trendNet, it was said to be mac compatible form mac OS 8.6) and 4 x 512 Mo of Ram (Hynix).
It worked just fine for a week and suddenly my mouse froze (and keyboard too > the mouse is plugged on the keyboard). Having no control on my mac (which seemed ok despite the usb deconnection) I had to hard reboot on the central Unit.
I unplugged the usb hub that occupied mu 2nd usb port (there was a wacom tablet and a flsh memory key on it). I left just the keyboard plugged (and mouse plugged on keyboard).
It was fine for... 2 or 3 hours and then it started again > mouse + keyboard deconnecting/freezing (the keyboard is a mac one, the mouse a microsoft one -optical-).
As the small red optical light of the mouse turns off when the mouse freezes I first thought the mouse or keyboard itself was the culprit.
I tested both of them them on a macbook and they worked just fine (never had a problem with them).
I ran disk utility, repaired the permissions. And it seemed better for a couple of hours.
When it happened again I unplugged the keyboard and plugged it on the 2nd usb port (which was free since I had unplugged everything else) > the mouse "came back to life" and I didn't have to reboot. But it happened again, like 2-3 times (every hour/half hour) until swapping the usb plug on the UC doesn't solve the problem anymore > hard reboot again...
Then I tried EVERYTHING
booting with techtool CD > everything ok, no pb found
running onyx to empty the cash and rerepair the permissions > ibid, no pb
resetting the PRAM with cmd-alt-p-r
resetting the PMU
resetting the usb and firewire ports after each hard reboot
cleaning the dust
removing my old scsi pci card (not used for ages)
moving my new firewire card on an another slot
installing a firmware update
nothing has solved the problem... it seems to arrive randomly, but mostly (more frequently) when working with several apps open.
The cursor seems to freeze for very very short periods (as a warning!) until it freezes for good > it's exactly as if the usb didn't deliver any electricity for micro laps of time (and it is the case I guess as my optical mouse light turns off).
So I change the usb plug into the other port and it works for a while, just as if only one usb port was functional at a time, but it always ends with a hard reboot (no choice).
It's always scary but it's also very annoying as my Western Digital Mybook external drive refuses to mount on desktop after hard reboots... I have to unplug it, replug it, restart etc... well this HD is a pain but I guess it's because it's in FAT 32 (since I forgot to format it when I bought it). So I don't bother too much about the HD itself, but however it seems that the firewire card suffers from this : I have a lot of trouble mounting 2 disks at a time (but with all this I need to backup!). It's like the fiwewire ports (of the pci card) suffered from the same pain as the usb : one at the time! and when I finally mount both external HDs, if I unplug one (after unmounting it and switching it off) the computer freezes.
Then one day I opened itunes, and... kernel panic...
That was 4 days ago I think and I've had like 3-4 KP since then (one a day). These kernel panic happen just as randomly as my usb deconnexions...
Today I tried my last chance : removing the new Hynix ram and putting back my 2 old 256 rams.
It was ok for a pair of hours and then > mouse freeze and kernel panic again...
I reaaally need help, I don't know what to do anymore. I've spent my last week unplugging usb plugs, opening my UC, repairing permissions etc...
now I feel helpless...
Here are some extracts of console logs I've had :
some :
May 14 22:57:42 localhost kernel: 0 0 AppleUSBCDCECMData: probe - provider doesn't want us to match
May 14 22:57:43 localhost kernel: 0 0 AppleUSBCDCWMCData: probe - provider doesn't want us to match
May 14 22:57:43 localhost kernel: 0 0 AppleUSBCDCACMData: probe - provider doesn't want us to match
tons and tons (but really!!) of these :
AppleUSBOHCI[0x1382800]::MakeDevice error setting address. err=0xe00002ed device=0x1f16000 - releasing device
May 14 23:08:26 localhost kernel: USBF: 715.217 IOUSBDevice[0x1654000]: Error (0xe00002ed) getting device device descriptor
May 14 23:08:26 localhost kernel: USBF: 715.248 IOUSBDevice[0x1654000]: Error (0xe00002ed) getting device device descriptor
May 14 23:08:26 localhost kernel: USBF: 715.279
IOUSBDevice[0x1654000]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:02 localhost kernel: USBF: 750.962 IOUSBDevice[0x13e5600]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:02 localhost kernel: USBF: 750.993 IOUSBDevice[0x13e5600]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:02 localhost kernel: USBF: 751. 24 IOUSBDevice[0x13e5600]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:02 localhost kernel: USBF: 751. 28 IOUSBDevice[0x13e5600]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:37 localhost kernel: USBF: 786. 65 IOUSBDevice[0x2056d00]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:37 localhost kernel: USBF: 786. 96 IOUSBDevice[0x2056d00]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:37 localhost kernel: USBF: 786.127 IOUSBDevice[0x2056d00]: Error (0xe00002ed) getting device device descriptor
May 14 23:09:37 localhost kernel: USBF: 786.131 IOUSBDevice[0x2056d00]: Error (0xe00002ed) getting device device descriptor
May 14 23:10:09 localhost kernel: USBF:
tons on this too :
2136.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 58749)
May 15 00:56:15 localhost kernel: USBF: 2137.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 59726)
May 15 00:56:16 localhost kernel: USBF: 2138.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 60703)
May 15 00:56:17 localhost kernel: USBF: 2139.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 61680)
May 15 00:56:18 localhost kernel: USBF: 2140.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 62657)
May 15 00:56:19 localhost kernel: USBF: 2141.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 63634)
May 15 00:56:20 localhost kernel: USBF: 2142.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 64611)
May 15 00:56:34 localhost kernel: USBF: 2156.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 13052)
May 15 00:56:35 localhost kernel: USBF: 2157.248 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 14029)
May 15 00:56:36 localhost kernel: USBF: 2158.272 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 15030)
May 15 00:56:37 localhost diskarbitrationd[87]: disk2s9 hfs 6950CF0C-02C2-3F9E-B5D5-EFC293557C95 PowerMac Software /Volumes/PowerMac Software
May 15 00:56:37 localhost kernel: USBF: 2159.272 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 16007)
May 15 00:56:38 localhost kernel: USBF: 2160.272 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 16984)
May 15 00:56:39 localhost kernel: USBF: 2161.272 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 17961)
May 15 00:56:40 localhost kernel: USBF: 2162.272 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 18938)
May 15 00:56:41 localhost kernel: USBF: 2163.272 AppleUSBOHCI[0x127f000] Watchdog detected dead controller (hcca #: 12727, hc #: 19915)
May 15 00:56:53 localhost syslogd: exiting on signal 15
May 15 01:17:06 localhost syslogd: restart
May 15 01:17:06 localhost syslogd: kernel boot file is /mach_kernel
May 15 01:17:06 localhost kernel: standard timeslicing quantum is 10000 us
May 15 01:17:06 localhost kernel: vmpagebootstrap: 125572 free pages
May 15 01:17:06 localhost kernel: migtable_maxdispl = 68
May 15 01:17:06 localhost kernel: IOKit Component Version 7.9:
May 15 01:17:06 localhost kernel: Wed Mar 30 20:07:52 PST 2005; root(rcbuilder):RELEASE_PPC/iokit/RELEASE
May 15 01:17:07 localhost kernel: 82 prelinked modules
May 15 01:17:07 localhost kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993
May 15 01:17:07 localhost kernel: The Regents of the University of California. All rights reserved.
May 15 01:17:07 localhost kernel:
May 15 01:17:07 localhost kernel: using 1310 buffer headers and 1310 cluster IO buffer headers
May 15 01:17:07 localhost kernel: Local FireWire GUID = 0x110600:0x2a1bd
May 15 01:17:07 localhost kernel: Local FireWire GUID = 0xa95ff:0xfeef67e0
May 15 01:17:07 localhost kernel: Security auditing service present
May 15 01:17:07 localhost kernel: BSM auditing present
May 15 01:17:07 localhost kernel: From path: "/pci@f4000000/ata-6@d/disk@0:10,\mach_kernel", Waiting on <dict ID="0"><key>IOPathMatch</key><string ID="1">IODeviceTree:/pci@f4000000/ata-6@d/@0:10</string></dict>
May 15 01:17:07 localhost kernel: Got boot device = IOService:/MacRISC2PE/pci@f4000000/AppleMacRiscPCI/ata-6@D/AppleKauaiATA/ATADev iceNub@0/IOATABlockStorageDriver/IOATABlockStorageDevice/IOBlockStorageDriver/ST 380011A Media/IOApplePartitionScheme/AppleHFS_Untitled2@10
May 15 01:17:07 localhost kernel: BSD root: disk0s10, major 14, minor 9
May 15 01:17:07 localhost kernel: AppleCPUThermo couldn't parse platform functions
May 15 01:17:07 localhost kernel: Jettisoning kernel linker.
May 15 01:17:07 localhost kernel: Resetting IOCatalogue.
May 15 01:17:07 localhost kextd[84]: registering service "com.apple.KernelExtensionServer"
May 15 01:17:10 localhost kernel: Matching service count = 0
May 15 01:17:10 localhost kernel: AppleRS232Serial: 0 0 AppleRS232Serial::start - returning false early, Connector or machine incorrect
May 15 01:17:10 localhost kernel: rtclock timebase_callback: late old 1000000000 / 41656700 new 1000000000 / 41656251
May 15 01:17:13 localhost SystemStarter: Bienvenue sur Macintosh.
May 15 01:17:14 localhost kernel: UniNEnet: Ethernet address 00:0a:95:ef:67:e0
May 15 01:17:14 localhost kernel: IOFireWireIP: FireWire address 00:11:06:00:00:02:a1:bd
May 15 01:17:14 localhost kernel: IOFireWireIP: FireWire address 00:0a:95:ff:fe:ef:67:e0
May 15 01:17:14 localhost lookupd[125]: lookupd (version 324.13) starting - Thu May 15 01:17:14 2008
May 15 01:17:15 localhost ConsoleMessage: Starting Apple Multicast DNS Responder
May 15 01:17:15 localhost ConsoleMessage: Starting timed execution services
May 15 01:17:15 localhost ConsoleMessage: Starting SecurityServer
May 15 01:17:15 localhost SystemStarter: D?marrage du r?pondeur DNS multi-diffusion Apple
May 15 01:17:15 localhost SystemStarter: D?marrage des services ? ex?cution diff?r?e
May 15 01:17:15 localhost ConsoleMessage: Starting kernel event agent
May 15 01:17:15 localhost mDNSResponder[147]: mDNSResponder-58.8.1 (Jan 31 2005 21:11:41) starting
May 15 01:17:15 localhost mDNSResponder[147]: SetupAddr invalid sa_family 0
May 15 01:17:15 localhost diskarbitrationd[87]: disk0s10 hfs 3A48DD89-B2C1-3D82-A158-1469A7237FD8 Sans titre /
May 15 01:17:15 localhost diskarbitrationd[87]: disk1s9 hfs 6950CF0C-02C2-3F9E-B5D5-EFC293557C95 PowerMac Software [not mounted]
May 15 01:17:16 localhost SystemStarter: Starting SecurityServer
May 15 01:17:16 localhost SystemStarter: D?marrage de l?agent d??v?nement du kernel
May 15 01:17:16 localhost ConsoleMessage: Initializing network
May 15 01:17:16 localhost SystemStarter: Initialisation du r?seau
May 15 01:17:16 localhost ConsoleMessage: Checking disks
May 15 01:17:18 localhost kernel: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex
May 15 01:17:18 localhost configd[86]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/set-hostna me
May 15 01:17:19 localhost set-hostname[190]: setting hostname to ordi.local
May 15 01:17:21 localhost kernel: ATY,Pheonix_A: vram [9c000000:04000000]
May 15 01:17:21 localhost configd[86]: posting notification com.apple.system.config.network_change
May 15 01:17:21 localhost configd[86]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
May 15 01:17:21 localhost mach_init[2]: Server 2ac7 in bootstrap d03 uid 0: "/usr/sbin/lookupd": exited as a result of signal 1 [pid 125]
May 15 01:17:21 localhost configd[86]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/set-hostna me
May 15 01:17:21 localhost lookupd[195]: lookupd (version 324.13) starting - Thu May 15 01:17:21 2008
May 15 01:17:21 localhost ConsoleMessage: Starting network time synchronization
May 15 01:17:21 localhost set-hostname[220]: setting hostname to ordi.local
May 15 01:17:23 localhost kernel: ATY,Pheonix_B: vram [98000000:04000000]
May 15 01:17:23 localhost SystemStarter: The "HasShadow" window property is obsolete. Use CGSSetWindowShadowAndRimParameters(cid, wid, 0.0,0.0, 0,0, CGSNoShadowStyle) to turn off the window shadow instead. Set a break-point on CGSLogMessage to find out where this property is set.
May 15 01:17:23 localhost ConsoleMessage: Loading Shared IP extension
May 15 01:17:23 localhost ntpdate[239]: ntpdate [email protected] Fri Sep 12 18:30:10 PDT 2003 (1)
May 15 01:17:24 localhost ConsoleMessage: Starting printing services
May 15 01:17:24 localhost ntpdate[239]: step time server 17.72.133.45 offset 0.090631 sec
May 15 01:17:24 localhost ntpd[262]: ntpd [email protected] Fri Sep 12 18:30:03 PDT 2003 (1)
May 15 01:17:24 localhost ntpd[262]: precision = 8 usec
May 15 01:17:24 localhost ConsoleMessage: Starting network file system
May 15 01:17:24 localhost diskarbitrationd[87]: disk2s1 msdos 00000000-0000-0000-0000-000000000000 My Book /Volumes/My Book
May 15 01:17:24 localhost automount[288]: automount version 57
May 15 01:17:24 localhost syslogd: /dev/console: Input/output error
May 15 01:17:24 localhost init: kernel security level changed from 0 to 1
May 15 01:17:24 localhost mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/libexec/fix_prebinding": exited with non-zero status 1 [pid 301]
May 15 01:17:24 localhost ConsoleMessage: Starting Apple File Service
May 15 01:17:25 localhost automount[311]: automount version 57
May 15 01:17:25 localhost ConsoleMessage: Starting Apache web server
May 15 01:17:25 localhost /usr/sbin/AppleFileServer: Sent launch request message to DirectoryService mach_init port
May 15 01:17:25 localhost DirectoryService[323]: Launched version 1.8.5 (v258.3)
May 15 01:17:26 localhost ConsoleMessage: Loading IP Firewall extension
May 15 01:17:27 localhost kernel: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled
May 15 01:17:27 localhost kernel: IPv6 packet filtering initialized, default to accept, logging disabled
May 15 01:17:27 localhost kernel: IP firewall loaded
May 15 01:17:27 localhost ConsoleMessage: Starting internet services
May 15 01:17:27 localhost /usr/sbin/httpd: Sent launch request message to DirectoryService mach_init port
May 15 01:17:27 localhost xinetd[351]: xinetd Version 2.3.11 started with libwrap options compiled in.
May 15 01:17:27 localhost xinetd[351]: Started working: 2 available services
May 15 01:17:28 localhost automount[311]: logout notification received.
May 15 01:17:28 localhost automount[311]: requesting logout processing.
May 15 01:17:28 localhost automount[288]: logout notification received.
May 15 01:17:28 localhost automount[288]: requesting logout processing.
May 15 01:17:28 localhost automount[311]: handledeferredrequests: user logged out.
May 15 01:17:28 localhost automount[288]: handledeferredrequests: user logged out.
May 15 01:17:29 localhost kernel: 0 0 AppleUSBCDCECMData: probe - provider doesn't want us to match
May 15 01:17:29 localhost kernel: 0 0 AppleUSBCDCWMCData: probe - provider doesn't want us to match
May 15 01:17:29 localhost kernel: 0 0 AppleUSBCDCACMData: probe - provider doesn't want us to match
May 15 01:17:29 localhost kernel: InternalUSBModem::setPowerState(1)
May 15 01:17:32 localhost TabletDriver[362]: #### GetFrontProcess failed to get front process (-600)
May 15 01:17:51 localhost diskarbitrationd[87]: SystemUIServer [376]:21019 not responding.
May 15 01:17:52 localhost diskarbitrationd[87]: disk1s9 hfs 6950CF0C-02C2-3F9E-B5D5-EFC293557C95 PowerMac Software /Volumes/PowerMac Software
May 15 01:19:39 localhost kernel: resize: max chain len 22, new table size 8192
May 15 01:27:28 localhost lookupd[195]: NetInfo connection failed for server 127.0.0.1/local
May 15 02:08:31 localhost kernel: USBF: 3107.389 AppleUSBOHCI[0x1281000]::MakeDevice error setting address. err=0xe00002ed device=0x12e8300 - releasing device
and my last panic logs
Mon May 12 14:45:14 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000006174696F PC=0x0000000000252638
Latest crash info for cpu 0:
Exception state (sv=0x3B912780)
PC=0x00252638; MSR=0x00009030; DAR=0x6174696F; DSISR=0x40000000; LR=0x0053CB20; R1=0x1C55BC50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x02AB8318 0x0053CB20 0x0053BEB0 0x00540044 0x005404F4 0x0053D538 0x00035148 0x00035028
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBHub(2.1.5)@0x539000
dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x471000
Proceeding back via exception chain:
Exception state (sv=0x3B912780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2EE6AC80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x3B912780)
PC=0x00252638; MSR=0x00009030; DAR=0x6174696F; DSISR=0x40000000; LR=0x0053CB20; R1=0x1C55BC50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x02AB8318 0x0053CB20 0x0053BEB0 0x00540044 0x005404F4 0x0053D538 0x00035148 0x00035028
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBHub(2.1.5)@0x539000
dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x471000
Exception state (sv=0x2EE6AC80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Wed May 14 23:30:32 2008
panic(cpu 0): Uncorrectable machine check: pc = 000000000070FE50, msr = 0000000000149030, dsisr = 42000000, dar = 00000000007D0000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 0000000000000000
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x0009160C 0x000908F8 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x1FC42280)
PC=0x0070FE50; MSR=0x00149030; DAR=0x007D0000; DSISR=0x42000000; LR=0x0070DBE4; R1=0x0CDBBD20; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x0070DB8C 0x0070D808 0x00267FCC 0x00266EAC 0x00266E10
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWOHCI(2.2.10)@0x708000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x398000
dependency: com.apple.iokit.IOFireWireFamily(1.8.8)@0x407000
Exception state (sv=0x1F638C80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Is my mac dying?? Does all this come from defectible hardware? Is reinstalling a sysem a waste of time?

philomene251 wrote:
Hello, and please forgive my english, I'll do my best!
My complements on that. While I read the post quickly, it was only later that I saw you're in Paris....
Anyway, I'm not an expert on logs (system and panic ones), but from what I can tell there is a problem with the PCI USB/Firewire card you installed. It looks like it's the USB portion of the card; those are happing at startup when I'm pretty sure there's a kind of initial checking of the PCI cards.
May 14 22:57:42 localhost kernel: 0 0 AppleUSBCDCECMData: probe - provider doesn't want us to match
AppleUSBOHCI0x1382800::MakeDevice error setting address. err=0xe00002ed device=0x1f16000 - releasing device
IOUSBDevice0x1654000: Error (0xe00002ed) getting device device descriptor
2136.248 AppleUSBOHCI0x127f000 Watchdog detected dead controller (hcca #: 12727, hc #: 58749)
The panics show dependencies to USB and FW:
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBHub(2.1.5)@0x539000
dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x471000
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWOHCI(2.2.10)@0x708000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x398000
dependency: com.apple.iokit.IOFireWireFamily(1.8.8)@0x407000
The problems with the card at startup are probably creating an unstable condition, which in turn is causing kernel panics later on.
Basic things first, whenever you change the hardware setup, e.g. RAM and adding cards, it's a really good idea to reset-PRAM. Did you do that? Try that first, it's simple and easy enough to try.
If resetting the PRAM doesn't help, then try the new PCI card. I re-read your post a few times, but I haven't seen whether you tried removing the PCI FW/USB card to see if that helps. Try your mouse and some other devises on the native USB and FW ports. If you're stable, then it very well could be the card.
Of course there's also the question of the RAM, which you pulled without help. Again, after any change of the hardware (adding RAM, pulling RAM, adding/pulling cards, etc.) even during testing, reset the PRAM at startup.
With new RAM it's usually a good idea to test it, with say AHT CD or Rember. If you test, you might want to do this without the new card. It's a little tricky right now because you added 2 new pieces of HW (RAM and FW/USB card) either which or both could cause the problems you're seeing. OS X is picky about RAM, and the MDDs in particular are extremely picky about RAM as far as Apple HW is concerned.
Lots of kernel panics can eventually cause damage to the OS X installation. So in the end, it may be worth re-installing. But, before you take that route. Try the simple things like removing the PCI FW/USB card & testing, and testing the RAM. Take it one step at a time.

Working with my 2 FireWire HD i had a crash. the only way to start was a safe start. then id maged to start from a DVD and install a MAC OS 10.3 wich ran 4 some time then the same problem only safeMode. kernel panic inserted the tech tool DVD

working with my 2 FireWire HD i had a crash. the only way to start was a safe start. then id maged to start from a DVD and install a MAC OS 10.3 wich ran 4 some time then the same problem only safeMode. kernel panic by inserting the tech tool DVD, wich produces the following highligted text:
panic(cpu 0 caller =xffff0003): 0x300 - Data access
latest stack backtrace for CPU 0:
Backtrace:
0x0009CC88 0x00D63C 0x00029DAO 0x000BOA10 0x000B4270
proceeding back via exception chain:
Exception state (sv=0x26acd700)
PC=0x2717E900; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x2717EBE4; R1=0x26AD3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x27178B0 0x00344ACB 0x00345970 0x2717EC08 0x2718458 0x00340590
0x003496EC 0x0034B59C 0x0034A6BC 0x000B1DD4
Kernel Loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWDHC1(3.9.5)00x2717c000->0x271aafff
dependency: com.apple.iokit.10PCIFamily(2.6)00x1e840000
dependency: com.apple.iokit.I0FireWireFamily(3.4.7)00x270dd000
Exception state (sv=0x26abd280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000;R1=0x00000000; XCP=0x00000000 (unknown)
BSD process name corresponding to current thread: kernel_task
so what
greetings from berlin

Greetings,
It appears to be a FW problem, possibly flaky case, or drive problem.
One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
Reboot, test again.
If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts (Users & Groups in later OSX versions)>Login Items window to see if it or something relevant is listed.
Check the System Preferences>Other Row, for 3rd party Pref Panes.
Also look in these if they exist, some are invisible...
/private/var/run/StartupItems
/Library/StartupItems
/System/Library/StartupItems
/System/Library/LaunchDaemons
/Library/LaunchDaemons

Kernel panics, graphic file corruption with Firewire

I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
I never actually solved the problem, just started using USB-2 instead and the issues went away.
--I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
--I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
I'll try FW again after a future system software upgrade but I'm giving up on it for now.

I've been having consistent problems with Firewire since I got my Mac Pro last year. I only recently narrowed it down to Firewire so I thought I'd write it up here for the record.
I never actually solved the problem, just started using USB-2 instead and the issues went away.
--I had been getting pretty consistent kernel panics while doing backups or large file transfers to an external FW drive. I tried a few different drives and cables and the panics were consistent.
--I also noticed a strange problem where graphic files I'd backed up (TIFF, JPEG, etc.) would have these single-pixel horizontal streaks running through them. This was a little disconcerting because it wasn't picked up during verification, it was just there when I opened the backup file.
I found lots of people with FW problems in these forums but none mentioned that strange file corruption I got.
I'll try FW again after a future system software upgrade but I'm giving up on it for now.

Kernel Panic Snow Leopard 10.6.4 + Logic Studio 9.1.1+ Motu firewire driver

Strange Kernel Panics are happening to my MacbookPRo early'08
I've just installed snow leopard,updated it to 10.6.4
Installed Logic Studio 9 and updated it to 9.1.1
Then I have a MOTU 896HD, installed drivers
then restarted my mac and there they're, kernel panic at thge startup, just after the first sound of powering on.
this is the kernel panic:
http://img683.imageshack.us/img683/4592/cimg2553d.jpg
http://img36.imageshack.us/img36/2274/cimg2554x.jpg
http://img84.imageshack.us/img84/4939/cimg2552.jpg
http://img710.imageshack.us/img710/59/cimg2551.jpg
I've done also a short video with an iPod nano to let you see completely this Kernel Panic. Don't wory, it's without any viruses or malware, I've just taken directly from my iPod nano.
http://www.megaupload.com/?d=ZF5WX4WN
What can it be?
Thanks a lot,
Best Regards,
Marco.

The info is linked above. I agree that that info should be on the download page, but not having that info there doesn't mean the drivers aren't 64 bit.
http://www.motu.com/techsupport/technotes/64-bit-mac-compatibility
Hardware
When using the 64-bit kernel in Mac OS X v10.6 and later, 64-bit hardware drivers must be used. MOTU FireWire/USB2 audio interfaces, PCI-424 audio interfaces, and USB MIDI interfaces can be used with the 32- or 64-bit kernel. *The minimum driver versions required for use with the 64-bit kernel are:*
*FireWire/USB2 Audio 1.5 (37320)*
PCI-424 Audio 1.5 (38352)
USB MIDI 1.5 (37320)
The current version available for download (after you log in) is 1.5.38352, so according to MOTU it is a 64 bit driver and runs on the 64 bit kernel.
Download here, you may need to log in. Forget about the two pages you linked to, I'm not sure how you found them, but they are old and are no longer relevant. http://www.motu.com/download/downloadmatching_downloads.html?platform_id=2&productid=14
The link to the download itself is here, again this link may not work if you don't log in first.
http://s3.amazonaws.com/motu/downloads/firewire/MOTUAudioInstaller-1.5.38352.zip
I downloaded the latest and tested it on 64 bit kernel and it worked fine, so yes, they are in fact 64 bit drivers. If you are still skeptical, just download for yourself and boot into the 64 bit kernel, you'll see that they work fine.

Is anyone having a problem connecting 400 firewire thru an adapter for the 800 firewire port on a Macbook Pro 2011? It does a kernel panic every time I connect it. Is there a "proper way" to connect it?

Is anyone having a problem connecting 400 firewire thru an adapter for the 800 firewire port on a Macbook Pro 2011? It does a kernel panic every time I connect it. Is there a "proper way" to connect it? Just in case it makes a difference I am trying to hook up an Avid Mbox Pro for Pro tools.

What is the part number and model of Firewire adapter?
I have used them in the past without any problems whatsoever.
Allan

Firewire induced Kernel Panic in OS10.4.3

Following the need to repair my HD drive (fixed using Diskwarrior) - connecting my external Firewire Drive (Maxtor one touch) causes a kernel panic !
External drive works OK in OS 10.3 and 10.4.2 partitions but not when booted into my 10.4.3 partition. Have repaired permissions, reset PRAM. Clearly not a hardware problem. Is this a 10.4.3 bug or a cache /file corruption which just needs fixing ?
NB For the experts I get the following report :
panic(cpu 0 caller 0x215D6DEC): IORegistryEntry::_RESERVEDIORegistryEntry8 called
Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x215D6DEC 0x215D68DC 0x215D643C 0x002BF014 0x002BEDDC
0x002BF844 0x002BFEB0 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.maxtor.iokit.IOFireWireMxBt(2.0.0d1)@0x215d5000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x83a000
Proceeding back via exception chain:
Exception state (sv=0x2132C280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
Model: PowerMac4,5, BootROM 4.4.5f3, 1 processors, PowerPC G4 (2.1), 800 MHz, 512 MB
Graphics: NVIDIA GeForce4 MX, GeForce4 MX, AGP, 32 MB
Memory Module: DIMM0/J22, 256 MB, SDRAM, PC133U-322
Memory Module: DIMM1/J20, 256 MB, SDRAM, PC133U-333
Modem: Dash2, Euro, V.92, 1.0F, APPLE VERSION 2.6.6
Network Service: Built-in Ethernet, Ethernet, en0
Parallel ATA Device: ST380020A, 74.53 GB
Parallel ATA Device: HL-DT-ST DVD-RW GCA-4020B,
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Fujitsu Component, Up to 1.5 Mb/sec, 100 mA
USB Device: USB Receiver, Logitech, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA

Further info.
Triggered by another post in this section I did a 'safe boot' which mounted the firewire drives OK. However, a following normal boot with Firewire connected exhibited the same "You need to restart ..." problems.
This must narrow down the problems but what needs to be done to fix it ?

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.)

Kernel Panic when plugging Firewire devices

I have a Kernal Panic each time I plug something in the Firewire ports. I already have tried many things to solve this issue, in vain (see here, in french : http://www.xrings.net/xrings/forum/viewtopic.php?t=216 )
If somebody has any suggestion... Thanks !

Thank you jeffdc, but I have done it.
In fact, I've done all the things I could think about : they are listed in the link referring to an other forum (in french) in the first topic of this discussion :
http://www.xrings.net/xrings/forum/viewtopic.php?t=216.
I translate it here in english :
MY MAC. Power PC G4 800 MHz 256 Mo. System : OS X 10.4.2.
ISSUE. Kernel Panic each time I try to connect any kind of device (HD, iPod) to any of my Firewire ports.
CABLES AND DEVICES. I changed external Firewire cables and devices to be sure that the problem was not coming from them. The kernel panic appears systematicaly after connecting to the Firewire ports, when the computer is switched on as switched off with a reset...
FIREWIRE PORTS. I followed the instructions from the Apple Support Site : disconnect evreything (USB and all ports), switch off and disconnect the computer from the electricity alimentation cable, wait a few minutes, reconnect, switch on. Nothing changed.
HARDWARE TEST. I reboot on the Apple Hardware Test CD. Results were OK. I've done it twice : first time with iPod connected on the firewire, second time with nothing connected on the firewire port. First time the result was OK : firewire was indicated as "present". Second time it was OK too : it was indicated as "absent". So the computer is able to detect the Firewire device... (PS. I don't have any trouble with the iPod, nor with the software nor with the hardware, when the connection is with USB, so the iPod and its software are OK.)
AUTORISATIONS. I have of course repaired the autorisations with Disk Utility. Nothing changed.
NVRAM. I have done a reboot in Open Firmware (pommealt+of) to reset the Non Volatil RAM (reset-nvram, reset-all). For no result.
CORRUPTED, HIDDEN FILES. I've tried to do a big cleaning with Applejack utility (corrupted files etc.) in Open Firmware again. Again in vain.
NEW SYSTEM ON A PARTITION. My HD is divided en three partitions, so I've done a reboot on the Installation CD from my old 10.2 System on a partition containing only documents. I made a reset on that System, done a few upgradings (System, iTunes and iPod), and now that partition is 10.2.8.
NEW FIREWIRE TEST ON THE REINSTALLED SYSTEM. Under that freshly reinstalled System 10.2.8, I tried again to connect the iPod on the FireWire port : Kernel Panic again.
QUESTION. So, what does happen ? Is it a software or a hardware issue ? Or an original bug in the 10.2 system ? What can I do ?
Thank you again to all the people who have already read my post and took time to give me an answer, and to all the people who will do it.

Kernel panics w/Firewire CD drive

Hi. I'm running a 500MHz TiBook, with OS X, 10.4.3. Ever since the last security update (the large one that came out on the 29th, I believe) I've been getting kernel panics. They seem to be tied into my older FireWire CD burner. Whenever I start up my computer with it connected, the computer starts up and immediatly goes to kernel panic. When I plug it into my laptop, it does the same thing. I've tried every combination of devices I can, it pretty much always happens. (I've managed to get it to work twice, but nothing was different.) Had absolutely no problems with the burner before the update, and it still works on my roomate's G4 Powermac running Panther. Other firewire devices all run perfectly normal on my laptop.
The CD burner is a QPS bran Que!Fire CDRW 4x4x24.
I've searched on these forums and elsewhere, and haven't found very much that applies to my situation, and the few things I have found don't work. I'm probably just searching on the wrong terms.
I pulled up the panic log from Console. It follows below. If anyone's got any leads or ideas, that'd be great. I'm still trying to contact QPS. It was suggested I redo the firmware on the CD drive using another computer; Que's website gives a dead link to a forum. When I tracked that site down, they didn't have what was needed. So yeah, any help is much appreciated! thanks!
J. Pierce
Kernel panic log from Console follows below:
Thu Dec 15 22:15:08 2005
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000000 PC=0x00000000328F3380
Latest crash info for cpu 0:
Exception state (sv=0x327BC000)
PC=0x328F3380; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x328F3380; R1=0x173637D0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000024 0x002BBE40 0x002BC0F0 0x002B7980 0x002BBFBC 0x002BC158
0x32B70890 0x32B70680 0x32B70478 0x2D4A8A44 0x2D48A040 0x2D489940 0x2D4F5A24 0x2D4E5450
0x002CF960 0x002CE828 0x000A9814
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.QPSQueFire(1.4.4)@0x328f2000
dependency: com.apple.iokit.IOFireWireSBP2(1.7.5)@0x32b6c000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4.4)@0x2d7d8000
dependency: com.apple.iokit.IOFireWireSerialBusProtocolTransport(1.4.0)@0x32b46000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
com.apple.iokit.IOFireWireSBP2(1.7.5)@0x32b6c000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
com.apple.driver.AppleFWOHCI(2.5.2)@0x2d4df000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x275e4000
dependency: com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
com.apple.iokit.IOFireWireFamily(2.0.8)@0x2d480000
Proceeding back via exception chain:
Exception state (sv=0x327BC000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2D239500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x327BC000)
PC=0x328F3380; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x328F3380; R1=0x173637D0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000024 0x002BBE40 0x002BC0F0 0x002B7980 0x002BBFBC 0x002BC158
0x32B70890 0x32B70680 0x32B70478 0x2D4A8A44 0x2D48A040 0x2D489940 0x2D4F5A24 0x2D4E5450
500 MHz TiBook Mac OS X (10.4.3)

Hi J.P.,
Your panic log is definitely flagging the kernel extensions for the FireWire burner:"Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.QPSQueFire(1.4.4)@0x328f2000"so that is clearly the problem. The version shown (1.4.4) is the most current version. Unless the kernel extension itself has become corrupted, something in the security update may have rendered that driver incompatible with Mac OS X.
This is something you want to take up with Que before proceeding further. If they've had similar reports, they might release a new kernel extension. Otherwise, you're faced with trying to reinstall that kernel extension from an identical copy of Tiger or performing an Archive and Install.
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.

Connection with firewire decks lost and kernel panics

Hi all,
I have just started to experience an odd issue.
My Mac Pro is having issues with seeing any firewire deck. I regularly use a DV camcorder and a ADVC-300 for my imports and never have any issues. In the last three days both devices are suddenly dropped whilst importing footage. At first I wondered if is was something to do with the recent update. However, I tried iMovie and it couldn't see either device. Once FCP can't see a device the only way to fix it is to restart the Mac.
I'm wondering if it could be hardware related as I have had 2 Kernel panics in as many days. I have reset the P & V ram, run disk utility but no improvement. I am about to run a hardware test also.
Does anybody have any ideas?
Thanks

Make & model of the DV camcorder?
Assuming the camcorder has a firewire output, are you saying you have both devices connected at the same time? If so, try the camcorder by itself. Then, open System Profiler (/Applications/Utilties/), look in the Firewire section and see if the computer is seeing it. We'll go from there.
J S is right about the FW cable, though - troubleshooting involves swapping out parts and devices one at a time to narrow down the search for a culprit. If the computer is NOT seeing the devices, then move on to swapping out stuff.
But before doing that, try the Guinness Solution: Power everything down and disconnect the power cable and the FW cable(s) from the Mac Pro. Leave it that way while you enjoy an adult beverage. After 15 minutes or so, plug everything back in, power up, and try it.
There's an electronic breaker in the circuitry on the logicboard in the Firewire bus path. If it senses an overload, it will activate. Disconnecting all power from it for a few minutes allows it to reset.

Kernel Panic with LaCie Firewire Speakers and SL 64 bit

Hi all,
I experienced kernel panics during boot in 64 bit and realized that the Apple FW driver causes a kernel panic during boot.
I isolated the problem to be my FW LaCie Speakers (attached through my cinema display 23"). I thought I have a conflict with something else, so I tried to make a clean installation but still, SL crashes when in 64 bit. No problem at all in 32 bit mode.
I'm really surprised as the kernel panic log shows the problem inside the Apple Audio FW driver...
Any ideas?
Thanks
Giuseppe

I just tried to connect the speakers directly to the computer and the problem is gone... really surprised that the hub in the cinema display is causing this problem.

Get kernel panic when I burn DVDs

when I burn several DVDs using the internal DVD burner on my 1.25 Ghz G4 running OS X 10.4.11, I am getting a kernel panic that tells me to reboot my computer. I'm using Toast Titanium 8 to burn with. Any ideas how to prevent this?
Here's the details:
Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x000000002A2AD680 PC=0x0000000000847964
Latest crash info for cpu 1:
Exception state (sv=0x33164500)
PC=0x00847964; MSR=0x00009030; DAR=0x2A2AD680; DSISR=0x40000000; LR=0x0083294C; R1=0x1CA33B00; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00072C8C 0x0083294C 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
0x000233F8 0x000ABEAC 0x341B47F8
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon8500(4.1.8)@0x82b000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x491000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x7f1000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x815000
Proceeding back via exception chain:
Exception state (sv=0x33164500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x33335780)
PC=0x9000B348; MSR=0x0200F030; DAR=0xE045C000; DSISR=0x42000000; LR=0x9000B29C; R1=0xF0343A60; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x33164500)
PC=0x00847964; MSR=0x00009030; DAR=0x2A2AD680; DSISR=0x40000000; LR=0x0083294C; R1=0x1CA33B00; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00072C8C 0x0083294C 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
0x000233F8 0x000ABEAC 0x341B47F8
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon8500(4.1.8)@0x82b000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x491000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x7f1000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x815000
Exception state (sv=0x33335780)
PC=0x9000B348; MSR=0x0200F030; DAR=0xE045C000; DSISR=0x42000000; LR=0x9000B29C; R1=0xF0343A60; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPCModel: PowerMac3,6, BootROM 4.5.7f1, 2 processors, PowerPC G4 (3.2), 1.25 GHz, 1.25 GB
Graphics: ATI Radeon 9000 Pro, ATY,RV250, AGP, 64 MB
Memory Module: DIMM0/J21, 256 MB, DDR SDRAM, PC2700U-25330
Memory Module: DIMM1/J22, 512 MB, DDR SDRAM, PC2700U-25330
Memory Module: DIMM2/J23, 512 MB, DDR SDRAM, PC2700U-30330
Modem: Dash2, UCJ, V.92, 1.0F, APPLE VERSION 2.6.6
Network Service: Internal Modem, PPP (PPPSerial), modem
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: pci9004,7850, sppciscsibus, SLOT-3
Parallel ATA Device: ST3300831A, 279.46 GB
Parallel ATA Device: WDC WD1600JB-00GVA0, 149.05 GB
Parallel ATA Device: PIONEER DVD-RW DVR-111D
Parallel ATA Device: ST3400632A, 372.61 GB
Parallel ATA Device: ST3250823A, 232.89 GB
SCSI Device: EPSON SCANNER GT-9500
USB Device: Hub, Up to 12 Mb/sec, 500 mA
USB Device: ImageMate 14 in 1 Reader/Writer, SanDisk, Up to 12 Mb/sec, 500 mA
USB Device: HP Color LaserJet 2600n, Hewlett-Packard, Up to 12 Mb/sec, 500 mA
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Fujitsu Component, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
FireWire Device: > LaCie d2 DVD-RW Firewire, LaCie Group SA, Up to 400 Mb/sec

I would unplug the carload of stuff jacked into the Mac (other than keyboard and mouse) and see if that continues. You have so much stuff jacked in something's got to give.

Firewire: kernel panic in: fwnet_write_complete

Similar Messages

Maybe you are looking for