Just wild-ass curiosity: I'm not having these problems, not even using VIA chipsets or amd64 chips - but I was just curious: can stuff like this get debugged by running in Xen, or VMWare for that matter? How much of a trick/hack would it be to have ivtv (+ myth) running under one of these virtualizers, if it can be done at all?
--- Mike Benoit <[EMAIL PROTECTED]> wrote: > Your not alone. I'm seeing the exact same issue. It > seems to mostly > happen when I'm recording 2 shows and watching a 3rd > on a different > frontend. I too am using a VIA chipset mainboard, > (KT400). > > I'm running a PVR-500 on ivtv 0.3.5 (k) and kernel > 2.6.11.8. > > > messages.3.gz:May 29 14:21:39 mythtv syslogd 1.4.1: > restart. > messages.3.gz:May 30 14:13:32 mythtv syslogd 1.4.1: > restart. > messages.3.gz:Jun 3 00:17:52 mythtv syslogd 1.4.1: > restart. > messages.3.gz:Jun 4 18:13:11 mythtv syslogd 1.4.1: > restart. > messages.2.gz:Jun 5 05:11:29 mythtv syslogd 1.4.1: > restart. > messages.2.gz:Jun 5 19:32:15 mythtv syslogd 1.4.1: > restart. > messages.2.gz:Jun 11 17:22:09 mythtv syslogd 1.4.1: > restart. > messages.1.gz:Jun 12 05:03:35 mythtv syslogd 1.4.1: > restart. > messages.1.gz:Jun 15 17:28:08 mythtv syslogd 1.4.1: > restart. > messages.1.gz:Jun 16 17:24:01 mythtv syslogd 1.4.1: > restart. > messages.1.gz:Jun 16 17:56:07 mythtv syslogd 1.4.1: > restart. > messages.1.gz:Jun 16 18:03:05 mythtv syslogd 1.4.1: > restart. > messages.1.gz:Jun 18 17:12:20 mythtv syslogd 1.4.1: > restart. > messages:Jun 19 05:03:42 mythtv syslogd 1.4.1: > restart. > > > On Mon, 2005-06-20 at 23:59 -0500, Michael Carland > wrote: > > Hello, > > > > I'm not 100% certain this is caused by ivtv, but > this list wins the > > friendliest/most knowledgeable contest, and the > prize is my question. > > > > I have an AMD64 machine running Debian sarge with > 2.6.11.7, in 32 bit > > mode. It's sole purpose is to run mythbackend > (.18). It has a single > > PVR-500MCE with ivtv 0.3.6e. I have a second > PVR-500 I'd like to add, > > but am trying to resolve this problem first. One > possible problem is my > > MB has a VIA chipset. It is an MSI K8T Neo2-F (I > was looking for AMD64 > > with a good number of PCI). > > > > The problem is it reboots spontaneously. There is > nothing in the logs, > > I even had the kernel use ttyS0 as the console, > and had another machine > > capture the output. Still nothing interesting. It > seems to happen more > > frequently if the machine is busier. I haven't > seen a reboot when it > > records a single program at a time, for weeks on > end. But if I am > > viewing something prerecorded (over NFS) while it > is recording, it is > > very likely I will get a reboot within 30 minutes. > I don't remember any > > reboots when I just view prerecorded video while > it is not recording. > > > > This has occured with older versions of the ivtv > driver, and although I > > am now using the firmware that came with the card, > I've also had > > problems with 0x02040011. I am not using any > module options. > > > > My questions: Is there a better way to determine > what is going wrong. > > Console to the serial port didn't capture the > error, and the machine > > reboots so fast, if I sat and watched the monitor, > and it did say > > something, I doubt I would be able to read it. > I've also read posts on > > this list that there people have had problems with > VIA chipsets. Does > > anyone know if these same problems happen with > these chipsets under > > Windoze? If not, would it be that Windoze isn't as > demanding of the > > chipset as linux is, or more likely the linux > drivers have problems > > because VIA doesn't give OSS developers the > datasheets they need? > > > > I'm going to try 2.6.12 now and see if that makes > a difference. I read > > something in the changelog about changing the way > interrupts are > > handled with VIA. I couldn't tell it that was > relevant to my situation, > > but it can't hurt to try. If anyone has > suggestions on how to narrow > > this down, before I have to buy a new MB, I'd > appreciate it. > > > > Thanks, > > > > -Michael > > > > > > Jun 20 23:14:35 stern kernel: ivtv: > ==================== START INIT > > IVTV ==================== > > Jun 20 23:14:35 stern kernel: ivtv: version 0.3.6 > (e) loading > > Jun 20 23:14:35 stern kernel: ivtv: Linux version: > 2.6.11.7 preempt K8 > > gcc-3.3 > > Jun 20 23:14:35 stern kernel: ivtv: In case of > problems please include > > the debug info > > Jun 20 23:14:35 stern kernel: ivtv: between the > START INIT IVTV and END > > INIT IVTV lines when > > Jun 20 23:14:35 stern kernel: ivtv: mailing the > ivtv-devel mailinglist. > > Jun 20 23:14:35 stern kernel: ivtv: Autodetected > WinTV PVR 150 card > > Jun 20 23:14:35 stern kernel: ivtv: Found an > iTVC16 based chip > > Jun 20 23:14:35 stern kernel: ACPI: PCI interrupt > 0000:02:08.0[A] -> > > GSI 17 (level, low) -> IRQ 17 > > Jun 20 23:14:35 stern kernel: ivtv: VIA PCI > device: 0x0282 vendor: > > 0x1106 > > Jun 20 23:14:35 stern kernel: tveeprom: Hauppauge: > model = 23552, rev = > > D592, serial# = 2943000 > > Jun 20 23:14:35 stern kernel: tveeprom: tuner = > Philips FQ1236A MK4 > > (idx = 92, type = 57) > > Jun 20 23:14:35 stern kernel: tveeprom: tuner fmt > = NTSC(M) (eeprom = > > 0x08, v4l2 = 0x00001000) > > Jun 20 23:14:35 stern kernel: tveeprom: > audio_processor = MSP3410D > > (type = 5) > > Jun 20 23:14:35 stern kernel: ivtv: i2c attach > [client=tveeprom[50],ok] > > Jun 20 23:14:35 stern kernel: ivtv: Tuner Type 57, > Tuner formats > > 0x00001000, Radio: yes, Model 0x00915652, Revision > 0x00000000 > > Jun 20 23:14:35 stern kernel: ivtv: NTSC tuner > detected > > Jun 20 23:14:35 stern kernel: ivtv: Radio detected > > Jun 20 23:14:35 stern kernel: tuner: Ignoring > new-style parameters in > > presence of obsolete ones > > Jun 20 23:14:35 stern kernel: tuner: chip found at > addr 0xc2 i2c-bus > > ivtv i2c driver #0 > > Jun 20 23:14:35 stern kernel: ivtv: i2c attach > [client=(tuner unset),ok] > > Jun 20 23:14:36 stern kernel: cx25840: requesting > firmware > > Jun 20 23:14:40 stern kernel: cx25840: firmware > loaded > > Jun 20 23:14:40 stern kernel: ivtv: i2c attach > [client=cx25840[50],ok] > > Jun 20 23:14:40 stern kernel: ivtv: i2c attach > [client=wm8775[50],ok] > > Jun 20 23:14:42 stern kernel: ivtv: Encoder > revision: 0x02050032 > > Jun 20 23:14:42 stern kernel: ivtv: Encoder > Firmware may be buggy, use > > version 0x02040011 > > Jun 20 23:14:42 stern kernel: ivtv: Configuring > WinTV PVR 150 card with > > 5 streams > > Jun 20 23:14:42 stern kernel: ivtv: Registered > v4l2 device, streamtype > > 0 minor 0 > > Jun 20 23:14:42 stern kernel: ivtv: Create DMA > stream 0 using 512 4096 > > byte buffers 0 kbytes total > > Jun 20 23:14:42 stern kernel: ivtv: Registered > v4l2 device, streamtype > > 1 minor 32 > === message truncated === ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
