On Wednesday 09 November 2005 21:38, Jurgen Kramer wrote: > On Wed, 2005-11-09 at 18:47 +0100, Hans Verkuil wrote: > > On Wednesday 09 November 2005 08:04, Daan de Beer wrote: > > > maybe I was too hasty with my conclusion. Yesterday my recordings > > > made with 0.4.0 and firmware 0x02040011 had a lot of audio and video > > > artifacts. I am not sure what causes this, because they now all had > > > it from the start... > > > > > > I will make a stream available for testing. > > > > I looked at your stream and it is indeed very similar to a problem that > > I have too: after 5-10 minutes my pvr350 also suddenly shows audio and > > video artifacts. > > I am getting the exact same problems from my PVR-500. It seems that my > PVR-250 is not affected. After about 10 minutes when, mostly the real > recorded show starts, I keep getting those 'mpeg blocks'. Sounds seem to > be OK though. > > Does reverting to an older version of ivtv and/or firmware solve it? > > Jurgen > > Encoder revision: 0x02040011 > ivtv: version 0.4.0
Where can the stream be downloaded? I would like to see it, because I too have
a problem with my PVR350 which might be best descriped with 'mpeg blocks'.
They do not occur when the machine is freshly booted, but once they appear
they are there in every recording. When these recordings are watched in
Mythtv usually ends with lots of errors in dmesg. Watching the recording in
mplayer obviously works fine (it uses the xdriver for xv over ivtv-fb), so
that's what I'm doing when I have a bad recording.
Yesterday while watching such a bad recording with 'mpeg blocks and seemingly
OK sound' in Myth over the PVR350's tv-out (this gave no errors in dmesg) the
picture stopped moving. I let it sit there and I think it was after that,
that I got this in dmesg:
Nov 9 15:51:54 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 20 times -
Nov 9 15:55:42 [kernel] ivtv0 warning: Failed api call 0x00000015 with result
0xfffffff0
Nov 9 15:55:53 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 9 times -
Nov 9 15:57:34 [kernel] ivtv0 warning: DEC: couldnt read clock
Nov 9 15:57:45 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 2 times -
Nov 9 15:58:08 [kernel] ivtv0 warning: Failed api call 0x00000015 with result
0xfffffff0
Nov 9 15:58:19 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 8 times -
Nov 9 15:59:49 [kernel] ivtv0 warning: Failed api call 0x00000015 with result
0xfffffff0
Nov 9 15:59:49 [kernel] ivtv0 warning: DEC: couldnt read clock
Nov 9 16:00:01 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:00:01 [kernel] ivtv0 warning: Failed api call 0x00000015 with result
0xfffffff0
Nov 9 16:00:14 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 8 times -
Nov 9 16:01:46 [kernel] ivtv0 warning: Failed api call 0x00000015 with result
0xfffffff0
Nov 9 16:01:58 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 15 times -
Nov 9 16:04:50 [kernel] ivtv0 warning: Failed api call 0x00000015 with result
0xfffffff0
Nov 9 16:05:01 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated twice -
Nov 9 16:05:13 [kernel] ivtv0 warning: DEC: couldnt read clock
Nov 9 16:05:24 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 11 times -
Nov 9 16:07:29 [kernel] ivtv0 warning: 100 ms time out waiting for firmware
Nov 9 16:07:40 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 6 times -
Nov 9 16:25:41 [kernel] ivtv0 warning: Failed api call 0x00000044 with result
0xfffffff0
Nov 9 16:25:53 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:25:53 [kernel] ivtv0 warning: Failed api call 0x0000004f with result
0xfffffff0
Nov 9 16:26:05 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:26:05 [kernel] ivtv0 warning: Failed api call 0x0000004a with result
0xfffffff0
Nov 9 16:26:17 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:26:17 [kernel] ivtv0 warning: Failed api call 0x00000045 with result
0xfffffff0
Nov 9 16:26:28 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:26:28 [kernel] ivtv0 warning: Failed api call 0x0000004b with result
0xfffffff0
Nov 9 16:26:40 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:26:40 [kernel] ivtv0 warning: Failed api call 0x00000050 with result
0xfffffff0
Nov 9 16:26:43 [kernel] ivtv0 warning: No Free Mailbox for cmd 0x00000047
after 100 tries!
Nov 9 16:26:56 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 7 times -
Nov 9 16:28:35 [kernel] ivtv0 warning: Failed api call 0x00000044 with result
0xfffffff0
Nov 9 16:28:47 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:28:47 [kernel] ivtv0 warning: Failed api call 0x0000004f with result
0xfffffff0
Nov 9 16:28:59 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:28:59 [kernel] ivtv0 warning: Failed api call 0x0000004a with result
0xfffffff0
Nov 9 16:29:11 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:29:11 [kernel] ivtv0 warning: Failed api call 0x00000045 with result
0xfffffff0
Nov 9 16:29:23 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:29:23 [kernel] ivtv0 warning: Failed api call 0x0000004b with result
0xfffffff0
Nov 9 16:29:34 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
Nov 9 16:29:34 [kernel] ivtv0 warning: Failed api call 0x00000050 with result
0xfffffff0
Nov 9 16:29:38 [kernel] ivtv0 warning: No Free Mailbox for cmd 0x00000047
after 100 tries!
Nov 9 16:29:38 [kernel] ivtv0 warning: Mailbox[0] 0x00000053 flags 0x00000003
Nov 9 16:29:38 [kernel] ivtv0 warning: Mailbox[1] 0x00000053 flags 0x00000003
Nov 9 16:29:38 [kernel] ivtv0 warning: Firmware UNRESPONSIVE when trying cmd
0x00000047!!!
Nov 9 16:29:50 [kernel] ivtv0 warning: 1000 ms time out waiting for firmware
- Last output repeated 5 times -
Nov 9 16:30:54 [kernel] ivtv0 warning: IRQ: IVTV_IRQ_DEC_DMA_ERR
Nov 9 16:31:12 [kernel] ivtv0 warning: 100 ms time out waiting for firmware
Nov 9 16:31:12 [kernel] ivtv0 warning: Failed api call 0x0000000e with result
0xfffffff0
Nov 9 16:31:12 [kernel] ivtv0 warning: stop_fw error 4. Code -16
Nov 9 16:31:13 [kernel] ivtv0: Removed WinTV PVR 350, card #0
Nov 9 16:31:20 [kernel] ivtv: ==================== START INIT IVTV
====================
Nov 9 16:31:20 [kernel] ivtv: version 0.4.0 (tagged release) loading
Nov 9 16:31:20 [kernel] ivtv: Linux version: 2.6.13-gentoo-r3 preempt
gcc-3.4
Nov 9 16:31:20 [kernel] ivtv: In case of problems please include the debug
info
Nov 9 16:31:20 [kernel] ivtv: between the START INIT IVTV and END INIT IVTV
lines when
Nov 9 16:31:20 [kernel] ivtv: mailing the ivtv-devel mailinglist.
Nov 9 16:31:20 [kernel] ivtv0: Autodetected WinTV PVR 350 card (iTVC15 based)
Nov 9 16:31:20 [kernel] tveeprom: ivtv version
Nov 9 16:31:20 [kernel] ivtv0: i2c attach to card #0 ok [client=tveeprom,
addr=50]
Nov 9 16:31:21 [kernel] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv
i2c driver #0
Nov 9 16:31:21 [kernel] saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver
#0)
Nov 9 16:31:21 [kernel] ivtv0: i2c attach to card #0 ok [client=saa7115,
addr=21]
Nov 9 16:31:21 [kernel] saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver
#0)
Nov 9 16:31:21 [kernel] msp34xx: ivtv version
Nov 9 16:31:21 [kernel] ivtv0: i2c attach to card #0 ok [client=MSP3418W-A2,
addr=40]
Nov 9 16:31:22 [kernel] ivtv0: loading /lib/modules/ivtv-fw-enc.bin
Nov 9 16:31:22 [kernel] ivtv0: loading /lib/modules/ivtv-fw-dec.bin
Nov 9 16:31:22 [kernel] ivtv0: Encoder revision: 0x02050032
Nov 9 16:31:22 [kernel] ivtv0: Decoder revision: 0x02020023
<snip>
Then as you can see I stopped all of Myth, and lircd, removed all lirc and
ivtv modules and reloaded them. Then in principle it seems the machine is
error free again, unless I ofcourse watch the bad recording again using the
PVR350 decoder.
Do you also see this?
Rutger
machine: AMD64
ivtv: 0.4.0
Encoder revision: 0x02050032
Decoder revision: 0x02020023
pgpPAi11pKtui.pgp
Description: PGP signature
_______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
