[mythtv-users] Frontend crash after 2-3 hours of live tv - Anysuggestions?
William
wmunson at rochester.rr.com
Thu Mar 23 22:44:17 UTC 2006
> * On Wed Mar 22, 2006 at 09:13:36AM -0500, William wrote:
> > I think I may have found the problem. It appears that myth tried to
> > make a 0.004 second long recording and then bombed when
> mythcommflag
> > tried to run on it.
>
> Keep looking, your off-base in a couple places.
>
> > Here is the output of my debug session.
>
> Nothing useful here unfortunately. If it crashed, you should
> include a backtrace.
>
> > 2006-03-21 22:00:08.708 External Tuning program exited with
> no error
> > 2006-03-21 22:00:08.729 scheduler: Finished recording: Fox First at
> > Ten: channel 1031 2006-03-21 22:00:09.017 TVRec(1):
> > RingBufferChanged()
> > 0: start_time: 737.558 duration: 8589.932
> > 1: start_time: 737.558 duration: 0.004
> > stream: start_time: 8195.086 duration: 95443.685 bitrate=0 kb/s
> > 2006-03-21 22:00:12.165 NVP: Recording does not have position map.
> > Run 'mythcommflag --file
> 1031_20060321220002.mpg --rebuild' to fix
> >
> > -------------------------------
> >
> > As you can see, my #1 encoder tried to make a 0.004 long recording
> > which is too short to have a position map.
>
> The #1 "encoder" you are talking about is stream #1 in the
> recording file. I can't answer why it is only 0.004 long,
> but it has nothing to do with Myth's tuner/card numbering.
>
> It didn't "bomb" when mythcommflag tried to run, at least not
> according to your logs. The log says "Recording does not
> have position map. Run 'mythcommflag --file
> 1031_20060321220002.mpg --rebuild' to fix". That is telling
> you to run mythcommflag if you want, myth didn't try to run it itself.
>
> I'd venture to say that the reason you're seeing the streams
> listed is because that means the pixmap generator fired off.
>
> If this did crash on you, then a backtrace may be the only
> thing that solves it, because there's nothing useful that I
> see in the log you posted.
>
> --
> Chris
Hi Chris,
Attached is a backtrace of the system while in the crashed state. Top output
follows.
(gdb)
(gdb) bt
#0 0x00ba67a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00c897f6 in __nanosleep_nocancel () from /lib/tls/libc.so.6
#2 0x00cb7d6a in usleep () from /lib/tls/libc.so.6
#3 0x08065347 in startTV ()
#4 0x080657b5 in TVMenuCallback ()
#5 0x0061a58c in ThemedMenuPrivate::handleAction ()
from /usr/lib/libmyth-0.19.so.0
#6 0x0061898e in ThemedMenuPrivate::keyPressHandler ()
from /usr/lib/libmyth-0.19.so.0
#7 0x0061c60b in ThemedMenu::keyPressEvent () from
/usr/lib/libmyth-0.19.so.0
#8 0x04ef44ac in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#9 0x04e5e00d in QApplication::internalNotify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#10 0x04e5dafc in QApplication::notify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x0069837d in MythMainWindow::customEvent ()
from /usr/lib/libmyth-0.19.so.0
#12 0x04eb9e92 in QObject::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#13 0x04ef43f2 in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0x04e5e00d in QApplication::internalNotify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x04e5d62f in QApplication::notify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x04e5ef6e in QApplication::sendPostedEvents ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x04e5edfc in QApplication::sendPostedEvents ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x04e070b9 in QEventLoop::processEvents ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x04e708ef in QEventLoop::enterLoop ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x04e5e290 in QApplication::enter_loop ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x0069973d in MythDialog::exec () from /usr/lib/libmyth-0.19.so.0
#22 0x0806eec2 in main ()
(gdb)
Output from top for whatever its worth.
top - 17:33:41 up 2 days, 19:18, 5 users, load average: 1.74, 1.59, 1.29
Tasks: 128 total, 1 running, 127 sleeping, 0 stopped, 0 zombie
Cpu(s): 42.4% us, 57.2% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.3% hi, 0.0% si
Mem: 515704k total, 511604k used, 4100k free, 860k buffers
Swap: 1020116k total, 252236k used, 767880k free, 84716k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8089 mythtv 15 0 612m 314m 26m S 98.0 62.5 95:58.48 mythfrontend
8085 root 11 -5 2220 364 172 S 1.7 0.1 8:53.98 3
6296 root 16 0 216m 15m 9532 S 0.7 3.0 7:10.54 mythbackend
9342 root 17 0 3268 928 724 R 0.3 0.2 0:00.06 top
1 root 16 0 3132 248 232 S 0.0 0.0 0:01.54 init
2 root 34 19 0 0 0 S 0.0 0.0 0:00.19 ksoftirqd/0
3 root 5 -10 0 0 0 S 0.0 0.0 0:00.67 events/0
4 root 8 -10 0 0 0 S 0.0 0.0 0:00.01 khelper
16 root 15 -10 0 0 0 S 0.0 0.0 0:00.00 kacpid
135 root 5 -10 0 0 0 S 0.0 0.0 0:06.52 kblockd/0
143 root 15 0 0 0 0 S 0.0 0.0 0:00.00 khubd
198 root 15 0 0 0 0 S 0.0 0.0 0:09.61 pdflush
200 root 7 -10 0 0 0 S 0.0 0.0 0:00.00 aio/0
199 root 15 0 0 0 0 D 0.0 0.0 1:14.07 kswapd0
293 root 25 0 0 0 0 S 0.0 0.0 0:00.00 kseriod
496 root 6 -10 0 0 0 S 0.0 0.0 0:00.00 ata/0
511 root 15 0 0 0 0 S 0.0 0.0 0:04.18 kjournald
1953 root 15 0 0 0 0 S 0.0 0.0 0:00.00 kjournald
1966 root 5 -10 0 0 0 S 0.0 0.0 0:04.53 xfslogd/0
1967 root 6 -10 0 0 0 S 0.0 0.0 0:00.00 xfsdatad/0
Does this help any?
Bill
More information about the mythtv-users
mailing list