2015-02-28, 19:49
Hi, i want to ask you guys for help figuring out what's causing my freezing problem.
It's a strange problem because it only happens once per boot (i can be wrong about this, it MAY be once per movie... i just realized i haven't tested this).
I replicated the issue by turning on my htpc, opening a movie (i'm streaming it, not using a local file) and let it run for a while.
Usually, around 5-10 min in i get a huge freeze, like 3-5 sec freeze of the image (sound keep going fine) and then the image speeds up to meet the timestamp it was suppose to be at.
I checked the time and then went into the log and exactly at that time i'm getting
Before i saw this i thought it was something like the GPU HANG talked about here, so i updated the kernel and tested, still have the problem.
Here's the complete Logs:
Before Kernel update - HAS DEBUG ON
After Kernel update - HAS DEBUG OFF
You can see the same lines on both files and both of them are on time with the visual problem i witnessed.
If you want i'll take another after the kernel update with debug on.
Well, thanks in advance for any help.
If i forgot to give you some info you need sorry about that, i'll post it asap.
It's a strange problem because it only happens once per boot (i can be wrong about this, it MAY be once per movie... i just realized i haven't tested this).
I replicated the issue by turning on my htpc, opening a movie (i'm streaming it, not using a local file) and let it run for a while.
Usually, around 5-10 min in i get a huge freeze, like 3-5 sec freeze of the image (sound keep going fine) and then the image speeds up to meet the timestamp it was suppose to be at.
I checked the time and then went into the log and exactly at that time i'm getting
Code:
14:15:11 T:140728588019456 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
14:15:17 T:140728588019456 WARNING: Previous line repeats 75 times.
14:15:17 T:140728588019456 DEBUG: CPullupCorrection: detected pattern of length 1: 41708.33, frameduration: 41708.333333
Before i saw this i thought it was something like the GPU HANG talked about here, so i updated the kernel and tested, still have the problem.
Here's the complete Logs:
Before Kernel update - HAS DEBUG ON
After Kernel update - HAS DEBUG OFF
You can see the same lines on both files and both of them are on time with the visual problem i witnessed.
If you want i'll take another after the kernel update with debug on.
Well, thanks in advance for any help.
If i forgot to give you some info you need sorry about that, i'll post it asap.