I does not seem related, as it seems you had a running box before upgrading the kernel, but I had this very ENC_DMAXFER problem when using a motherboard with a VIA chipset. My 350 seems to be very sensible to DMA problems.
Changing to another motherboard without a VIA chipset got me a very stable PVR. I'm running mythtv fine with ivtv-0.4.1 from svn and kernel 2.6.10. On 12/3/05, Mark Knecht <[EMAIL PROTECTED]> wrote: > On 12/3/05, Hans Verkuil <[EMAIL PROTECTED]> wrote: > > On Saturday 03 December 2005 16:45, Mark Knecht wrote: > > > On 12/3/05, Hans Verkuil <[EMAIL PROTECTED]> wrote: > > > > On Saturday 03 December 2005 16:17, Mark Knecht wrote: > > > > > Ah, come on. No one can venture a guess? > > > > > > > > > > This machine has run ivtv and MythTV for months. After a recent > > > > > kernel (2.6.12 to 2.6.14) upgrade this message started happening > > > > > AND the machine has gotten flaky. Thisis the only message I'm > > > > > getting that seems different from before the upgrade. > > > > > > > > > > HELP! > > > > > > > > > > - Mark > > > > > > > > > > On 12/2/05, Mark Knecht <[EMAIL PROTECTED]> wrote: > > > > > > > ivtv: ==================== END INIT IVTV > > > > > > > ==================== ivtv0 warning: ENC: REG_DMAXFER 2 wait > > > > > > > failed > > > > > > > ivtv0 warning: DEC: REG_ENCSG1LEN wait failed > > > > > > > > > > > > > > thanks, > > > > > > > Mark > > > > > > > > Was the kernel upgrade the only thing that changed? For me 2.6.12 > > > > was flaky (spontaneous crashes, etc.) while 2.6.14 is solid. > > > > > > > > The messages mean that a DMA transfer didn't start. Why? Don't > > > > know. But if it only happened after a kernel update and they > > > > disappear when you go back to 2.6.12, then that can be interesting > > > > to investigate. > > > > > > > > Hans > > > > > > Hans, > > > Does this message mean DMA is completely stopped? That would > > > explain some things. What I do see is that when MythTV starts > > > recording a file is opened but the size never grows. If so, the > > > message should be changed from a warning to a big FAIL! > > > > That's very likely, yes. > > > > > > > > Immediately after the kernel upgrade I didn't see these messages > > > and the system was working. I left my parents house and came back > > > home 350 miles north. I then got a call the next day with info that > > > the system was no longer working. IIRC he had rebooted for some > > > reason. I've been looking at it off and on over the last week. This > > > warning message is the only real clue from an ivtv perspective. > > > > > > I'll see about a reboot into the old kernel. > > > > OK. I know there are other DMA problems (ticket #49) but I want to > > finish a bunch of other tasks first in the next two weeks or so. > > > > Hans > > OK, something is pretty messed up with this machine. I went back the > older kernel. The only difference at this point is that I tried > ivtv-0.4.0-r2 instead of 0.3.7 that I ran earlier. When I first boot > the machine dmesg looks good. I then try to capture video without > MythTV and that fails. I looks at dmesg again and I see that DMA has > failed: > > EXT3 FS on sdb2, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > Linux video capture interface: v1.00 > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.4.0 (tagged release) loading > ivtv: Linux version: 2.6.12-gentoo-r6 preempt K7 gcc-3.3 > ivtv: In case of problems please include the debug info > ivtv: between the START INIT IVTV and END INIT IVTV lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv0: Autodetected WinTV PVR 150 card (iTVC16 based) > ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 11 > ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [LNK1] -> GSI 11 (level, > low) -> IRQ 11 > ivtv0: Unreasonably low latency timer, setting to 64 (was 32) > tveeprom: ivtv version > tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 2978579 > tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50) > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) > tveeprom: audio processor = CX25841 (type = 23) > tveeprom: decoder processor = CX25841 (type = 1c) > ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] > tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 > ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] > cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0) > cx25840 2-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes) > ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) > ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] > ivtv0: loading /lib/modules/ivtv-fw-enc.bin > ivtv0: Encoder revision: 0x02050032 > ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) > ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) > ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) > ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB > total) > tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0 > ivtv0: Initialized WinTV PVR 150, card #0 > ivtv: ==================== END INIT IVTV ==================== > [EMAIL PROTECTED] ~ $ cat /dev/video0 >test.mpg > > [EMAIL PROTECTED] ~ $ ls -al test.mpg > -rw-r--r-- 1 mark users 0 Dec 3 09:04 test.mpg > [EMAIL PROTECTED] ~ $ uname -r > 2.6.12-gentoo-r6 > [EMAIL PROTECTED] ~ $ dmesg > processor honours the WP bit even in supervisor mode... Ok. > Calibrating delay loop... 3612.67 BogoMIPS (lpj=1806336) > Mount-cache hash table entries: 512 > CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 > 00000000 00000000 00000000 > <SNIP> > EXT3 FS on sdb2, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > Linux video capture interface: v1.00 > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.4.0 (tagged release) loading > ivtv: Linux version: 2.6.12-gentoo-r6 preempt K7 gcc-3.3 > ivtv: In case of problems please include the debug info > ivtv: between the START INIT IVTV and END INIT IVTV lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv0: Autodetected WinTV PVR 150 card (iTVC16 based) > ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 11 > ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [LNK1] -> GSI 11 (level, > low) -> IRQ 11 > ivtv0: Unreasonably low latency timer, setting to 64 (was 32) > tveeprom: ivtv version > tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 2978579 > tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50) > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) > tveeprom: audio processor = CX25841 (type = 23) > tveeprom: decoder processor = CX25841 (type = 1c) > ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] > tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 > ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] > cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0) > cx25840 2-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes) > ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) > ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] > ivtv0: loading /lib/modules/ivtv-fw-enc.bin > ivtv0: Encoder revision: 0x02050032 > ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) > ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) > ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) > ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB > total) > tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0 > ivtv0: Initialized WinTV PVR 150, card #0 > ivtv: ==================== END INIT IVTV ==================== > ivtv0 warning: ENC: REG_DMAXFER 2 wait failed > ivtv0 warning: ENC: DMA still Pending while stopping capture! > ivtv0 warning: DEC: REG_ENCSG1LEN wait failed > [EMAIL PROTECTED] ~ $ > [EMAIL PROTECTED] ~ $ > > I suppose I could try going back to 0.3.7 and seeif that makes any difference. > > What's the chances that the PVR-150 has died?????? > > Thanks, > Mark > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
