LinHES Forums
http://forum.linhes.org/

Myth crashing intermittently, how do i diagnose?
http://forum.linhes.org/viewtopic.php?f=11&t=17515
Page 1 of 2

Author:  rmflook [ Wed Jan 02, 2008 6:51 am ]
Post subject:  Myth crashing intermittently, how do i diagnose?

Hi,

I have not long installed the latest version of knoppmyth (R5F27) and have found that there are two problems which are continually occuring but not all the time.

1) When watching video the video will 'jam' at a random point (it is seemingly never the same point in a movie) and freeze on a frame with the last half second of sound repeating over and over.

2) When left doing nothing for a while the system will simply freeze up.

For both of these problems the system will not respond to keyboard commands and i am unable to SSH in from another machine. Therefore i have to force power down the system.

I know that there are a bunch of logs as mentioned on the wiki but i have had a gander and cant see anything obvious. However it would help if i knew what i was looking for in the first place.

Id be very grateful for any help

Author:  marc.aronson [ Wed Jan 02, 2008 9:18 am ]
Post subject: 

A few questions:

1. What is your full hardware configuration? (CPU, mobo, video card, memory, tuners, etc.)

2. Was this hardware configuration ever stable with this distribution?

3. For scenario # 1 -- what type of video are you watching and what player are you using?

4. For scenario # 2 -- please post the last 30 lines of /var/log/kern.log and /var/log/messages the next time it happens (or from the last time it happened, if you have it available).

Marc

Author:  Greg Frost [ Wed Jan 02, 2008 4:19 pm ]
Post subject: 

One thing you could try is to run memtest overnight to see if you are getting any memory errors. I think you can do this by booting with the knoppmyth cd and typing memtest at the first prompt.

Author:  cecil [ Thu Jan 03, 2008 12:12 am ]
Post subject: 

Code:
cd /var/log/mythtv
Take a look at your logs. Read the wiki...

Author:  snaproll [ Thu Jan 03, 2008 10:05 am ]
Post subject: 

I had this with a Mythbox using an old (2001) machine that began experiencing 'Taiwan capacitor failures', causing repeated crash & reboot.

Solution was to replace all the mb capacitors in the machine.

Author:  rmflook [ Wed Jan 09, 2008 8:11 am ]
Post subject: 

Cheers for the info so far guys. I dont think it is a hardware problem as the system is as stable as can be if i jump out of myth into the knoppix style desktop. My hardware is as follows

320Gb PATA harddrive
DVD Rom
512 DDR2 RAM
AMD Sempron 3400+
Onboard sound
Asus EN6200LE 64MB (Nvidia based card)

I ran memtest all for a whole day and it didnt throw any errors.

As for the video i was watching it was an avi and the player i was using was mplayer. I dont have the log handy as im not connected to the net at home, bit ill copy it to a usb next time it happens and bring in the log.

Author:  marc.aronson [ Wed Jan 09, 2008 9:19 am ]
Post subject: 

What motherboard are you using?

Author:  rmflook [ Thu Jan 10, 2008 7:27 am ]
Post subject: 

Not entirely sure which mobo im using. Found the specs for the machine i have and is this the info about the mobo?

Chipset North Bridge: VIA K8M890
South Bridge: VIA VT8237A

If not the info about the machine can be found here

http://www.ebuyer.com/product/119978

Might there be something wrong with it?

Just seems a bit odd that it runs without fault when im not in mythtv but when i am in mythtv thats when problems start occurring.

Author:  marc.aronson [ Thu Jan 10, 2008 10:18 am ]
Post subject: 

Read this post for information about known issues with the via chip set -- perhaps this applies to your situation: http://mysettopbox.tv/phpBB2/viewtopic.php?t=6321

Author:  rmflook [ Fri Jan 11, 2008 11:33 am ]
Post subject: 

Cheers for the info, but i think it is unlikely in my case as when i was using the previous version of knoppmyth i never had any problems. Dont really want to go back a version though as i could never get rmvb files to work and now it the latest release i can.

Author:  acipolone [ Sun Jan 13, 2008 10:58 pm ]
Post subject: 

I have half of the problem you do, occasionally. Sometimes it just locks up.

I dug through the logs and never found anything. Memory seems okay. I never posted because ... well, I couldn't provide any info other than "it froze up". Hehe.

I'm not using any hardware remotely close to what you have. Does it happen regularly to you, or is it sort of random?

Author:  rmflook [ Fri Jan 18, 2008 12:31 pm ]
Post subject: 

Now that i finally am back on the net at home i can provide a bit more info.

This is the last 30 lines of output from my kern.log the last time my mythbox decided to crash itself

Jan 18 18:07:37 mythtv kernel: fuse init (API version 7.7)
Jan 18 18:07:37 mythtv kernel: Linux agpgart interface v0.101 (c) Dave Jones
Jan 18 18:07:37 mythtv kernel: NET: Registered protocol family 17
Jan 18 18:07:37 mythtv kernel: NET: Registered protocol family 10
Jan 18 18:07:37 mythtv kernel: lo: Disabled Privacy Extensions
Jan 18 18:07:37 mythtv kernel: IPv6 over IPv4 tunneling driver
Jan 18 18:07:37 mythtv kernel: kjournald starting. Commit interval 5 seconds
Jan 18 18:07:37 mythtv kernel: EXT3 FS on hda3, internal journal
Jan 18 18:07:37 mythtv kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 18 18:07:37 mythtv kernel: r8169: eth0: link up
Jan 18 18:07:37 mythtv kernel: Vendor: ST325082 Model: 4A Rev: 0000
Jan 18 18:07:37 mythtv kernel: Type: Direct-Access ANSI SCSI revision: 00
Jan 18 18:07:37 mythtv kernel: SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
Jan 18 18:07:37 mythtv kernel: sdb: Write Protect is off
Jan 18 18:07:37 mythtv kernel: sdb: Mode Sense: 27 00 00 00
Jan 18 18:07:37 mythtv kernel: sdb: assuming drive cache: write through
Jan 18 18:07:37 mythtv kernel: SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
Jan 18 18:07:37 mythtv kernel: sdb: Write Protect is off
Jan 18 18:07:37 mythtv kernel: sdb: Mode Sense: 27 00 00 00
Jan 18 18:07:37 mythtv kernel: sdb: assuming drive cache: write through
Jan 18 18:07:37 mythtv kernel: sdb: sdb1
Jan 18 18:07:37 mythtv kernel: sd 2:0:0:0: Attached scsi disk sdb
Jan 18 18:07:37 mythtv kernel: usb-storage: device scan complete
Jan 18 18:07:43 mythtv kernel: eth0: no IPv6 routers present
Jan 18 18:08:01 mythtv kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan 18 18:08:02 mythtv kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 24 (level, low) -> IRQ 24
Jan 18 18:08:02 mythtv kernel: PCI: Setting latency timer of device 0000:02:00.0 to 64
Jan 18 18:08:02 mythtv kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 1.0-9755 Mon Feb 26 23:21:15 PST 2007
Jan 18 18:13:52 mythtv kernel: Kernel logging (proc) stopped.
Jan 18 18:13:52 mythtv kernel: Kernel log daemon terminating.

And the last 30 lines from messages file

Jan 18 18:07:37 mythtv kernel: r8169: eth0: link up
Jan 18 18:07:37 mythtv kernel: Vendor: ST325082 Model: 4A Rev: 0000
Jan 18 18:07:37 mythtv kernel: Type: Direct-Access ANSI SCSI revision: 00
Jan 18 18:07:37 mythtv kernel: SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
Jan 18 18:07:37 mythtv kernel: sdb: Write Protect is off
Jan 18 18:07:37 mythtv kernel: SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
Jan 18 18:07:37 mythtv kernel: sdb: Write Protect is off
Jan 18 18:07:37 mythtv kernel: sdb: sdb1
Jan 18 18:07:37 mythtv kernel: sd 2:0:0:0: Attached scsi disk sdb
Jan 18 18:07:39 mythtv mt-daapd[2946]: *** WARNING *** The programme 'mt-daapd' uses the HOWL compatiblity layer of Avahi.
Jan 18 18:07:39 mythtv mt-daapd[2946]: *** WARNING *** Please fix your application to use the native API of Avahi!
Jan 18 18:07:39 mythtv mt-daapd[2946]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=howl&e=mt-daapd>
Jan 18 18:08:01 mythtv kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan 18 18:08:02 mythtv kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 24 (level, low) -> IRQ 24
Jan 18 18:08:02 mythtv kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 1.0-9755 Mon Feb 26 23:21:15 PST 2007
Jan 18 18:08:10 mythtv gconfd (mythtv-3593): starting (version 2.16.1), pid 3593 user 'mythtv'
Jan 18 18:08:10 mythtv gconfd (mythtv-3593): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jan 18 18:08:10 mythtv gconfd (mythtv-3593): Resolved address "xml:readwrite:/home/mythtv/.gconf" to a writable configuration source at position 1
Jan 18 18:08:10 mythtv gconfd (mythtv-3593): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jan 18 18:08:10 mythtv gconfd (mythtv-3593): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jan 18 18:08:10 mythtv gconfd (mythtv-3593): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jan 18 18:08:40 mythtv gconfd (mythtv-3593): GConf server is not in use, shutting down.
Jan 18 18:08:40 mythtv gconfd (mythtv-3593): Exiting
Jan 18 18:12:44 mythtv mt-daapd[3953]: *** WARNING *** The programme 'mt-daapd' uses the HOWL compatiblity layer of Avahi.
Jan 18 18:12:44 mythtv mt-daapd[3953]: *** WARNING *** Please fix your application to use the native API of Avahi!
Jan 18 18:12:44 mythtv mt-daapd[3953]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=howl&e=mt-daapd>
Jan 18 18:13:43 mythtv shutdown[4021]: shutting down for system reboot
Jan 18 18:13:52 mythtv kernel: Kernel logging (proc) stopped.
Jan 18 18:13:52 mythtv kernel: Kernel log daemon terminating.
Jan 18 18:13:53 mythtv exiting on signal 15

I really hope someone can help me with this, im guessing from the logs its something to do with the kernal

Author:  slowtolearn [ Fri Jan 18, 2008 1:38 pm ]
Post subject: 

rmflook wrote:
Now that i finally am back on the net at home i can provide a bit more info.
...
And the last 30 lines from messages file
...
Jan 18 18:13:43 mythtv shutdown[4021]: shutting down for system reboot
Jan 18 18:13:52 mythtv kernel: Kernel logging (proc) stopped.
Jan 18 18:13:52 mythtv kernel: Kernel log daemon terminating.
Jan 18 18:13:53 mythtv exiting on signal 15
Looks like a normal system shutdown is starting. How is this system configured? (combined BE/FE, diskless FE, etc.) Do you have it set to startup/shutdown automatically for any reason? (eg. http://knoppmyth.net/phpBB2/viewtopic.php?t=17366)

Author:  rmflook [ Fri Jan 18, 2008 6:12 pm ]
Post subject: 

My set up is a combined backend frontend. I dont have it set to shutdown for any reason and the key thing about it shutting down is that it does it after a random amount of time each time it 'crashes'. So while it might crash almost immediately one time it might crash after 10 hours the next time

Author:  shrabok [ Wed Feb 06, 2008 11:57 am ]
Post subject: 

I was dealing with the same issue and dug up somewhere to change XvMC to libmpeg2 for video and the problem has definately reduced if not stopped. I would get hard freezes that required computer reset.

Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/