hi people,

i am running 13.1 with a custom compiled kernel (2.6.35.10) with the following changes applied to it: http://linuxtv.org/wiki/index.php/Le...Fast_DTV2000DS (see down the page).

system runs fine for 3 or 4 days and then i get this: http://img20.imageshack.us/img20/3268/errorif.png

any idea what it may be?

When you play with the kernel and development code, you should expect the kernel panics.

The moral of the story: do not mess with the kernel, unless you know what you do and/or you know programming.

As far as I understand it, you have a device that is not yet supported by Linux. If I were you, I would stand in the latest kernel, with the hope that one day, it will work with this device.

Afatech 9015 is supported from 2.6.37-rc8, at least is my dvb-t usb-dongle working great. I built it following Alien Bob's brilliant how-to. Can't say if it works with a pci card, but I would try that solution instead of messing with external modules if I had one of those.

Good luck!

Jan-C

To read the kernel panic and figure out exactly what is going on requires some knowledge. I've been a programmer for a long time, but on Windows and mainframes, not Linux.

However, here's the rules: The top part of the screen (above the long, wrapped line) is a simple trace backwards in time from the point of failure to a few calls before. Then a dump of the exact instructions that failed, followed by an error message, followed by a more detailed trace, again most recent call to oldest call at the bottom of the screen. Please note that the terms 'most recent' and 'oldest' only refer to the on-screen text, which covers a few milliseconds at best, and not to 3 or 4 days' trace.

The confusing thing is that the numbers on the left increase as we get older. Well, those numbers describe when the output happened, not when the event on the line happened.

Starting with the upper part, then, begin with the line immediately above the long line of output:
The cpu appears to go idle; we examine the acpi info to see how to handle idle; suddenly an apic interrupt!; we die.

The lower portion does the same in a bit more detail:
The cpu appears to go idle; we examine acpi info to see how to handle this; apic interrupt, passed off to smp_apic_interrupt; irq exits; then things start to go south.

If I were you I' examine my options around cpu idling and APIC handling, as a start, or any newly added patches. Which you're doing. I'd also do what you're doing and post something somewhere.

Also, you should note as much detail as you can: are you actually using the machine (mouse moving, typing, watching videos) when it fails? Does it always fail when you're away; when waking up; when plugging in USB stuff, etc. Is the TV stuff trying to start recording, or playing, or stopping? The TV card and the panic may or may not be related.

You could try removing the TV card, making sure the modules aren't loaded, and run for a few days to see if you can repeat the panic. Add back in the card, test again.

Good luck!

1 members found this post helpful.

wasn't aware of the work in 2.6.37-rc8. i compiled 2.6.37 (according to alienbob's guide and using config from -current to start with)... but no luck. i cannot get a channel lock. i do sometimes after a long time but that's maybe one in 10 attempts. i wish i never got this stupid card!

What about the firmware, I'm using this:
http://palosaari.fi/linux/v4l-dvb/fi...-usb-af9015.fw
In your first post's link to linuxtv.org it was mentioned that a downgrade of the firmware might help with some errors. What program do you use? I tried xine, mplayer, vlc and kaffeine and settled with kaffeine due to the simple-to-use gui and recording features.

i have tried 4.95 and 5.1 versions of the firmware and the problems with channel lock are still there. i'm using mythtv.