We upgraded our zero clients to 4.5 firmware about three weeks ago, and since then we've been having problems with screens going black for 3-5 seconds and then coming back on. We've also had occasions where the screens go blank and won't come back on without disconnecting and reconnecting (twice). Checking the zero client logs we're seeing a string of these events when this happens:
| 7-08T13:41:08Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): Insufficient imaging resources. Dropping imaging data. |
| 2014-07-08T13:41:08Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): RDMA size_left= 0 chain_left=21 total_desc_used=401 free_desc=109 |
| 2014-07-08T13:41:09Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): Insufficient imaging resources. Dropping imaging data. |
| 2014-07-08T13:41:09Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): RDMA size_left= 0 chain_left=24 total_desc_used=401 free_desc=108 |
| 2014-07-08T13:41:09Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): Insufficient imaging resources. Dropping imaging data. |
| 2014-07-08T13:41:09Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): RDMA size_left= 0 chain_left=25 total_desc_used=401 free_desc=104 |
| 2014-07-08T13:41:09Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): Insufficient imaging resources. Dropping imaging data. |
| 2014-07-08T13:41:09Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): RDMA size_left= 0 chain_left=24 total_desc_used=401 free_desc= 99 |
| 2014-07-08T13:41:10Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): Insufficient imaging resources. Dropping imaging data. |
| 2014-07-08T13:41:10Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): RDMA size_left= 0 chain_left=19 total_desc_used=401 free_desc=108 |
| 2014-07-08T13:41:19Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): Insufficient imaging resources. Dropping imaging data. |
| 2014-07-08T13:41:19Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): RDMA size_left= 0 chain_left= 0 total_desc_used=401 free_desc= 98 |
| 2014-07-08T13:41:25Z> LVL:2 RC: 0 | MGMT_IMG :Resetting imaging codec. |
| 2014-07-08T13:41:25Z> LVL:2 RC: 0 | MGMT_IMG :Resetting imaging codec. |
| 2014-07-08T13:41:25Z> LVL:2 RC: 0 | LOCAL_CURSOR :Display0: w=1920 (dmt=1920) h=1080 (dmt=1080) x=0 y=0 rot=0 |
| 2014-07-08T13:41:25Z> LVL:2 RC: 0 | LOCAL_CURSOR :Display1: w=1920 (dmt=1920) h=1080 (dmt=1080) x=1920 y=0 rot=0 |
| 2014-07-08T13:41:25Z> LVL:2 RC: 0 | LOCAL_CURSOR :Display2: w=0 (dmt=0) h=0 (dmt=0) x=0 y=0 rot=0 |
| 2014-07-08T13:41:25Z> LVL:2 RC: 0 | LOCAL_CURSOR :Display3: w=0 (dmt=0) h=0 (dmt=0) x=0 y=0 rot=0 |
| 2014-07-08T13:41:25Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): Insufficient imaging resources. Dropping imaging data. |
| 2014-07-08T13:41:25Z> LVL:2 RC:-513 | MGMT_IMG :(pkt_rx_resource_check): RDMA size_left=28 chain_left=31 total_desc_used=401 free_desc=108 |
| 2014-07-08T13:41:27Z> LVL:1 RC:-500 | MGMT_IMG :(pkt_rx_resource_check): Resetting imaging due to prolonged error condition. |
| 2014-07-08T13:41:27Z> LVL:2 RC: 0 | MGMT_IMG :Resetting imaging codec. |
| 2014-07-08T13:41:28Z> LVL:2 RC: 0 | MGMT_IMG :Resetting imaging codec. |
| 2014-07-08T13:41:29Z> LVL:2 RC: 0 | MGMT_IMG :Resetting imaging codec. |
I have a ticket open with Teradici and they are looking at the problem but I thought I'd post this in case anyone else is considering moving to the 4.5 release. I have yet to see this on the few Tera2 clients I have here, so perhaps it's only a Tera1 issue? This is in a View 5.3 environment with dual 1920x1280 monitors and Apex offload cards.
Geoff