search for: 10000msec

Hi, folks, We've been recently (the last few months) having issues on workstations with the radeon driver. A typical sample is this, from /var/log/messages: Jan 23 11:35:32 <workstation> kernel: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec Jan 23 11:35:32 <workstation> kernel: radeon 0000:03:00.0: GPU lockup (current fence id 0x0000000000000212 last fence id 0x0000000000000213 on ring 0) Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: Saved 23 dwords of commands on ring 0. Jan 23 11:35:33 <workstation> ke...

...een by the most delayed frame minus the delay seen by the least delayed frame. The jitter buffer only has a relative view of things and doesn't know the absolute delay - because it only has the other side's timestamps to look at. So you can see that you could get a 20msec lag and even a 10000msec jitter. I'd just comment that the jitter buffer only needs to account for jitter. It matters nowt to the jitter buffer if the packets have been 2 hours in transit as long as they arrive at a steady pace. Sometimes timestamps on an iax call do jump rather than incrementing steadily. Th...

...c00000)" although the position may vary. even if the same value was computed earlier in the results array The first patch of this series does not change the behavior (or instruction dump). however, using the ADDC instruction results in hang on every cos test "ring 0 stalled for more than 10000msec" "GPU lockup (waiting for 0x00000000001023cf last fence id 0x00000000001023ce on ring 0)" although the actual test results follow the same result as before (random failures mostly in float8/16 tests). I can even get test pass with hang on every subtest Using SIGN_EXTEND_INREG inste...