What's up my technologically advanced peeps? I have a query. I have a somewhat unusual network set up (maybe not) as follows:

- G5 Tower (dual 2.7) in home office connected via Gigabit Ethernet.
- MacBookPro connected via 100BaseT Ethernet in home office or Airport when roaming
- MacMini 1.83 Intel Core Duo hooked up via 100BaseT Ethernet in home theater
- 50" HD5040 Pioneer (720P) connected to MacMini via DVI-HDMI
- Integra Receiver connected to MacMini via optical for 5.1 surround
- 2 TB Buffalo NAS in attic with backed up DVD's on it

I have an EyeTV 500 and 250 hooked up to the G5 for recording shows which are archived on a dedicated 400GB SATA internal drive.

On the MacMini, I access the EyeTV recordings folder on the network by mounting the G5 drive and specifying in the EyeTV preferences the location of the EyeTV folder on the network.

It works pretty great. The HD archives seem to stream without a problem on the network. I can watch CSI Miami in all its HD glory without a problem.

My problem: Lately, when watching these HD programs on the MacMini, I will have the occasional Kernel Panics, which is frustrating. Sometimes it happens when I am rewinding or forwarding, other times it is when I am not doing anything. Does anyone have any idea why this is happening?

Prior to getting the MacMini, I had tested the set up on the MacBook Pro and I never had a Kernel Panic.

Any thoughts would be much appreciated.

-MAcguyincali

Any other behavior before the KP? Are they 720p/1080i files you're playing at the time? Play back through EyeTV or Quicktime or VLC? Do you know if the G5 is recording when you have playback issues? Do you have similar issues when playing off the Mac Mini's internal disc? The NAS server?

That's a stack of questions, but if for example it's only 1080i files that give a hard time, maybe you could copy ABC shows (or whichever network) onto your Mini before watching as a simple workaround?

Any other behavior before the KP? Are they 720p/1080i files you're playing at the time? Play back through EyeTV or Quicktime or VLC? Do you know if the G5 is recording when you have playback issues? Do you have similar issues when playing off the Mac Mini's internal disc? The NAS server?

That's a stack of questions, but if for example it's only 1080i files that give a hard time, maybe you could copy ABC shows (or whichever network) onto your Mini before watching as a simple workaround?

Nothing unusual seems to be happening before the KP.

I will check to see what types of files I'm playing. Its usually a combination of 720p and 1080i, but can't say for certain which ones I was watching when KP happened.

I am playing back through EyeTV (so I don't need to use keyboard / mouse).

I will copy a file to the MacMini drive and play it there to see if there is a problem.


I guess I have to troubleshoot it a little more and report back. Thanks for the suggestions.

-macguyincali

What devices are physically attached to the Mini? Does it panic if you detach the EyeTV thingy? [Can you play-back video w/o the EyeTV attached?] Are you running the latest rev of the EyeTV software/drivers?

In my experience, kernel panics are commonly caused by flaky USB devices and/or bad drivers.

I think I had EyeTV 2.3.3, dual EyeTV500s and Apple remote-related kernel panics happen to me twice--in succession--then I haven't been able to duplicate it.

Somewhat similar network setup to you--G4 Powermac over gigabit to a supposedly gigabit 1.83 Macbook--I think each time I had two windows open, both with digital audio selected, which does stretch the 1.83, once I think it was related to a remote button press and the second time I think it happened when I tried to quit the EyeTV app with both windows still open. Later I found that my Macbook was only getting 100MB and not gigabit speed between the two Macs. Took me a while to figure out that was because I was passing my Cat5e through a surge supressor--once I removed the cable and plugged it back in to the Macbook--bingo--fast 32MB/sec transfers--and--no kernel panic since.

I don't have enough info to feel like I'm out of the water yet, or to even feel like I know why it happened. Right now I'm sticking with crazy button presses on the remote. Until it happens again. Yeah, that's the ticket.

Oh, this is with 1GB of original Apple RAM in the Macbook. My experience, kernel panics are more often RAM related. How much RAM is in the mini, anyway? And are you keeping an eye on the temperature, by chance, when you're playing back high def?

What devices are physically attached to the Mini? Does it panic if you detach the EyeTV thingy? [Can you play-back video w/o the EyeTV attached?] Are you running the latest rev of the EyeTV software/drivers?

In my experience, kernel panics are commonly caused by flaky USB devices and/or bad drivers.

I actually don't have any USB devices hooked up. In fact the only thing plugged into the mac is the DVI-HDMI cable, the optical out and the Ethernet cable. The EyeTV is actually hooked up upstairs to the G5.

I think I had EyeTV 2.3.3, dual EyeTV500s and Apple remote-related kernel panics happen to me twice--in succession--then I haven't been able to duplicate it.

Somewhat similar network setup to you--G4 Powermac over gigabit to a supposedly gigabit 1.83 Macbook--I think each time I had two windows open, both with digital audio selected, which does stretch the 1.83, once I think it was related to a remote button press and the second time I think it happened when I tried to quit the EyeTV app with both windows still open. Later I found that my Macbook was only getting 100MB and not gigabit speed between the two Macs. Took me a while to figure out that was because I was passing my Cat5e through a surge supressor--once I removed the cable and plugged it back in to the Macbook--bingo--fast 32MB/sec transfers--and--no kernel panic since.

I don't have enough info to feel like I'm out of the water yet, or to even feel like I know why it happened. Right now I'm sticking with crazy button presses on the remote. Until it happens again. Yeah, that's the ticket.

Oh, this is with 1GB of original Apple RAM in the Macbook. My experience, kernel panics are more often RAM related. How much RAM is in the mini, anyway? And are you keeping an eye on the temperature, by chance, when you're playing back high def?

Interesting. Several times, the KP happened when rewinding on the Apple Remote (actually the Harmony remote programmed to emulate the Apple).

RAM might have something to do with it. I have the minimum RAM. I was going to install some more RAM later. I actually have two 1GB DDR2-533 modules that I bought for my laptop (but turned out to be the wrong kind) that are sitting around. I wonder if that will work in the MacMini?

Thanks for your advice.

Hi All,

I am using an EyeTV Hybrid with my Mac Mini, and was having kernel panics until I closed the Live TV window when I was away from the mini (when it was supposed to sleep).
FYI - Elgato recommends in their FAQs closing the Live TV window or the computer will not sleep: http://faq.elgato.com/index.php/faq/more/237/

I also noticed that both my mini and the hybrid get uncomfortably hot when the Live TV window is left open for long periods. I used a USB extension cable to get the Hybrid away from the cooling vents on the back of the mini, fearing either of them would be damaged by overheating.

I'm running 512MB of RAM, but I'll most probably take the plunge to 1 or 2GB around Leopard time!

Separate issue - I have definitely noticed a distinct graininess in the blacks in the Mac Mini DVI-HDMI output to my Sony SXRD that doesn't exist in the Sony's ATSC picture. I also have the same annoying graininess when playing a DVD on the mini, which doesn't exist when using a regular DVD player. Could somebody point me to a thread on this - I'm having trouble finding one.

MB

Separate issue - I have definitely noticed a distinct graininess in the blacks in the Mac Mini DVI-HDMI output to my Sony SXRD that doesn't exist in the Sony's ATSC picture. I also have the same annoying graininess when playing a DVD on the mini, which doesn't exist when using a regular DVD player. Could somebody point me to a thread on this - I'm having trouble finding one.


I would like to know more about this too, although I haven't noticed this on my system (not a total videophile junky, tho).

FYI - Elgato recommends in their FAQs closing the Live TV window or the computer will not sleep: http://faq.elgato.com/index.php/faq/more/237/


Good to know, even though I don't have the EyeTV hooked up to the MacMini, I was thinking of trying that next (although will be a pain to try... I'll have to split the coax). As far as I know, you can't open a live window unless hooked up directly to the EyeTV (not through the network the way I have it set up).

i have the same kernal panic problem with EyeTV. Also on an Intel Mac Mini, 1GB of Apple RAM. Also have it connected through optical audio out. I'm using the Miglia TVMini HD. It mostly occurs when first opening a Live window or a recording. Occasionally, however, it will just happen randomly in the middle of watching something. It happens about once a day.

I just emailed Miglia tech support, hope to hear back soon. Interesting to know someone else with a Mini is having the same problem. Hopefully Elgato will be able to fix it. If I were to guess, I have a feeling it may be related to the optical audio. I was running the Mini through regular stereo for a little while at first, and don't recall having these problems. Unfortunately, I have to say, having 5.1 is worth a panic here and there.

No kernel panics here. 1.66 GHz CoreDuo Mini with EyeTV 500, EyeTV 2.3.0, 2 GB RAM, and multiple Firewire hard drives connected to the Mini in series. I do get very infrequent total system freezes requiring a power-down-reboot every 2 months or so, but I haven't nailed down a specific cause. So far it hasn't caused loss of a recording.

Could you be having an EyeTV 2.3.3 issue? I've learned to avoid Elgato's point-point updates (.3.3) as those tend to be experimental and buggy. Point updates (.3.0) seem more solid overall.

Tue Jan 23 07:57:03 2007
panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x29f8e000, CR3: 0x00db5000, CR4: 0x000006e0
EAX: 0x4144a544, EBX: 0x00002a10, ECX: 0x00000288, EDX: 0x00002a10
CR2: 0x29f8e000, EBP: 0x14343ce8, ESI: 0x29f8e000, EDI: 0x4144c534
EFL: 0x00010206, EIP: 0x00195e76, CS: 0x00000008, DS: 0x00190010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14343ae8 : 0x128d1f (0x3c9540 0x14343b0c 0x131df4 0x0)
0x14343b28 : 0x1a3135 (0x3cf1f4 0x0 0xe 0x3cea24)
0x14343c38 : 0x19a8d4 (0x14343c4c 0x1 0x14343c68 0xe)
0x14343ce8 : 0x6f2470 (0x2dfae00 0x29f8c010 0x41440000 0x2951)
0x14343d38 : 0x6f22b2 (0x2e0ef00 0x2951 0xa84 0x6)
0x14343d78 : 0x6f20ac (0x2e0ef00 0x1 0x14343da8 0x199c36)
0x14343df8 : 0x6ed865 (0x2e0ef00 0x3949988 0x2dd5 0x43e4)
0x14343e78 : 0x6ecf37 (0x41fb000 0x2dd5 0x43e4 0x4502000)
0x14343ea8 : 0x3b183e (0x41fb000 0x2dd5 0x43e4 0x0)
0x14343f08 : 0x1955a1 (0x14343f44 0x0 0x0 0x0)
0x14343fc8 : 0x19ad4e (0x31c7910 0x19ad30 0x8 0x207) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0c5dbd8
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.6.0b3)@0x6e3000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x530000
dependency: com.apple.kext.OSvKernDSPLib(1.0)@0x6e1000

I've been geting kernal panics since May 2006. They always have IOAudioFamily in the "Kernal loadable modules in backtrace" area. Since this is obviously an invalid stack pointer, I don't think it means the kernal audio code has to be involved. However, my panics all look very much like this one.

I had a EyeTV 500 and a Hybrid hooked up together on a Mac Mini for a while. The two devices really didn't like each other.

Kernel panics, EyeTV crashing, wife yelling, errr, um. In any case, I've replaced the EyeTV 500 with another hybrid and moved the 500 to a different machine. While it's still got issues (man, I hope they work out two tuner support in the future), it doesn't have kernel panics, nor does EyeTV crash any more.

Cheers,
Randy Stewart

Yesterday while exporting a 480i video to iPod format on my Mini I received the message, "You need to restart your computer. Hold down the power button for several seconds or press the restart button." I had to completely reinstall EyeTV preferences following the power-down-reboot.

Does anybody else get these type of total system freezes? I've had several.

yes, that's exactly what has happened to me, maybe 4 or 5 random kernel panics total since I upgraded to 2.3.3 with my 1.83 Macbook, Comcast QAM and dual EyeTV500 setup (I know you're still on 2.3.0, methinks whatever bug is causing this now has been there for a while.) The latest occurrence was the other night while I was simultaneously 1) playing back a recorded program with digital audio out (the Taymor PBS Magic Flute) and 2) recording two other programs with my EyeTV500s. Started watching the recording at around 8PM, got about an hour in, then the two 9PM shows which had been scheduled to record started just fine, then maybe 20 minutes later got that same screen message and system freeze.

I had almost completely switched over to the Mac/dual EyeTV setup--and rarely even turned on my LG3410A. Now I've started programming it again for backup, just in case. Note: I haven't had any EyeTV-related kernel panic when I wasn't also doing something with the Mac or Apple remote, i.e. all dual unattended recordings have worked just fine.

Just to add a data point, my last kernel panic looks very similar to Dick Shelton's:

Fri Feb 2 21:05:22 2007
panic(cpu 1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x2b16e000, CR3: 0x00da4000, CR4: 0x000006e0
EAX: 0x31e2dc98, EBX: 0x000022ec, ECX: 0x000000bf, EDX: 0x000022ec
CR2: 0x2b16e000, EBP: 0x13ff3ce8, ESI: 0x2b16e000, EDI: 0x31e2fc88
EFL: 0x00010206, EIP: 0x00195e76, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13ff3ae8 : 0x128d1f (0x3c9540 0x13ff3b0c 0x131df4 0x0)
0x13ff3b28 : 0x1a3135 (0x3cf1f4 0x1 0xe 0x3cea24)
0x13ff3c38 : 0x19a8d4 (0x13ff3c4c 0x35c4c08 0x13ff3c88 0xe)
0x13ff3ce8 : 0x76f470 (0x2bbe600 0x2b16c010 0x31e22000 0x2f26)
0x13ff3d38 : 0x76f2b2 (0x2bcbf00 0x2f26 0x8bb 0x19d23a)
0x13ff3d78 : 0x76f0ac (0x2bcbf00 0x1 0x13ff3dd8 0x11cd2a)
0x13ff3df8 : 0x76a865 (0x2bcbf00 0x35c6f88 0x31e1 0xfec)
0x13ff3e78 : 0x769f37 (0x4283400 0x31e1 0xfec 0x354abc0)
0x13ff3ea8 : 0x3b183e (0x4283400 0x31e1 0xfec 0x0)
0x13ff3f08 : 0x1955a1 (0x13ff3f44 0x0 0x0 0x0)
0x13ff3fc8 : 0x19ad4e (0x2f3f978 0x0 0x19d0b5 0x2f3f978) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb1599b78
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.6.0b3)@0x760000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x515000
dependency: com.apple.kext.OSvKernDSPLib(1.0)@0x75e000

panic(cpu 2 caller 0x001023CC): jnl: transaction too big (8385024 >= 8388096 bytes, bufsize 4096, tr 0x50f8f7c bp 0x550a0120)

Latest stack backtrace for cpu 2:
Backtrace:
0xFFFFFFFF
backtrace terminated - unaligned frame address: 0xFFFFFFFF

Proceeding back via exception chain:
Exception state (sv=0x6204E000)
PC=0x900059EC; MSR=0x0200F030; DAR=0x6215B000; DSISR=0x42000000; LR=0x90BA8854; R1=0xBFFFD030; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC

I've contacted the EyeTV people about this continuing situation but they've just ignored me.

Dab--the really key descriptors in all that look something like this:

"Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.6.0b3)@0x760000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x515000
dependency: com.apple.kext.OSvKernDSPLib(1.0)@0x75e000"

Was anything like that in your log?

Also, when does this happen to you and how often? If you get the chance, you might also want to share with us what device(s) you have, which Mac, and which version of the EyeTV software you're running...

Tue Jan 23 07:57:03 2007
panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x29f8e000, CR3: 0x00db5000, CR4: 0x000006e0
EAX: 0x4144a544, EBX: 0x00002a10, ECX: 0x00000288, EDX: 0x00002a10
CR2: 0x29f8e000, EBP: 0x14343ce8, ESI: 0x29f8e000, EDI: 0x4144c534
EFL: 0x00010206, EIP: 0x00195e76, CS: 0x00000008, DS: 0x00190010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14343ae8 : 0x128d1f (0x3c9540 0x14343b0c 0x131df4 0x0)
0x14343b28 : 0x1a3135 (0x3cf1f4 0x0 0xe 0x3cea24)
0x14343c38 : 0x19a8d4 (0x14343c4c 0x1 0x14343c68 0xe)
0x14343ce8 : 0x6f2470 (0x2dfae00 0x29f8c010 0x41440000 0x2951)
0x14343d38 : 0x6f22b2 (0x2e0ef00 0x2951 0xa84 0x6)
0x14343d78 : 0x6f20ac (0x2e0ef00 0x1 0x14343da8 0x199c36)
0x14343df8 : 0x6ed865 (0x2e0ef00 0x3949988 0x2dd5 0x43e4)
0x14343e78 : 0x6ecf37 (0x41fb000 0x2dd5 0x43e4 0x4502000)
0x14343ea8 : 0x3b183e (0x41fb000 0x2dd5 0x43e4 0x0)
0x14343f08 : 0x1955a1 (0x14343f44 0x0 0x0 0x0)
0x14343fc8 : 0x19ad4e (0x31c7910 0x19ad30 0x8 0x207) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0c5dbd8
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.6.0b3)@0x6e3000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x530000
dependency: com.apple.kext.OSvKernDSPLib(1.0)@0x6e1000 Ooohhh. Doesn't look like you guys are having any fun here. I might just look over you shoulder. :eek:

I have a mac mini (dual core intel)... eyetv hybrid... external firewire laCie drive...
and am seeing these crashes :(

Mine have happened when I watch something while recording (which adds an
unfortunate *blip* to my recorded show). My kernel panic traceback is
identical to those above.

Time for an email to eye tv I guess :(

Tennesotans

Hi All,
Separate issue - I have definitely noticed a distinct graininess in the blacks in the Mac Mini DVI-HDMI output to my Sony SXRD that doesn't exist in the Sony's ATSC picture. I also have the same annoying graininess when playing a DVD on the mini, which doesn't exist when using a regular DVD player. Could somebody point me to a thread on this - I'm having trouble finding one.MB

I have a 1st generation 60"SXRD with my mini connected DVI->HDMI. Playing either DVDs or ripped DVDs, or movie trailers, I get deep blacks with no graininess.

Dab--the really key descriptors in all that look something like this:
"Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.6.0b3)@0x760000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x515000
dependency: com.apple.kext.OSvKernDSPLib(1.0)@0x75e000"

Was anything like that in your log?
...

I have the same problems. I'm using a Miglia TV MiniHD connected to a G5, the G5 is connected via DVI-> HDMI to my projector and via optical audio cable to the surround system. I do get the occasional (<4 out of 30 trials) kernel panics when watching a recording while it records another show.
So I contacted Tech Support at Miglia yesterday and promply got a reply this morning, saying it's a known problem:


Hello,
This is a known problem. Apparently, it is due to a minor Mac OS X bug. The workaround until this is fixed is to set the audio to System Sound Output.
If you have any further queries, please do not hesitate to contact us.
Thanks,


Question now, of course, is whether Apple is fixing this. I assume it's Apple's fault as it's their subsystem that crashes the entire system. My suggestion to everybody who's encountering this: send the crash log to Apple (the one that pops up after the restart).

Regards

This is a known problem. Apparently, it is due to a minor Mac OS X bug. The workaround until this is fixed is to set the audio to System Sound Output.

So, El Gato passed the buck back to Apple? If this is such a known problem with Core Audio, why aren't we aware of other third party software or external devices similarly affected?

Anyone know if there's something about this bug in the Apple Developer Connection notes?

So, El Gato passed the buck back to Apple? If this is such a known problem with Core Audio, why aren't we aware of other third party software or external devices similarly affected?

Anyone know if there's something about this bug in the Apple Developer Connection notes?

Good points!!
To make this clear: the response I got was from Miglia's Tech support, not from Elgato.
With regards to the question why we don't see this bug in other software.... well, I only have EyeTV that produces AC3 sound which I can route through the optical out. (Makes me wonder whether the bug would also occur when routing stereo through the optical).

The fact that the kernel panics only seem to occur while EyeTv is recording at the same time, on the other hand, suggests that it might actually be EyeTV related and not CoreAudio...

I've sent another email to Miglia's tech support trying to get some more information on that. We'll see.

That's interesting, I thought El Gato (and the indefatigable Nick) was providing technical support for all these third party devices running the EyeTV software...and some are getting this kernel panic when not recording. No, if they're passing the buck back to Apple they're saying it's something in "com.apple.iokit.IOAudioFamily"

http://developer.apple.com/documentation/DeviceDrivers/Conceptual/IOKitFundamentals/Families_Ref/chapter_11_section_4.html

and if there were it should be showing up in all sorts of other things, like external M-audio devices, USB devices, DACs, etc. There would be bitching and moaning in other forums...

Switching to System sound output is hardly a solution.

That's interesting, I thought El Gato (and the indefatigable Nick) was providing technical support for all these third party devices running the EyeTV software...and some are getting this kernel panic when not recording. No, if they're passing the buck back to Apple they're saying it's something in "com.apple.iokit.IOAudioFamily"

http://developer.apple.com/documentation/DeviceDrivers/Conceptual/IOKitFundamentals/Families_Ref/chapter_11_section_4.html

and if there were it should be showing up in all sorts of other things, like external M-audio devices, USB devices, DACs, etc. There would be bitching and moaning in other forums...

Switching to System sound output is hardly a solution.

I did get another response from Rob @ Miglia's tech support. He confirms it's an OS X bug and Apple is aware of this.

It seems it's a Core Audio bug that's specifically linked with the optical (built-in) output. That would explain why nobody with external audio interfaces notices this.

And yes, I agree, switching to the analog line out is not a solution.
But again, I think the best we can do is sending the "post-mortem" kernel logs to Apple after the system recovers from the panic.

Has anyone gotten any digital audio-induced kernel panics since upgrading to 2.4? I'm trying to gauge whether 2.4 has helped in this regard...

Yeap - 2.4 and I still get kernal panic with digital audio. I have a ticket with Elgato about this exact bug.

I have a ticket with Elgato about this exact bug.

That's a good one, so you'll be on the top of the pile for this week! That pile has steadily grown in the past year from those of us unwilling to switch off digital to system sound output, unfortunately they've washed their hands of it and blame Apple. I was just hoping against odds that they identified some pattern or specific behaviors which caused these things, and somehow slowed sequences down or coded around them. I've only had 1 kernel panic since, my normal rate is 2 per month, always playing back one file, recording another and using the Apple remote.

Maybe we'll catch a break in October...

chefklc - I so hear you. My ticket is currently "escalated to high" - still in the open status.... and I opened it in January. - RAWR - I haven't heard anything about it for almost a month now.

It truly make NO sense that if VLC can pass AC-3 streams fine - why can't Elgato figure out their problem...

Elgato would not have to install a kernel module to get digital output; therefore, since this is a kernel address space panic, Apple is by definition responsible for the bug. Whenever you can compromise the kernel, some smart person can turn that in to a security hole. I have had 21 of these panics in the past year and wasn't outraged until I got one during "24".

I have had 21 of these panics in the past year and wasn't outraged until I got one during "24".

Yeah, Dick, I hear you, even though I've essentially migrated to dual 500s, for our really important recordings I've kept my LG 3410A around just for backups. It's saved my bacon three times since we started tracking these panics. (And it has firewire so if I was archiving a whole season of something I could still offload it.)

Yeap - 2.4 and I still get kernal panic with digital audio. I have a ticket with Elgato about this exact bug.

I actually never saw any KP *until* bumping up to 2.4. I'm pretty sure my issue is different however, as I only use analog sound. My panic did look just about the same as the one posted above, however.

Started happening almost everytime I tried to use EyeTV(with the Hybrid). I escalated to Elgato and they said:

"Your unusual problem is not being reported by others, in general. Panics in OS X are always rare. "

With a suggestion to try 2.3.3 again... I just hooked everything up to my iMac and so far so good. :confused:

I have been having a similar problem. About once a day I will get a KP using the Eyetv on my 1.5 Ghz Intel Core Solo Mac Mini with 512MB of Ram and OS 10.4.10. I use an external HD to store my recordings and optical out for audio.

It seems like a few people have had this problem, and I would rather not have to turn off digital audio.

Please let me know.

well, zeal, once a day is too often, none of us here have ever gotten the digital audio panic that often. A few thoughts, though, one is that you didn't say which El Gato device you have, which version of the EyeTV software you're running, what you're recording, what external drive connection you're using (USB, firewire, other.) And when you say using--do you get them doing a certain activity, like watching and recording, using the remote, just doing a timed recording and nothing else, etc?

512 RAM isn't enough. There's no excuse not to be at least at 1GB with RAM as cheap as it is. And the Solo can't handle high def, how you getting digital audio if not with HD programming?

As far as the current situation, I haven't gotten one in a couple of weeks with a 1.83 CD, 2GB RAM, two 500s, 10.4.10 and still on 2.4.1--didn't record too much QAM stuff over the Summer and I haven't gotten one so far since the Fall season started. We'll see. (A handful of trusted users here report they never get them.) It will be interesting to see if any of the new HDHomerun users report anything, likewise those who have upgraded to 2.5.

I have a Mac Mini 1.66 Core Duo w/ 1 GB of Ram and EyeTV 500. I can confirm the KP on Eyetv 2.5 on my system. For some reason, it happens a lot to me as well( perhaps once every 2-5 days), so I usually end up staying on system output - and setting my Receiver to DD Prologic II. :(

But I always check it with updates. been doing it for like a year now...

I have given up on Elgato to find the problem. Fingers crossed for OSX 10.5

.... so I usually end up staying on system output - and setting my Receiver to DD Prologic II. :(

But I always check it with updates. been doing it for like a year now...

I have given up on Elgato to find the problem. Fingers crossed for OSX 10.5

Me too, I got tired of the KP a couple months ago, switched to analog output (as much as I hate it). After having migrated eyetv from a G5 with Miglia TV Mini HD to a Mac Mini (with a homerun), I didn't even bother to try the digital out.
I've given up too. Elgato blames Apple, and vice versa.... oh well...

well, zeal, once a day is too often, none of us here have ever gotten the digital audio panic that often. A few thoughts, though, one is that you didn't say which El Gato device you have, which version of the EyeTV software you're running, what you're recording, what external drive connection you're using (USB, firewire, other.) And when you say using--do you get them doing a certain activity, like watching and recording, using the remote, just doing a timed recording and nothing else, etc?

512 RAM isn't enough. There's no excuse not to be at least at 1GB with RAM as cheap as it is. And the Solo can't handle high def, how you getting digital audio if not with HD programming?

I have an EyeTV 250 Plus, with EyeTV 2.5 (3013) installed. I record to a Buffalo 500gb external drive over Firewire. I have it hooked up to an antenna for OTA content. So, the 250 Plus is via USB and the HD is Firewire. I keep everything else up to date, I have OS 10.4.10 right now.

The Core Solo can handle HD programming very nicely. The 250 plus does most of the encoding so there is very little for the mini to do.

The KPs always happen during playback. I have seen both when watching something delayed (NCAA football on ABC), and when watching a recording. It KPed on me most recently while watching Poker After Dark (NBC) recording, which is Digital, 480p.

The Core Solo can handle HD programming very nicely.

You'd be the first person here to feel that way. Most core solo mini users with max'ed out RAM report it can do a decent job with 720p ATSC, but that's it. (We have 1.66 core duo users realizing it can't always handle higher bit rate 1080i content--good thing for you, down the road you could always swap a C2D in place of your solo, should you so desire.)

The 250 plus does most of the encoding so there is very little for the mini to do.

Recording-wise, yes, but playback doesn't involve the encoder at all--that's all CPU.

The KPs always happen during playback.

OK, so open up Activity monitor and leave it open while you're trying to induce a kernel panic--and that way you can look at CPU% and page ins/outs as well--notice anything suspicious?

What display do you have it connected to, and what res?

Have you looked in your crash logs to see what it reveals as the cause? The same every time? You want to first rule "com.apple.iokit.IOAudioFamily" either in or out.

Is the firewire drive daisychained with anything else? Is anything else connected via USB?

I've been running the HDHomerun (latest firmware) to a MacBook Pro Core Duo 1.83 with 10.4.10 and EyeTV 2.5 and have gotten three (or four?) panics in three days. I too am running optical out and have 1gb of RAM with data stored on an external USB device. Also running DVI out to TV.

The panics have happened once or twice when also pressing the remote (at least the once or twice I've seen it occur). The other time was during Sesame Street, son and wife weren't happy, though a reboot always fixes it (for a time).

I'll switch to system audio and see what happens.

Maybe 10.5 will have a fix for this (assuming Elgato is on the ball about it being an OSX bug)?.

Side note: Can I use a Harmony remote (which one? (http://www.logitech.com/index.cfm/remotes/universal_remotes/&cl=us,en)) to also do things like open and close TV stream windows and enter channel numbers directly? That would make the system a bit easier to use (less menu-y). Oooh I could also program it to go directly to sub-menu's in FrontRow. That would be awesome. Sorry, not trying to hijack the thread, just askin' ;)

Edit by me: okay these is already a thread for this in the forum (doh): http://www.avsforum.com/avs-vb/showthread.php?t=914821

Cheers,

Sean

Sean, look back earlier in thread for the "digital audio panic" info, it's in a couple of posts by Dick and by me, and then look in your logs after you get a kernel panic, it will look something like this:

"Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.6.0b3)@0x760000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x515000
dependency: com.apple.kext.OSvKernDSPLib(1.0)@0x75e000"

if it is indeed the digital audio bug.

I'll switch to system audio and see what happens.

Right, that's the second thing to do: because one thing those of us affected by this particular bug have in common is the kernel panics go away IF you switch to system sound out, period, end of sentence. If you still get panics or random shutdowns after doing this, you have some other problem.

Do yourself two other favors so you don't spin your wheels--pop your system restore disks in and run Apple Hardware Test, see if you get any errors. Also test your RAM with something a little more extensive, like Rember.

Hi all,
New to this forum but thought I should add my flavour to the thread. Ive just got my setup (<1mth). In summary Mac Mini Core 2 Duo, 2Gb RAM. Running Elgato Diversity and EyeTV 2.5. Using Digital Audio too. Kernel panics often, once every two days at least. Im pretty well over it....

Ive just taken the system back to bear bones and uninstalled EyeTV completely including all of the pref files. Ive removed all other co-resident SW and switched off all Energy Saving options. I then loaded EyeTV 2.5. Its been running for 2 days without incident so far and I'm still using the digital output. Im going to let it run until it panics again and see if I have any better luck. Stay tuned for this test.....

Using Digital Audio too. Kernel panics often, once every two days at least.

Yeah, now that my dual 500's are up and running, and we're back watching TV fairly regularly, the EyeTV digital audio kernel panics are still around. (10.4.10, 1.83 CD, two 500s, 2.4.1 or 2.5)

By the way, just did a search on the El Gato support pages, and I couldn't find what they're currently saying about this. Anyone have a link to the El Gato FAQ entry specifically mentioning it is an Apple OS X bug and there's nothing El Gato can do about it or has any public recognition of this been "disappeared?"