View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 5 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sat Mar 10, 2012 2:31 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 252
Location: GA, USA
In the past few weeks, both with 7.1 and 7.2, I've been getting kicked out of recorded programs while watching them. Rather than a segfault, mythtv seems to be exiting cleanly, storing a bookmark, etc, all the way to the main menu. It's the equivalent of someone hitting the esc key rapidly at least 3 times because the system backs out of the recording, backs out of the recorded programs, and ends up at the main menu. It happens too quickly for it to be an accidental button press. There is one keyboard attached to the computer and nothing is on top of it that might press esc accidentally. I'm using a Harmony 550 remote to emulate a Hauppauge Grey remote which is also in my coffee table but I've verified no buttons are being pressed on it.

Below are the mythfrontend and mythbackend logs for the sequence surrounding the most recent occurrence. In this case, I started a program and it auto quit after about a minute, I restarted it, it auto quit again, I restarted it, and then I manually exited. There doesn't seem to be a noticeable difference in the logs between my intentional termination of the recording and the times I'm kicked out. There are some other, possibly unrelated errors in the log I'm also trying to track down.

Pastebin links:
Frontend Log
Backend Log

Errors that jump out at me:
mythfrontend.log wrote:
2012-03-10 13:45:49.730 ALSA, Error: Setting hardware audio buffer size to 128
2012-03-10 13:45:49.730 ALSA, Error: Error opening /proc/asound/card0/pcm1p/sub0/prealloc: Permission denied.
2012-03-10 13:45:49.730 ALSA, Error: Try to manually increase audio buffer with: echo 128 | sudo tee /proc/asound/card0/pcm1p/sub0/prealloc
2012-03-10 13:45:49.730 ALSA, Error: Unable to sufficiently increase ALSA hardware buffer size - underruns are likely
I've tried the suggestion and the /proc/asound/card0/pcm1p/sub0/prealloc file remains at 64 even after editing as root and changing the number to 128. I also changed the file's group to audio, made sure mythtv was a member, and permitted group write.

mythbackend.log wrote:
2012-03-10 13:51:16.291 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (957 errors)
2012-03-10 13:51:19.846 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (946 errors)
2012-03-10 13:51:20.851 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (953 errors)
2012-03-10 13:51:21.858 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (956 errors)
2012-03-10 13:51:22.864 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (947 errors)
2012-03-10 13:51:23.872 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (954 errors)
2012-03-10 13:51:24.876 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (959 errors)
2012-03-10 13:51:25.880 MythSocket(ffffffffa4f72778:49): writeStringList: Error, No data written on writeBlock (959 errors)
I've seen this error mentioned on the mailing list but haven't seen a good solution.

Any ideas on how to fix this problem so that my recordings stop quitting on me? What other logs can I check?

_________________
LinHES R8.6 BE/FE GIGABYTE GA-X48-DS5 / EVGA GeForce 9800 GTX+ / 4GB DDR2 RAM


Top
 Profile  
 
PostPosted: Fri Mar 16, 2012 4:13 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 252
Location: GA, USA
I'm bumping this because I hope someone can provide some insight or tell me what else I can look at to troubleshoot. I've tried manually optimizing the database, choosing repair tables in mythweb (even though they already reported OK), looked in every log I can find, and still nothing. We get randomly kicked out of recordings every time we try to watch recorded programs. I'm thinking it might be a FE problem because my slave FE in another room was able to watch programs without getting kicked out.

The errors I listed above still show up, but I don't know if they are even relevant. I also noticed the new dated directories in /var/log and checked the logfiles there. All I'm getting are messages repeated over and over about how it can't read the CD when in fact the CD drive is empty. Nothing that seems to be related to recorded programs ending unexpectedly.

My WAF is dropping by the day. Please let me know if you can think of what else to check.

Thanks.

_________________
LinHES R8.6 BE/FE GIGABYTE GA-X48-DS5 / EVGA GeForce 9800 GTX+ / 4GB DDR2 RAM


Top
 Profile  
 
PostPosted: Sat Mar 17, 2012 9:45 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1532
Location: California
What remote control and what remote receiver are you using? Is it possible that some other device in the room is sending rapid fire IR sequences that are being picked up by your receiver?

Try ssh'ing into your box and running "irw". Replicate the circumstances. If some device is generating IR sequences, IRW will show them to you concurrent with your frantend reacting to them. Repeat the same experiment using "ir-keytable -t" instead of "IRW". Again, let's see what the output is.

Please also post the output of "ir-keytable".

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 
PostPosted: Sat Mar 17, 2012 9:47 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1532
Location: California
One more request - please try the experiment with the keyboard both plugged in and unplugged. I doubt it is the keyboard, but the diagnostic process kinda requires us to try all the angles...

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 
PostPosted: Fri Jun 15, 2012 8:24 pm 
Offline
Joined: Wed Apr 12, 2006 3:05 pm
Posts: 252
Location: GA, USA
I swear I'm the worst about previewing a post and then forgetting to hit submit. Anyway, in case this helps anyone else, I upgraded my NVIDIA drivers manually following another post here on linhes.org. After upgrading I stopped experiencing these errors. It was a while ago so I didn't remember the exact steps, but this problem hasn't occurred once since the driver update.

_________________
LinHES R8.6 BE/FE GIGABYTE GA-X48-DS5 / EVGA GeForce 9800 GTX+ / 4GB DDR2 RAM


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 14 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu