Hi all,
I'm having trouble with R5A30.2 crashing, I installed mbemon to see if it would help. last night the machine crashed so i checked the logs that it talked about in the program and found three,mebmon.log, mythbackend.log, and mythbackend.log-1, that have info about the crash. Here is mbemon:

mbemon started Wed Nov 8 17:06:15 EST 2006

Problem encountered on Thu Nov 9 22:13:33 EST 2006
Log file size of 1392 blocks is too large -- probable runaway
Halting backend
Stopping MythTV server: mythbackend .
Capturing back end log file
Restarting backend
Starting MythTV server: mythbackend.
Restarting gdm

Problem encountered on Thu Nov 9 22:28:41 EST 2006
Log file size of 1560 blocks is too large -- probable runaway
Halting backend
Stopping MythTV server: mythbackend .
Capturing back end log file
Restarting backend
Starting MythTV server: mythbackend.
Restarting gdm


This is a small portion of mythbackend.log-1 that shows the machine having trouble recording ER, the file is much bigger but contains more of the same kind of info, I think this is one of the files that mbemon is talking about but I have no idea what it's telling me any suggestions?

2006-11-09 22:01:02.513 Started recording "ER" on channel: 1013 on cardid: 1, sourceid 1
2006-11-09 22:01:02.961 Changing from None to RecordingOnly
2006-11-09 22:01:03.141 Can't enable VBI recording
vbi: Invalid argument
[mpeg2video @ 0xb771d010]00 motion_type at 12 0
[mpeg2video @ 0xb771d010]invalid mb type in B Frame at 5 1
[mpeg2video @ 0xb771d010]00 motion_type at 9 3
[mpeg2video @ 0xb771d010]00 motion_type at 5 7
[mpeg2video @ 0xb771d010]invalid mb type in B Frame at 12 8
[mpeg2video @ 0xb771d010]00 motion_type at 10 9
[mpeg2video @ 0xb771d010]00 motion_type at 11 10
[mpeg2video @ 0xb771d010]ac-tex damaged at 0 11
[mpeg2video @ 0xb771d010]invalid mb type in B Frame at 5 17
[mpeg2video @ 0xb771d010]00 motion_type at 2 18
[mpeg2video @ 0xb771d010]ac-tex damaged at 20 21
[mpeg2video @ 0xb771d010]Warning MVs not available
[mpeg2video @ 0xb771d010]00 motion_type at 20 10
[mpeg2video @ 0xb771d010]invalid cbp at 0 16
[mpeg2video @ 0xb771d010]mb incr damaged
[mpeg2video @ 0xb771d010]ac-tex damaged at 0 24

You're a bit short of details.

What type of capture card are you using?
Have you upgraded your drivers?

The card is a pvr 500 and I'm using the drivers that came with the install.

There was a known and long standing DMA bug in the ivtv drivers which has been fixed in the newest releases. The messages in your log file seem to indicate a corrupted MPEG2 stream which would fit with this. Try upgrading the ivtvt drivers to 0.4.7 following the directions on the CompileIvtv page on the wiki. I believe that R5A30 has a new enough kernel to allow this. You will need to replace every occurance of 0.4.6 in the instructions with 0.4.7 if I don't get chance to update them first.

If you haven't done a lot of custom upgrades to the system (adding packages via apt-get and the like) upgrading to R5C7 or later might also be in order. If you decide to do this, please see R5C7 or R5D1 upgrade hints before you start.