[mythtv-users] change in hostname/dhcp/router = instability?

[Sean Goodpasture]

running mythdora FWIW.

I've got a linksys router and got the wild hair to install DD-WRT on
it today.  One of the things you can do is static DHCP.  This allows
you to make sure that a given box always gets the same IP.  I guess
that it also does something with DNS?  I didn't change the hostname,
just the way that the IP is assigned.  The hostname actually stayed
the same, but now I can reach the backend by name rather than only by
IP.

In any case, since doing this, I get all sorts of instability with my
main backend.  When watching live TV (on a remote frontend) I get
random crashes when changing the channel.  Sometimes the crash happens
when I'm playing around in recordings or recording settings.

I did watch most of the football 2nd half this evening, but right
after it borked when I went to check the score of the college game on
ESPN.

The bad thing is that there is nothing in the log at all.  Just a
changing to Live TV on my tuner and then the restart stuff from when I
restart the backend.

One time there was a dump in the log:
2007-12-29 19:52:38.241 TVRec(7): HW Tuner: 7->7
*** glibc detected *** /usr/bin/mythbackend: malloc(): memory
corruption (fast): 0x09f92c2f ***
======= Backtrace: =========
/lib/libc.so.6[0x252621]
/lib/libc.so.6(__libc_malloc+0x7e)[0x2532de]
/usr/lib/libstdc++.so.6(_Znwj+0x27)[0x5703a7]
/usr/lib/libstdc++.so.6(_Znaj+0x1d)[0x5704dd]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZN7QString9setLengthEj+0x3f)[0x5298e5f]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZN7QString4growEj+0x30)[0x5298ff0]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZN7QString6insertEjPK5QCharj+0x4f)[0x52990ff]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZN7QString6insertEjRKS_+0x3c)[0x529926c]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZN7QString6insertEj5QChar+0x45)[0x529fc75]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZNK14QLocalePrivate16longLongToStringExiiij+0xf5)[0x5287df5]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZN7QString6setNumExi+0x8c)[0x529e75c]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZN7QString6numberExi+0x4b)[0x529e80b]
/usr/lib/qt-3.3/lib/libqt-mt.so.3(_ZNK7QString3argExii+0x17d)[0x529e9cd]
/usr/lib/libmythtv-0.20.2.so.0(_ZNK18SignalMonitorValue9GetStatusEv+0xe5)[0x63fcca5]
======= Memory map: ========

I built this backend about a month ago, and did a thorough burnin and
test with memtest, so I'm reasonably confident that it's not the
memory...


Here's a "silent" crash example:
2007-12-29 22:23:31.219 MainServer::HandleAnnounce Playback
2007-12-29 22:23:31.230 adding: mythfrontendLR as a client (events: 0)
2007-12-29 22:23:31.242 MainServer::HandleAnnounce FileTransfer
2007-12-29 22:23:31.248 adding: mythfrontendLR as a remote file transfer
2007-12-29 22:23:43.878 Finished recording College Basketball "Arizona
at Memphis": channel 5033
-- crashed here
2007-12-29 22:26:08.999 Using runtime prefix = /usr
2007-12-29 22:26:09.103 New DB connection, total: 1
2007-12-29 22:26:09.127 Connected to database 'mythconverg' at host: localhost
2007-12-29 22:26:09.139 Current Schema Version: 1160
Starting up as the master server.



It's not reproducible 100% of the time, but if my backend is dieing,
I'm in hot water :-)

Thanks in advance,

Sean