[mythtv-users] Myth segfaults: how to troubleshoot further?

leifontheroad leifontheroad at hotmail.com
Tue May 5 17:16:01 UTC 2009


I recently upgraded my machine to make it more HD-ready. I moved to a new mobo, faster proc, more RAM, more hdd. I'm running mythbuntu 8.10. I also moved all my old recordings over to my new machine, and also imported the DB from my old machine to the new (using http://www.mythtv.org/docs/mythtv-HOWTO-23.html#ss23.7, which has worked great for me many times before as I've upgraded over the years). Here's my setup:

Asus MN378-VM mobo with onboard GeForce 8200 / HDMI
Athlon 64 X2 5600
4GB G.Skill RAM
Mythbuntu 8.10
Rosewill PCIE Firewire card (VIA 3403 chipset)


With this new setup, I'm seeing segfaults related to mythbackend or mythfilldatabase on a regular basis (1+ times / day). Here are a few from the last few days:

$ more messages | grep segfault
May  3 16:30:14 mythtv2 kernel: [61152.409051] mythfilldatabas[12076]: segfault at b6785494 ip 085ba735 sp b492b7f0 error 7
May  4 08:38:02 mythtv2 kernel: [34181.816293] mythbackend[9122]: segfault at 10 ip 0806c642 sp bf90c050 error 4 in mythbackend[8048000+118000]
May  4 21:55:03 mythtv2 kernel: [82003.781958] nm-system-setti[5836]: segfault at 10 ip b80b7c59 sp bf8d7eb0 error 4 in libnm-settings-plugin-ifupdown.so[b80b2000+8000]
May  4 23:00:03 mythtv2 kernel: [ 2442.673099] mythbackend[6545]: segfault at 732 ip b67d8d2b sp b1816568 error 6 in libqt-mt.so.3.3.8[b6244000+6f2000]
May  4 23:32:45 mythtv2 kernel: [ 4404.410880] mythbackend[7640]: segfault at 0 ip b77173e6 sp a8a1ef70 error 4 in libmythtv-0.21.so.0.21.0[b7536000+a1e000]

I've searched through the mailing lists and googled, but I'm not seeing anything helpful with respect to these messages. A few posts have mentioned ensuring that the IP addresses for the FE/BE and DB are all synched up, but this is a combined FE/BE, so it's not complicated (and I've confirmed that everything is setup correctly). I've also run memtest86 on my RAM (no errors), and tried new RAM (still get segfaults), so I don't think it's a case of bad RAM. And the only significant errors I'm seeing are related to myth - no other segfaults in messages or syslog. 

It's possible that the DB isn't happy, and didn't like the import from my old system, so my next thought is to re-install everything and see how it all runs before importing data from my old DB. I haven't yet run the "optimize DB" script, so I'll try that as well. 

Any other suggestions? I've been running mythtv since about 2001, and this is the most stumped I've been.

Thanks,

-Leif
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090505/0fa28675/attachment.htm>


More information about the mythtv-users mailing list