[mythtv-users] DevRdB(/dev/video0) Error: Poll giving up

Brian J. Murrell brian at interlinx.bc.ca
Thu May 6 17:44:03 UTC 2010


I have a BE/FE running 0.22-fixes which I've recently moved to a new
motherboard (Abit NF7-S FWIW).  Included in the hardware is one PVR-150
and one PVR-500 (for a total of 3 tuners, of course).

Since moving all of this to this new hardware, I have been experiencing
random recording failures on random PVR devices.  When the recording
failure happens, I see the following in the backend log:

2010-05-05 21:42:17.556 DevRdB(/dev/video0) Error: Poll giving up
2010-05-05 21:42:17.796 MPEGRec(/dev/video0) Error: Device error detected
2010-05-05 21:42:17.942 DevRdB(/dev/video0): Stop(): Not running.
2010-05-05 21:42:20.913 DevRdB(/dev/video0) Error: Poll giving up
2010-05-05 21:42:20.919 MPEGRec(/dev/video0) Error: Device error detected
2010-05-05 21:42:20.922 DevRdB(/dev/video0): Stop(): Not running.
...
2010-05-05 21:55:08.585 DevRdB(/dev/video0) Error: Start(): pthread_create failed.
                        eno: Resource temporarily unavailable (11)
2010-05-05 21:55:08.898 MPEGRec(/dev/video0) Error: Device error detected
2010-05-05 21:55:08.899 DevRdB(/dev/video0): Stop(): Not running.
2010-05-05 21:55:09.334 DevRdB(/dev/video0) Error: Start(): pthread_create failed.
                        eno: Resource temporarily unavailable (11)
2010-05-05 21:55:09.335 MPEGRec(/dev/video0) Error: Device error detected
2010-05-05 21:55:09.336 DevRdB(/dev/video0): Stop(): Not running.

/dev/video0 is the PVR-250 and /dev/video{1,2} are the PVR-500:

[   16.088289] ivtv0: Autodetected Hauppauge WinTV PVR-250
[   17.733278] ivtv1: Autodetected WinTV PVR 500 (unit #1)
[   19.607074] ivtv2: Autodetected WinTV PVR 500 (unit #2)

This failure seems to happen to all of /dev/video{0,1,2} devices at one
time or another and does not happen all of the time.  Sometimes it
happens when only a single device is being used.

It usually happens right from the beginning of an attempted recording,
but as you can see from the example pasted above, it actually happened
42 minutes into a recording!  The above recording started at 21:00 and
recorded fine until 21:42:17, per above.

$ dmesg | grep ivtv tells me:

[   16.032384] ivtv: Start initialization, version 1.4.1
[   16.032577] ivtv0: Initializing card 0
[   16.032584] ivtv0: Autodetected Hauppauge card (cx23416 based)
[   16.032683] ivtv 0000:01:07.0: PCI INT A -> Link[APC4] -> GSI 19 (level, high) -> IRQ 19
[   16.032696] ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
[   16.088289] ivtv0: Autodetected Hauppauge WinTV PVR-250
[   16.155481] saa7115 2-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
[   17.150513] msp3400 2-0040: MSP3445G-B8 found @ 0x80 (ivtv i2c driver #0)
[   17.604179] tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[   17.670947] IRQ 19/ivtv0: IRQF_DISABLED is not guaranteed on shared IRQs
[   17.671352] ivtv0: Registered device video0 for encoder MPG (4096 kB)
[   17.671377] ivtv0: Registered device video32 for encoder YUV (2048 kB)
[   17.671400] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
[   17.671428] ivtv0: Registered device video24 for encoder PCM (320 kB)
[   17.671431] ivtv0: Initialized card: Hauppauge WinTV PVR-250
[   17.671577] ivtv1: Initializing card 1
[   17.671582] ivtv1: Autodetected Hauppauge card (cx23416 based)
[   17.671911] ivtv 0000:02:08.0: PCI INT A -> Link[APC1] -> GSI 16 (level, high) -> IRQ 16
[   17.671923] ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
[   17.733278] ivtv1: Autodetected WinTV PVR 500 (unit #1)
[   18.011435] cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
[   18.388898] tuner 3-0060: chip found @ 0xc0 (ivtv i2c driver #1)
[   18.644360] tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #1)
[   18.652027] ivtv 0000:01:07.0: firmware: requesting v4l-cx2341x-enc.fw
[   19.109215] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[   19.308171] ivtv0: Encoder revision: 0x02060039
[   19.392801] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1)
[   19.527623] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1)
[   19.540953] IRQ 16/ivtv1: IRQF_DISABLED is not guaranteed on shared IRQs
[   19.541392] ivtv1: Registered device video1 for encoder MPG (4096 kB)
[   19.541420] ivtv1: Registered device video33 for encoder YUV (2048 kB)
[   19.541445] ivtv1: Registered device vbi1 for encoder VBI (1024 kB)
[   19.541470] ivtv1: Registered device video25 for encoder PCM (320 kB)
[   19.541494] ivtv1: Registered device radio1 for encoder radio
[   19.541497] ivtv1: Initialized card: WinTV PVR 500 (unit #1)
[   19.541643] ivtv2: Initializing card 2
[   19.541648] ivtv2: Autodetected Hauppauge card (cx23416 based)
[   19.541977] ivtv 0000:02:09.0: PCI INT A -> Link[APC2] -> GSI 17 (level, high) -> IRQ 17
[   19.541990] ivtv2: Unreasonably low latency timer, setting to 64 (was 32)
[   19.607071] ivtv2: Correcting tveeprom data: no radio present on second unit
[   19.607074] ivtv2: Autodetected WinTV PVR 500 (unit #2)
[   19.611485] cx25840 4-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #2)
[   19.626171] tuner 4-0043: chip found @ 0x86 (ivtv i2c driver #2)
[   19.635843] tuner 4-0061: chip found @ 0xc2 (ivtv i2c driver #2)
[   19.638343] wm8775 4-001b: chip found @ 0x36 (ivtv i2c driver #2)
[   19.648269] IRQ 17/ivtv2: IRQF_DISABLED is not guaranteed on shared IRQs
[   19.649473] ivtv2: Registered device video2 for encoder MPG (4096 kB)
[   19.649504] ivtv2: Registered device video34 for encoder YUV (2048 kB)
[   19.649532] ivtv2: Registered device vbi2 for encoder VBI (1024 kB)
[   19.649564] ivtv2: Registered device video26 for encoder PCM (320 kB)
[   19.649567] ivtv2: Initialized card: WinTV PVR 500 (unit #2)
[   19.649596] ivtv: End initialization
[   20.204025] ivtv 0000:02:08.0: firmware: requesting v4l-cx2341x-enc.fw
[   20.239067] ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[   20.276023] ivtv 0000:02:09.0: firmware: requesting v4l-cx2341x-enc.fw
[   20.311528] ivtv2: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[   20.436179] ivtv1: Encoder revision: 0x02060039
[   20.508181] ivtv2: Encoder revision: 0x02060039
[59112.076065] ivtv0: All encoder MPG stream buffers are full. Dropping data.
[59112.076069] ivtv0: Cause: the application is not reading fast enough.

and then there are some:

[268549.360036] ivtv0: DMA TIMEOUT 00000001 0
[268552.920025] ivtv0: DMA TIMEOUT 00000001 0
[268555.888022] ivtv0: DMA TIMEOUT 00000001 0
[268558.892018] ivtv0: DMA TIMEOUT 00000001 0
[268561.828023] ivtv0: DMA TIMEOUT 00000001 0
[268564.800021] ivtv0: DMA TIMEOUT 00000001 0

messages.  And looking at the timestamped version of those messages, I
can see that they do correlate to the above failure:

May  5 16:11:21 pvr kernel: [248695.256331] i2c-adapter i2c-2: sendbytes: NAK bailout.
May  5 16:11:21 pvr kernel: [248695.256370] msp3400 2-0040: I/O error #0 (read 0x10/0x200)
May  5 21:09:19 pvr kernel: [266572.975561] i2c-adapter i2c-2: sendbytes: NAK bailout.
May  5 21:09:19 pvr kernel: [266572.975661] msp3400 2-0040: I/O error #0 (read 0x10/0x200)
May  5 21:16:58 pvr kernel: [267032.152884] agpgart-nvidia 0000:00:00.0: AGP 3.0 bridge
May  5 21:16:58 pvr kernel: [267032.152904] agpgart-nvidia 0000:00:00.0: putting AGP V3 device into 8x mode
May  5 21:16:58 pvr kernel: [267032.153002] nvidia 0000:03:00.0: putting AGP V3 device into 8x mode
May  5 21:35:36 pvr kernel: [268150.362453] i2c-adapter i2c-2: sendbytes: NAK bailout.
May  5 21:35:36 pvr kernel: [268150.362489] msp3400 2-0040: I/O error #0 (read 0x10/0x200)
May  5 21:42:15 pvr kernel: [268549.360036] ivtv0: DMA TIMEOUT 00000001 0
May  5 21:42:18 pvr kernel: [268552.920025] ivtv0: DMA TIMEOUT 00000001 0
May  5 21:42:21 pvr kernel: [268555.888022] ivtv0: DMA TIMEOUT 00000001 0
May  5 21:42:24 pvr kernel: [268558.892018] ivtv0: DMA TIMEOUT 00000001 0
May  5 21:42:27 pvr kernel: [268561.828023] ivtv0: DMA TIMEOUT 00000001 0

Notice the first "DMA TIMEOUT" message at 21:42:15 only 2 seconds before
the first "DevRdB(/dev/video0) Error: Poll giving up" message.

That said, there are other recording failures which don't have any "DMA
TIMEOUT" messages associated with them.

Any ideas?

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100506/eda5d6b0/attachment.pgp>


More information about the mythtv-users mailing list