| LinHES Forums http://forums.linhes.org/ |
|
| Frontend hangs while watching live tv 7NIF2, PVR-350, R4V5 http://forums.linhes.org/viewtopic.php?f=2&t=2732 |
Page 1 of 2 |
| Author: | mrice [ Tue Oct 19, 2004 7:35 am ] |
| Post subject: | Frontend hangs while watching live tv 7NIF2, PVR-350, R4V5 |
I don't mean to be redundant by posting in two threads, but this is basically a continuation of http://mysettopbox.tv/phpBB2/viewtopic.php?t=2519 However, much of that thread is involved with my previous motherboard and the issues are not the same. So here is a fresh start with just the facts. I am using the Chaintech 7NIF2 (nforce2 chipset), Athlon XP 2400+, 512MB RAM, PVR-350, 120GB drive. The whole lot is installed in an Antec Aria case. The installation process I followed was, 1. installed Knoppmyth R4V5 onto freshly formatted drive. 2. setup NFS to export /myth/gallery and /myth/music to local network. 3. setup PVR-350 per wiki http://knoppmythwiki.homelinux.org/inde ... stallation. 4. setup time sync per wiki http://knoppmythwiki.homelinux.org/inde ... onizeHowTo 5. setup IR blaster per http://losdos.dyndns.org:8080/public/my ... _LIRC.html My cabling is pretty simple; cable into digital cable box, s-vid to PVR-350, video from PVR-350 to TV. This machine serves as both my backend and frontend. At first, everything appeared to work fine with this setup. I never got around to doing anything fancy, like transcoding or ripping DVD, but all basic stuff, live tv, recording, playback, sound, remote, music, images - all worked. Now after a few days while watching live TV and attempting to navigate through the program guide, the front end freezes up. That is, picture and sound both stop. I can exit out of live tv back to the menu, but if I then attempt to go back to live tv it completely hangs and has to be forceably killed remotely (I can still ssh into the box). In the logs is something like this: Code: Oct 9 17:08:37 io kernel: saa7115[0]: decoder set picture bright=127 contrast=63 saturation=63 hue=0 Oct 9 17:08:37 io last message repeated 3 times Oct 9 17:08:37 io kernel: saa7115[0]: decoder set size Oct 9 17:08:37 io kernel: Hpsc: 0x00001, Hfsc: 0x00600 Oct 9 17:08:37 io kernel: Setting full NTSC height Oct 9 17:08:37 io kernel: saa7115[0]: decoder disable output Oct 9 17:08:37 io kernel: saa7115[0]: decoder enable output Oct 9 17:08:53 io kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting... Oct 9 17:09:00 io last message repeated 44 times The next time this happened I found this in the syslog: Code: Oct 10 11:06:23 io kernel: ivtv: Got DMA-done, but not expecting one Oct 10 11:06:44 io kernel: ivtv: DMA read error. Result=0x00000002 Oct 10 11:14:12 io kernel: ivtv: DMAP not set Oct 10 11:14:28 io last message repeated 12 times Oct 10 11:15:07 io kernel: saa7115[0]: decoder set size Oct 10 11:15:07 io kernel: Hpsc: 0x00001, Hfsc: 0x00600 Oct 10 11:15:07 io kernel: Setting full NTSC height Oct 10 11:15:30 io kernel: ivtv: DMA read error. Result=0x00000002 Oct 10 11:15:33 io kernel: ivtv: DMA read error. Result=0x00000002 Oct 10 11:16:13 io kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting... Oct 10 11:16:20 io last message repeated 49 times Oct 10 11:16:22 io kernel: ivtv: 100 ms time out waiting for firmware Oct 10 11:16:22 io kernel: ivtv: api call 0x00000001 Oct 10 11:16:22 io kernel: ivtv: COULDN'T START PLAYBACK -16 Oct 10 11:16:23 io kernel: ivtv: 100 ms time out waiting for firmware Oct 10 11:16:23 io kernel: ivtv: api call 0x0000000d Oct 10 11:16:23 io kernel: ivtv: DEC: error pausing Oct 10 11:16:24 io kernel: ivtv: 100 ms time out waiting for firmware Oct 10 11:16:24 io kernel: ivtv: api call 0x00000003 Oct 10 11:16:24 io kernel: ivtv: DEC: error changing speed Oct 10 11:16:24 io kernel: ivtv: DEC: error in slow/fast mode Note the DMA read error message. At about this point, I rebooted into the bios and checked around for this "c1-disconnect" option I have read about. Couldn't find it, but did find "apic enabled" and changed it to "disabled" since that has been mentioned as a possible cause for problems with myth. Over the next week, it seemed that that message became increasinly frequent. Now it seems to freeze up pretty much every time I attempt to watch live tv, especially when the osd is involved (such as program guide, or changing channels). In the log today I see some even more disturbing messages: Code: Oct 19 08:24:42 io kernel: ivtv: DMAP not set Oct 19 08:24:42 io kernel: ivtv: i_flags=8, 3 s_sflags=4 Oct 19 08:24:44 io kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting... Oct 19 08:24:45 io last message repeated 2 times Oct 19 08:24:45 io kernel: ivtv-fb: error sending DMA info Oct 19 08:24:45 io kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting... Oct 19 08:24:49 io last message repeated 11 times Oct 19 08:24:49 io kernel: ivtv-fb: error sending DMA info Oct 19 08:24:49 io last message repeated 5 times Oct 19 08:24:50 io kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting... Oct 19 08:24:50 io last message repeated 2 times Oct 19 08:24:50 io kernel: ivtv-fb: error sending DMA info Oct 19 08:24:50 io last message repeated 9 times Oct 19 08:24:51 io kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting... Oct 19 08:24:53 io last message repeated 9 times Oct 19 08:24:54 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:24:54 io kernel: ivtv: api call 0x00000002 Oct 19 08:24:54 io kernel: ivtv: stopDEC error 2. Code -16 Oct 19 08:24:55 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:24:55 io kernel: ivtv: api call 0x00000044 Oct 19 08:24:56 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:24:56 io kernel: ivtv: api call 0x0000004f Oct 19 08:24:57 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:24:57 io kernel: ivtv: api call 0x0000004a Oct 19 08:24:58 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:24:58 io kernel: ivtv: api call 0x00000045 Oct 19 08:24:59 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:24:59 io kernel: ivtv: api call 0x0000004b Oct 19 08:25:00 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:25:00 io kernel: ivtv: api call 0x00000050 Oct 19 08:25:01 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:25:01 io kernel: ivtv: api call 0x00000046 Oct 19 08:25:03 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:25:03 io kernel: ivtv: api call 0x00000047 And finally Code: Oct 19 08:47:41 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 08:47:41 io kernel: ivtv: api call 0x00000081 Oct 19 08:47:41 io kernel: ivtv: startcap error 1. Code -16 Oct 19 08:47:42 io kernel: spurious 8259A interrupt: IRQ7. Oct 19 08:47:44 io kernel: ivtv: Timeout waiting for data! Oct 19 08:48:17 io last message repeated 11 times Oct 19 08:49:18 io last message repeated 20 times Oct 19 08:50:00 io last message repeated 14 times Oct 19 08:50:01 io /USR/SBIN/CRON[949]: (root) CMD ([ -d /etc/shaper ] && /etc/init.d/shaper timecheck) Oct 19 08:50:03 io kernel: ivtv: Timeout waiting for data! Oct 19 08:50:36 io last message repeated 11 times Oct 19 08:51:39 io last message repeated 21 times Oct 19 08:52:42 io last message repeated 21 times Oct 19 08:53:43 io last message repeated 20 times Oct 19 08:54:46 io last message repeated 21 times Oct 19 08:55:49 io last message repeated 21 times Oct 19 08:56:52 io last message repeated 21 times Oct 19 08:57:53 io last message repeated 20 times Oct 19 08:58:56 io last message repeated 21 times Oct 19 08:59:56 io last message repeated 20 times Oct 19 08:59:59 io kernel: ivtv: Timeout waiting for data! Oct 19 09:00:01 io /USR/SBIN/CRON[957]: (root) CMD ([ -d /etc/shaper ] && /etc/init.d/shaper timecheck) Oct 19 09:00:02 io kernel: ivtv: Timeout waiting for data! Oct 19 09:00:36 io last message repeated 11 times Oct 19 09:01:00 io last message repeated 8 times Oct 19 09:01:10 io kernel: ivtv: 1000 ms time out waiting for firmware Oct 19 09:01:10 io kernel: ivtv: api call 0x00000082 Oct 19 09:01:10 io kernel: ivtv: stopcap error 2. Code -16 Oct 19 09:05:01 io /USR/SBIN/CRON[965]: (root) CMD (nice -n 19 /usr/local/bin/mythlink.sh) Oct 19 09:05:38 io kernel: saa7115[0]: decoder set picture bright=127 contrast=63 saturation=63 hue=0 Oct 19 09:05:38 io last message repeated 3 times Oct 19 09:05:38 io kernel: saa7115[0]: decoder set size Oct 19 09:05:38 io kernel: Hpsc: 0x00001, Hfsc: 0x00600 Oct 19 09:05:38 io kernel: Setting full NTSC height Oct 19 09:05:39 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:39 io kernel: ivtv: api call 0x000000c9 Oct 19 09:05:39 io kernel: ivtv: init error 1. Code -16 Oct 19 09:05:40 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:40 io kernel: ivtv: api call 0x000000c7 Oct 19 09:05:40 io kernel: ivtv: init error 2. Code -16 Oct 19 09:05:41 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:41 io kernel: ivtv: api call 0x000000b9 Oct 19 09:05:41 io kernel: ivtv: init error 3. Code -16 Oct 19 09:05:42 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:42 io kernel: ivtv: api call 0x000000bb Oct 19 09:05:42 io kernel: ivtv: init error 4. Code -16 Oct 19 09:05:43 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:43 io kernel: ivtv: api call 0x0000008f Oct 19 09:05:43 io kernel: ivtv: init error 5. Code -16 Oct 19 09:05:44 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:44 io kernel: ivtv: api call 0x00000091 Oct 19 09:05:44 io kernel: ivtv: init error 6. Code -16 Oct 19 09:05:45 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:45 io kernel: ivtv: api call 0x00000099 Oct 19 09:05:45 io kernel: ivtv: init error 7. Code -16 Oct 19 09:05:46 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:46 io kernel: ivtv: api call 0x00000095 Oct 19 09:05:46 io kernel: ivtv: init error 8. Code -16 Oct 19 09:05:47 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:47 io kernel: ivtv: api call 0x00000097 Oct 19 09:05:47 io kernel: ivtv: init error 9. Code -16 Oct 19 09:05:48 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:48 io kernel: ivtv: api call 0x000000b1 Oct 19 09:05:48 io kernel: ivtv: init error 10. Code -16 Oct 19 09:05:49 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:49 io kernel: ivtv: api call 0x000000c5 Oct 19 09:05:49 io kernel: ivtv: init error 11. Code -16 Oct 19 09:05:50 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:50 io kernel: ivtv: api call 0x000000bd Oct 19 09:05:50 io kernel: ivtv: init error 12. Code -16 Oct 19 09:05:51 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:51 io kernel: ivtv: api call 0x0000009b Oct 19 09:05:51 io kernel: ivtv: init error 13. Code -16 Oct 19 09:05:52 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:52 io kernel: ivtv: api call 0x0000009d Oct 19 09:05:52 io kernel: ivtv: init error 14. Code -16 Oct 19 09:05:53 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:53 io kernel: ivtv: api call 0x0000009f Oct 19 09:05:53 io kernel: ivtv: init error 15. Code -16 Oct 19 09:05:54 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:54 io kernel: ivtv: api call 0x000000a1 Oct 19 09:05:54 io kernel: ivtv: init error 16. Code -16 Oct 19 09:05:55 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:55 io kernel: ivtv: api call 0x000000d0 Oct 19 09:05:55 io kernel: ivtv: init error 17. Code -16 Oct 19 09:05:56 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:56 io kernel: ivtv: api call 0x000000d8 Oct 19 09:05:56 io kernel: ivtv: init error 18. Code -16 Oct 19 09:05:56 io kernel: Oct 19 09:05:57 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:57 io kernel: ivtv: api call 0x000000d6 Oct 19 09:05:57 io kernel: ivtv: init error 20. Code -16 Oct 19 09:05:57 io kernel: saa7115[0]: decoder disable output Oct 19 09:05:58 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:58 io kernel: ivtv: api call 0x000000cd Oct 19 09:05:58 io kernel: ivtv: init error 19. Code -16 Oct 19 09:05:58 io kernel: Oct 19 09:05:58 io kernel: saa7115[0]: decoder enable output Oct 19 09:05:59 io kernel: ivtv: 100 ms time out waiting for firmware Oct 19 09:05:59 io kernel: ivtv: api call 0x00000081 Oct 19 09:05:59 io kernel: ivtv: startcap error 1. Code -16 Oct 19 09:06:02 io kernel: ivtv: Timeout waiting for data! Oct 19 09:06:11 io last message repeated 3 times Oct 19 09:06:21 io kernel: ivtv: 1000 ms time out waiting for firmware Oct 19 09:06:21 io kernel: ivtv: api call 0x00000082 Oct 19 09:06:21 io kernel: ivtv: stopcap error 2. Code -16 And the icing on the cake, from /var/log/myth/mythbackend.log Code: 2004-10-19 09:05:53 Couldn't read data from the capture card in 15 seconds. Game over, man.
Has anybody had these problems before??? |
|
| Author: | cesman [ Tue Oct 19, 2004 7:54 am ] |
| Post subject: | |
Try the 350 in another PCI slot. |
|
| Author: | mrice [ Tue Oct 19, 2004 5:32 pm ] |
| Post subject: | |
cesman: thanks for the suggestion. I found another post on the ivtv forums that mentioned that also in reference to the "game over, man" log message. Unfortunately, it did not seem to help. I had the PVR-350 in the outer-most slot and moved it to the inner-most slot (nearest the CPU). Then brought up live TV, activated the osd (program guide) and scrolled down for about a minute before it stopped playback and this was logged: Code: Oct 19 19:11:00 io kernel: ivtv: DMA read error. Result=0x00000002
Oct 19 19:11:26 io last message repeated 2 times Oct 19 19:11:38 io kernel: ivtv: DMA read error. Result=0x00000002 Oct 19 19:12:09 io kernel: ivtv: ivtv_dec_timeout: lost IRQ; resetting... I then went back into bios and disabled the parallel port, game port, and floppy disk controller, none of which I use anyway. At first I thought that helped, but eventually got the same result. But, on the bright side, no more "game over, man" in mythbackend.log. |
|
| Author: | Xsecrets [ Tue Oct 19, 2004 6:13 pm ] |
| Post subject: | |
well the two most problematic slots are the outermost and innermost, you should probably try one in the middle. |
|
| Author: | mrice [ Tue Oct 19, 2004 9:08 pm ] |
| Post subject: | |
Well, there are only three slots in the 7NIF2, do you really think it's going to make any difference? |
|
| Author: | greywire [ Fri Oct 22, 2004 9:37 am ] |
| Post subject: | similar problem.... |
I seem to be having a similar problem with my setup. I also have a chaintech mobo, but with a hauppauge 250. Latest knoppmyth, fresh install. It seems to hang while watching TV after a few hours. I also am getting video and audio glitching, which gets recorded so it seems like the problem is the 250 card and not the motherboard. The glitching seems to happen all the time. Any ideas yet? |
|
| Author: | mrice [ Fri Oct 22, 2004 4:46 pm ] |
| Post subject: | |
I haven't found a solution yet. I tried rebuilding ivtv from a newer version (ivtv-0.1.10-pre2-ck100z and ivtv-0.1.10-pre2-ck105i) but I can't get X to start with those versions. I posted a plea for help also on the ivtv mailing list, but no response. greywire: do you also get "DMA read error" messages in your /var/log/syslog? |
|
| Author: | greywire [ Sat Oct 23, 2004 11:51 am ] |
| Post subject: | no dma errors... |
I dont see any dma errors, only thing I see pertaining to dma is this: Got DMA-done, but not expecting one |
|
| Author: | mrice [ Tue Oct 26, 2004 6:11 am ] |
| Post subject: | |
I have more symptoms that may be related to the same problem: While trying to copy a recorded show (approx 4GB) across NFS (using ssh), the mythtv completely locked up (about 1.6GB into the transfer). While recording a show, if I tell Mythtv to stop recording, then try to delete the recordded segment (through the same menu as "stop recording"), the backend crashes and I have to reboot. Maybe one of these rings a bell with someone? It starts to sound like a problem with the hda driver? |
|
| Author: | greywire [ Tue Oct 26, 2004 12:31 pm ] |
| Post subject: | |
I had something similar happen to me last night. I wonder our drives are bad or something is not configured right? Also I was thinking maybe the chaintech doesnt like our memory modules? I've read that its a little finicky about memory... |
|
| Author: | tvmyth [ Sun Nov 14, 2004 7:56 pm ] |
| Post subject: | Move to center pci and try isthmus |
I have the same chaintec /pvr 350 setup. I had similiar problems with program guide always freezing and intermittant freezes during tv recording/watching. I switched to the middle pci slot and still had a program guide freeze. Odly enough, I switched my osd to isthmus http://mysettopbox.tv/phpBB2/viewtopic. ... ht=isthmus and havn't had a problem since. Maybe a coincidence, who knows, but it has been fine for 3 days when I always had lockups 5-10 seconds into osd of the program guide. I had an installation problem (my fault) w/ isthmus. I untarred it in the /usr/share/Mythtv/themes folder, then created an isthmus folder and copied contents. Totally screwed up permissions. The directions say... download and copy tar to /usr/share/Mythtv/themes.....create an isthmus folder, then untar to this folder. After changing to isthmus as the onscreen display, all the problems are gone, program guide works like a charm. Good luck |
|
| Author: | mrice [ Thu Nov 18, 2004 6:56 pm ] |
| Post subject: | will give isthmus a try |
Thanks for the suggestion. I changed the osd to isthmus and will anxiously wait to see if that helped. I also get lockups every time the myth tries to switch from a live program I am watching to recording something else. The osd comes up and asks if I want to let it do it or keep watching tv, but no matter which response I give it, if I am still watching live tv when the time comes, it goes black and has to be rebooted. I have just about given up on this ever working properly, so I really hope changing the osd works. |
|
| Author: | greywire [ Fri Nov 19, 2004 5:26 pm ] |
| Post subject: | |
Quote: if I am still watching live tv when the time comes, it goes black and has to be rebooted
I'm still having this same problem, even with isthmus. I've noticed that it does come back when the show is done recording. And you can do: /etc/init.d/gdm restart from an SSH session on another computer and it resets things in all cases where it locks up. I've also noticed that, even with 512MB ram, mythtv consumes it all after some time, and starts using swap -- which then makes video stutter. Again, the "..gdm restart" command above solves the problem, freeing more than half the memory and video then plays fine again. |
|
| Author: | mrice [ Tue Nov 30, 2004 2:53 pm ] |
| Post subject: | |
An update: Changing to isthmus on my setup has definitely improved stability. I have gotten one or two crashes since then, but no where near as many as I was getting. The frontend still hangs when I try to go into cutlist edit mode, but that is apparently a separate issue that I'll have to wait for a fix for. |
|
| Author: | greywire [ Tue Nov 30, 2004 2:59 pm ] |
| Post subject: | |
yeah, isthmus is more stable for some reason, but I still get lockups often enough that its unusable for my family (the wife wont go near my box). I find it anoying to type "/etc/init.d/gdm restart" and nobody else has the skill or patience or desire to even do that. Can't really blame them. So, my mythtv is nearly useless... |
|
| Page 1 of 2 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|