| LinHES Forums http://forum.linhes.org/ |
|
| Mysterious Lockups http://forum.linhes.org/viewtopic.php?f=17&t=15181 |
Page 1 of 3 |
| Author: | whitlmr [ Thu May 10, 2007 2:57 pm ] |
| Post subject: | Mysterious Lockups |
I'm having an odd problem with the new myth system I built. Occassionally I will come home and the system is completely locked up (still in frontend). I can't restart x, SSH in, or anything so I have to hit the reset button to get it back up. Perhaps unrelated or not, the backend isn't always starting on boot.. I have to ALT-X and sudo mythbackend & to get it going. After that everything works fine. I'm still green when it comes to linux, I know there should be some way to tell from log files or something similar what is causing the lockups, but I don't even know where to begin.. Can someone point me in the right direction? I'm running R5E50, ASUS M2N32-SLI motherboard with a AMD Athlon 64 X2 3600+ Windsor 2GHz processor, Geforce 7950GT video card. Thanks in advance for your help. Michael |
|
| Author: | jigawho [ Thu May 10, 2007 4:23 pm ] |
| Post subject: | |
Unfortunately I can't help you on the freezing side, except to suggest you run memtest for a day and see if you get any errors. Generally hard freezes like that are caused by hardware either failing or overheating The backend not starting problem is a known issue having to do with the script that starts it. If you search the forum someone posted a fix that seems to have cleared it up for me. In the meantime, if you press alt-3 it should restart the backend (alt-2 stops it). |
|
| Author: | mjl [ Thu May 10, 2007 6:59 pm ] |
| Post subject: | |
Hi, I have had that happen also when using a large serial drive. IDE has been working ok for me. Mike |
|
| Author: | whitlmr [ Thu May 10, 2007 7:09 pm ] |
| Post subject: | |
I do have a 750GB SATA drive. |
|
| Author: | mjl [ Thu May 10, 2007 7:15 pm ] |
| Post subject: | |
HI, I have not had the chance to try running KM off an ide and use the serial just as the /myth storage. Just a thought. (Do a backup first!) Mike |
|
| Author: | talanar [ Fri May 18, 2007 6:55 pm ] |
| Post subject: | |
I'm having the same problem, using a 320GB IDE hard drive, on a P4 2.26Ghz machine, 512MB ram, with 2x Hauppauge PVR500's as a back end machine, and it has been locking up constantly. Running windows XP no problems, running FreeBSD 6.2 no problems, running regular Knoppix off of a CD no problems. Only has been happening with Knoppmyth. Also I some times get an odd problem with the PVR500's where the recording gets a little jumbled, say i watch the same show on my TV and also even live on the box, the tv always is nice and stable, and on the box it will sometimes jitter the video. Almost like it's not getting it's interrupts serviced enough. And that is only with one pvr500 doing anything, recording on only one encoder, the other idel and the other card also idle. Anyone have any ideas? |
|
| Author: | Girkers [ Sat May 19, 2007 5:15 am ] |
| Post subject: | |
With Lockups there are so many reasons for this to be happening it is had to discern what the exact root cause of the problem is. Here are some tips to try and find where the problem may lay. 1. Physically inspect the Mainboard - What you are looking for is busted or popped capacitors, this has plagued many Mainboards for sometime and the reason a lot of manufacturers are moving towards using solid capacitors. Capacitors are the tall things generally around the CPU socket and have a cross on the silver top. If the top is raised or you can see a light brown powder seeping out the top you know your in trouble. 2. Memtest - This test will test your memory (RAM) and it is important to let this test run for some time as the problem may be caused by components when under stress, I would suggest at the very minimum of 3 passes. 3. Heat - This is sometimes hard to determine, the simpliest way I can suggest to see if this is the issue, is as soon as the computer locks up, reboot the computer and go into your BIOS. In there you will have something like "PC Health" which will list the temperatures inside the system and fan speeds. You could find that the system is overheating or a fan my be under performing. 4. Power supplier - This is sometimes the least thought about component and is often neglected as a $40(AU) case can include a power supply thus why would you purchase another one. Think of it this way, if you pay $40(AU) for a case and PSU, why would you spend btn $80(AU) - $200(AU) on a decent one when I already have one. Power is essential to the stability of the system, without clean, reliable power the system is not worth a pinch of poop. To look at this issue, in your BIOS as in suggestion 3, check your "PC Health", there should be voltages listed, check they are very close to what they should be. Now this is only an indication as the system is not under load and that is where the problem could be. If possible unplug unnecessary components, eg other HDDs, stuff like that. 5. Failing HDD - You could test the Hard Disk Drive with the manufacturers software to ensure that it is not failing. You can download the software from the their website or you can use this disc Ultimate Boot CD which contains a number of utilities for testing system components including a number of drive manufacturer tools. In saying all that it could be the software, but unlikely due to the large install base and few user reporting similar problems. If you have a particular problem don't hesitate to post a reply or drop me an email or PM. |
|
| Author: | mjl [ Sat May 19, 2007 6:03 am ] |
| Post subject: | |
Hi, Those are good tips especially for home built / older hardware. The boxes I had the issues were Dells, One fresh out of the box and one only slightly older with new 500 gig drive. I backed down to R5C7 and they run like rocks. I'm suspecting some "energy saving" mode on the new large drives but with out some kind of trail it is tough to travel. Could even be some simular control in the kernel. More questions then answers. Mike |
|
| Author: | whitlmr [ Tue May 29, 2007 7:21 pm ] |
| Post subject: | |
I'm still having the random lockups, it just happened and I was logged into the computer over ssh.. I saw this was spit out in the SSH terminal. I'm still very new to linux so I'm not really sure what it all means.. Can someone help decipher? Quote: Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ...
mythbox kernel: Process events/0 (pid: 8, ti=c2178000 task=c216a5d0 task.ti=c2178000) Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: ds: 007b es: 007b ss: 0068 Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: Oops: 0002 [#1] Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: esi: f7a037e0 edi: c2104dc0 ebp: c2105494 esp: c2179f08 Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: EIP is at free_block+0x93/0x130 Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: CPU: 0 Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: PREEMPT SMP Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: eax: c4c06040 ebx: c20eabc0 ecx: f7a03000 edx: fdfdfdfd Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: Stack: 00000440 0000002c 0000001f c2105418 c2105400 0000002c 00000000 c01777ab Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: 00000000 00000000 c2104dc0 c20eabe4 c20eabc0 c2104dc0 c213df40 00000000 Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: c0178ff3 00000000 00000000 c2010280 c2010284 c0133dde 00000000 c213df68 Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: Call Trace: Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: Code: 05 01 c2 8b 02 f6 c4 40 0f 85 a2 00 00 00 8b 02 84 c0 0f 89 a0 00 00 00 8b 4a 1c 8b 44 24 20 8b 11 8b 9c 87 90 00 00 00 8b 41 04 <89> 42 04 c7 41 04 00 02 20 00 89 10 c7 01 00 01 10 00 8b 41 0c Message from syslogd@mythbox at Tue May 29 20:20:03 2007 ... mythbox kernel: EIP: [<c01776b3>] free_block+0x93/0x130 SS:ESP 0068:c2179f08 Read from remote host 192.168.2.45: Connection reset by peer Connection to 192.168.2.45 closed. |
|
| Author: | Girkers [ Tue May 29, 2007 10:17 pm ] |
| Post subject: | |
I just did a search on Google in regards to this error and from what I read it may have to do with multicore processing and the kernel. You could try turn off Hyperthreading (Intel) or run the processor as a single core (if using dual core) to see if this eleminates you problem I also would like to ask, did you do any of the tests I suggested? |
|
| Author: | whitlmr [ Sat Jun 09, 2007 8:02 am ] |
| Post subject: | |
I have an AMD processor so turning off hyperthreading is not an option. I dug around a little in the BIOS and didn't see an option to switch to single core, where is this normally? I did run memstest for 2 passes with no errors. According to RRDTool the system and CPU temperature has been very constant (the reboots show up as breaks in the graph and there's no spike before the break). Here's my complete system: ASUS M2N32-SLI Deluxe Wireless Edition AMD Athlon 64 X2 3600+ Windsor 2.0GHz Socket AM2 Processor Model ADO3600CUBOX - Retail7200 RPM SATA 3.0Gb/s Hard Drive - OEM XFX PVT71JYHE9 GeForce 7950GT 512MB 256-bit GDDR3 PCI Express x16 HDCP ExTreme Edition Video Card SILVERSTONE LASCALA 10 CS-SST-LC10B Black Aluminum front panel, 1.0mm SECC body ATX Media Center Computer Case Thermaltake TR2 W0070RUC ATX 430W Power Supply - Retail Seagate Barracuda 7200.10 ST3750640AS 750GB Kingston HyperX 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model KHX6400D2K2/2G - Retail |
|
| Author: | marc.aronson [ Sun Jun 10, 2007 8:21 am ] |
| Post subject: | |
What tuner card(s) are you using? Marc |
|
| Author: | whitlmr [ Sun Jun 10, 2007 10:01 am ] |
| Post subject: | |
Oops..forgot to include those.. I pulled them from my last mythtv system (which had no lockups) Hauppauge PVR-150 and Hauppauge PVR-250 (that's what the box said, but it's a bttv chipset) |
|
| Author: | marc.aronson [ Sun Jun 10, 2007 11:39 am ] |
| Post subject: | |
I had some stability issues quite a while back that I resolved by changing some of the settings in /etc/lilo.conf. I modified the line that reads "append=" to look like this: Code: append="splash=silent apm=power-off nomce noapic"
I believe it was the "noapic" that was key for me. I don't know if this will help you, but if you decide to try it, you first edit the file, then execute "lilo -v", then reboot, all as root. Marc |
|
| Author: | whitlmr [ Sun Jun 10, 2007 12:16 pm ] |
| Post subject: | |
Thanks for the tip Marc, I just made the change. I did notice on reboot that it seems to be a lot faster. The typical boot text was screaming by and the frontend seemed to load faster. Not sure what this means, but I'm not complaining! |
|
| Page 1 of 3 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|