View unanswered posts    View active topics

Board index KnoppMyth General

All times are UTC - 6 hours





Post new topic Reply to topic  Page 1 of 2
  [ 30 posts ] 
Go to page 1, 2  Next
Print view Previous topic   Next topic  
Author Message
Search for:
gummybear
 Post subject: Stream 2 Overflow
PostPosted: Fri Jul 22, 2005 6:32 pm 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
Started getting some jerky playback (pauses, etc.)

Checked the log and found several hundred entries like so:

Code:
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #215: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #216: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #217: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #218: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #219: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #220: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #221: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:24:46 mythtv kernel: ivtv: ENC Stream 2 OVERFLOW #222: Stealing a Buffer, 4194668 currently allocated
Jul 22 19:25:09 mythtv kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
Jul 22 19:25:09 mythtv kernel: agpgart: Device is in legacy mode, falling back to 2.x
Jul 22 19:25:09 mythtv kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
Jul 22 19:25:09 mythtv kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode


I'm guessing the ivtv driver is f'd up.

Anything other thoughts?
Top
 Profile  
 
khrusher
 Post subject:
PostPosted: Fri Jul 22, 2005 9:31 pm 
Offline
Joined: Tue Apr 13, 2004 6:51 pm
Posts: 890
Location: Groton, MA
several of us have this issue, seems to come and go. there are posts here that mention different ivtv version to try. A symptom of this issue is a full / patition as the error gets continually logged to syslog, kern.log, messages AND mythbackend.log

I havent had time to try the various ivtv versions, I have (for the time being) settle for a script that cleans up the logs

search here for logrotate, 'disk full' there is even a post from cesman on the topic (however his advice -- for once-- didn't help me)

please share if you solve this

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA
Top
 Profile  
 
gummybear
 Post subject:
PostPosted: Fri Jul 22, 2005 10:00 pm 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
Yeah, that log file is getting pretty big, in't it.

Writing all the crap to the log can't be very good for performance either.

I've got a very minimal system (mostly for heat and power reasons), and I can't afford much extra load.

Anyway, I turned off VBI encoding and that seems to have eliminated the error message in the log (at least for now).

I don't know if this truly fixes the problem or not, but here's the command I used:

ivtvctl -d /dev/video0 -x 0

I guess I'll see if it comes back tomorrow...

These ivtv 0.3 drivers are a real mess, BTW. Too many cooks in the kitchen and too many chipsets to deal with. I suppose it will get there eventually, but it's pretty painful right now.

Jon
Top
 Profile  
 
cesman
 Post subject:
PostPosted: Sun Jul 24, 2005 9:48 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
How about some hardware details?

_________________
cesman

When the source is open, the possibilities are endless!
Top
 Profile  
 
gummybear
 Post subject:
PostPosted: Mon Jul 25, 2005 9:17 am 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
    Biostar M7VIG 400
    Duron 800 Mobile
    Geforce4 MX4000
    Diamond PVR-550
    Netgear MA311
    Maxtor 200GB HD
    512MB RAM
Top
 Profile  
 
cesman
 Post subject:
PostPosted: Mon Jul 25, 2005 4:16 pm 
Offline
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location: Fontana, Ca
Does this occur in both live TV and recorded programs?

_________________
cesman

When the source is open, the possibilities are endless!
Top
 Profile  
 
gummybear
 Post subject:
PostPosted: Mon Jul 25, 2005 4:26 pm 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
cesman wrote:
Does this occur in both live TV and recorded programs?

I'm not really sure. When I was testing this, I was only using Live TV.

Since I did a clean install of R5A16 a few days ago, I disabled the VBI (per the command above) and haven't seen a trace of the error.

The strange thing is, I can set this parameter with ivtvctl -x 0, but if I look at the parameter with ivtvctl -X it shows that VBI is enabled. :?

Jon

p.s. One other thing I did differently in the last install was to disable closed captioning in mythtv-setup.
Top
 Profile  
 
khrusher
 Post subject:
PostPosted: Mon Jul 25, 2005 7:19 pm 
Offline
Joined: Tue Apr 13, 2004 6:51 pm
Posts: 890
Location: Groton, MA
this seems to happen durring backend recording for me. or at least NOT when watching Live.

seems to happen twice a week for me...I have a logfile cleaning cron entry, but a reboot usually makes the system happier once the logs are cleared

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA
Top
 Profile  
 
gummybear
 Post subject:
PostPosted: Mon Jul 25, 2005 8:26 pm 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
I just did a few backend recording test and the overflow errors haven't shown up in the log yet.

khrusher, What version of ivtv are you using?

Have you tried turning off logging in ivtv? Maybe try 'ivtv_debug=0' in your config.

It may not resolve the underlying problem, but maybe it will stop the log from filling up...
Top
 Profile  
 
khrusher
 Post subject:
PostPosted: Tue Jul 26, 2005 6:29 am 
Offline
Joined: Tue Apr 13, 2004 6:51 pm
Posts: 890
Location: Groton, MA
I am running ivtv: version 0.2.0 (rc3j)

Guess I'm not real sure where ivtv options would go...

I do see these files:

Code:
root@mythtv:/etc/mythtv/modules # ls
bttv  bttv0  bttv1  bttv2  bttv3  ivtv  ivtv0  ivtv1  ivtv2  ivtv3

root@mythtv:/etc/mythtv/modules # cat ivtv
alias char-major-81 videodev
alias char-major-61 lirc_serial
options msp3400 once=1 simple=1
# add below ivtv msp3400 saa7115 tuner
# add above ivtv lirc_dev lirc_i2c
root@mythtv:/etc/mythtv/modules # cat ivtv0
alias char-major-81-0 ivtv


Here is the bootup info, looks pretty clean to me

Code:
Jul 21 19:29:21 mythtv kernel: ivtv: ==================== START INIT IVTV ====================
Jul 21 19:29:21 mythtv kernel: ivtv: version 0.2.0 (rc3j) loading
Jul 21 19:29:21 mythtv kernel: ivtv: Linux version: 2.6.11.9-chw-2 SMP preempt 586 gcc-3.3
Jul 21 19:29:21 mythtv kernel: ivtv: In case of problems please include the debug info
Jul 21 19:29:21 mythtv kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when
Jul 21 19:29:21 mythtv kernel: ivtv: mailing the ivtv-devel mailinglist.
Jul 21 19:29:21 mythtv kernel: ivtv: Autodetected WinTV PVR 250 card
Jul 21 19:29:21 mythtv kernel: ivtv: Found an iTVC15 based chip
Jul 21 19:29:21 mythtv kernel: ivtv: XXX PCI device: 0x2570 vendor: 0x8086
Jul 21 19:29:21 mythtv kernel: ivtv: i2c attach [client=tveeprom[0],ok]
Jul 21 19:29:21 mythtv kernel: ivtv: Tuner Type 8, Tuner formats 0x00001000, Radio: yes, Model 0x009d7496, Revision 0x00000004
Jul 21 19:29:21 mythtv kernel: ivtv: NTSC tuner detected
Jul 21 19:29:21 mythtv kernel: ivtv: Radio detected
Jul 21 19:29:21 mythtv kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
Jul 21 19:29:21 mythtv kernel: ivtv: i2c attach [client=(tuner unset),ok]
Jul 21 19:29:21 mythtv kernel: saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
Jul 21 19:29:22 mythtv kernel: ivtv: i2c attach [client=saa7115[0],ok]
Jul 21 19:29:22 mythtv kernel: msp34xx: ivtv version
Jul 21 19:29:22 mythtv kernel: ivtv: i2c attach [client=MSP3435G-B6,ok]
Jul 21 19:29:23 mythtv kernel: ivtv: Encoder revision: 0x02040011
Jul 21 19:29:23 mythtv kernel: ivtv: Decoder revision: 0x02020023
Jul 21 19:29:23 mythtv kernel: ivtv: Configuring WinTV PVR 250 card with 5 streams
Jul 21 19:29:23 mythtv kernel: ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
Jul 21 19:29:23 mythtv kernel: ivtv: Registered v4l2 device, streamtype 0 minor 0
Jul 21 19:29:23 mythtv kernel: ivtv: Create DMA stream 1
Jul 21 19:29:23 mythtv kernel: ivtv: Registered v4l2 device, streamtype 1 minor 32
Jul 21 19:29:23 mythtv kernel: ivtv: Create stream 2 using 40 52224 byte buffers  2097152 kbytes total
Jul 21 19:29:23 mythtv kernel: ivtv: Registered v4l2 device, streamtype 2 minor 224
Jul 21 19:29:23 mythtv kernel: ivtv: Create DMA stream 3 using 455 4608 byte buffers  2097152 kbytes total
Jul 21 19:29:23 mythtv kernel: ivtv: Registered v4l2 device, streamtype 3 minor 24
Jul 21 19:29:23 mythtv kernel: ivtv: Create stream 4
Jul 21 19:29:23 mythtv kernel: ivtv: Registered v4l2 device, streamtype 4 minor 64
Jul 21 19:29:23 mythtv kernel: ivtv: Setting Tuner 8
Jul 21 19:29:23 mythtv kernel: tuner: type set to 8 (Temic NTSC (4036 FY5)) by ivtv i2c driver #0
Jul 21 19:29:23 mythtv kernel: ivtv: Setting audio matrix to input 3, output 1
Jul 21 19:29:23 mythtv kernel: ivtv: Switching standard to NTSC.
Jul 21 19:29:23 mythtv kernel: ivtv: ivtv_enc_thread: pid = 3334, itv = 0xe0b52aa0
Jul 21 19:29:23 mythtv kernel: ivtv: Initialized WinTV PVR 250, card #0
Jul 21 19:29:23 mythtv kernel: ivtv: Autodetected WinTV PVR 250 card
Jul 21 19:29:23 mythtv kernel: ivtv: Found an iTVC15 based chip
ul 21 19:29:23 mythtv kernel: ivtv: XXX PCI device: 0x2570 vendor: 0x8086
Jul 21 19:29:23 mythtv kernel: ivtv: i2c attach [client=tveeprom[1],ok]
Jul 21 19:29:23 mythtv kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #1
Jul 21 19:29:23 mythtv kernel: ivtv: i2c attach [client=(tuner unset),ok]
Jul 21 19:29:23 mythtv kernel: saa7115: starting probe for adapter ivtv i2c driver #1 (0x10005)
Jul 21 19:29:24 mythtv kernel: ivtv: i2c attach [client=saa7115[1],ok]
Jul 21 19:29:24 mythtv kernel: msp34xx: ivtv version
Jul 21 19:29:24 mythtv kernel: ivtv: i2c attach [client=MSP3448W-A2,ok]
Jul 21 19:29:24 mythtv kernel: ivtv: Tuner Type 2, Tuner formats 0x00001000, Radio: yes, Model 0x00a51450, Revision 0x00000000
Jul 21 19:29:24 mythtv kernel: ivtv: NTSC tuner detected
Jul 21 19:29:24 mythtv kernel: ivtv: Radio detected
Jul 21 19:29:25 mythtv kernel: ivtv: Encoder revision: 0x02040011
Jul 21 19:29:25 mythtv kernel: ivtv: Decoder revision: 0x02020023
Jul 21 19:29:25 mythtv kernel: ivtv: Configuring WinTV PVR 250 card with 5 streams
Jul 21 19:29:25 mythtv kernel: ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
Jul 21 19:29:25 mythtv kernel: ivtv: Registered v4l2 device, streamtype 0 minor 1
Jul 21 19:29:25 mythtv kernel: ivtv: Create DMA stream 1
Jul 21 19:29:25 mythtv kernel: ivtv: Registered v4l2 device, streamtype 1 minor 33
Jul 21 19:29:25 mythtv kernel: ivtv: Create stream 2 using 40 52224 byte buffers  2097152 kbytes total
Jul 21 19:29:25 mythtv kernel: ivtv: Registered v4l2 device, streamtype 2 minor 225
Jul 21 19:29:25 mythtv kernel: ivtv: Create DMA stream 3 using 455 4608 byte buffers  2097152 kbytes total
Jul 21 19:29:25 mythtv kernel: ivtv: Registered v4l2 device, streamtype 3 minor 25
Jul 21 19:29:25 mythtv kernel: ivtv: Create stream 4
Jul 21 19:29:25 mythtv kernel: ivtv: Registered v4l2 device, streamtype 4 minor 65
Jul 21 19:29:25 mythtv kernel: ivtv: Setting Tuner 2
Jul 21 19:29:25 mythtv kernel: tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles)) by ivtv i2c driver #1
Jul 21 19:29:25 mythtv kernel: ivtv: Setting audio matrix to input 3, output 1
Jul 21 19:29:25 mythtv kernel: ivtv: Switching standard to NTSC.
Jul 21 19:29:25 mythtv kernel: ivtv: ivtv_enc_thread: pid = 3391, itv = 0xe0b66e00
Jul 21 19:29:25 mythtv kernel: ivtv: Initialized WinTV PVR 250, card #1
Jul 21 19:29:25 mythtv kernel: ivtv: ====================  END INIT IVTV  ====================

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA
Top
 Profile  
 
gummybear
 Post subject:
PostPosted: Tue Jul 26, 2005 8:19 am 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
khrusher wrote:
I am running ivtv: version 0.2.0 (rc3j)

Well, first I would try using the ivtvctl command I mentioned above from a shell and see if that helps. You might have to do this for each tuner if you've got multiple tuners setup.

You could also try turning off closed captioning in mythtv-setup (assuming you don't need this).

If that doesn't work, you could try disabling the ivtv logging:

Code:
root@mythtv:/etc/mythtv/modules # cat ivtv
alias char-major-81 videodev
alias char-major-61 lirc_serial
options msp3400 once=1 simple=1
options ivtv ivtv_debug=0
# add below ivtv msp3400 saa7115 tuner
# add above ivtv lirc_dev lirc_i2c
Top
 Profile  
 
khrusher
 Post subject:
PostPosted: Tue Jul 26, 2005 9:17 am 
Offline
Joined: Tue Apr 13, 2004 6:51 pm
Posts: 890
Location: Groton, MA
I tried the ivtvctl -x 0 command btu got the same result
Quote:
"but if I look at the parameter with ivtvctl -X it shows that VBI is enabled. "

I have added the line
Code:
options ivtv ivtv_debug=0

to /etc/mythtv/modules/ivtv and ivtv1 as I have two tuners.

We'll see :)

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA
Top
 Profile  
 
gummybear
 Post subject:
PostPosted: Fri Jul 29, 2005 7:36 am 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
gummybear wrote:
"but if I look at the parameter with ivtvctl -X it shows that VBI is enabled. "

khrusher wrote:
I tried the ivtvctl -x 0 command btu got the same result

Apparently this needs to be done as root; mine seems to be sticking now.

Haven't seen that error come back yet. I am using ivtv 0.3.3 with ivtv_debug=1
Top
 Profile  
 
khrusher
 Post subject:
PostPosted: Tue Aug 09, 2005 1:38 pm 
Offline
Joined: Tue Apr 13, 2004 6:51 pm
Posts: 890
Location: Groton, MA
Well, its been two weeks since I added ivtv_debug=0 parameter.

I haven't seen the disk filling log dumps since. Now, I can't confirm this is the fix, could be coincidence, but the issue was occuring about 3 times a week.

I'll report back if issue returns.

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA
Top
 Profile  
 
gummybear
 Post subject:
PostPosted: Tue Aug 09, 2005 1:53 pm 
Offline
Joined: Mon Jul 04, 2005 8:25 pm
Posts: 114
khrusher wrote:
Well, its been two weeks since I added ivtv_debug=0 parameter.

I haven't seen the disk filling log dumps since. Now, I can't confirm this is the fix, could be coincidence, but the issue was occuring about 3 times a week.

I'll report back if issue returns.


That's good, but I don't think it's actually fixing the problem; you just can't see the error because you've disabled logging.

Turning off the VBI as root seemed to do it for me, and I've still got ivtv logging enabled.

Jon
Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 2
  [ 30 posts ] 
Go to page 1, 2  Next


Board index KnoppMyth General

All times are UTC - 6 hours




Who is online

Users browsing this forum: Bing [Bot] and 4 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu