Can a PCoIP "Zero" Client Crash?

hmartin · ‎03-12-2010

I've had a user who has been "knocked out" of her VM several times. She's using a Wyse P20 'zero' client. Just before getting kicked out of the VM, she sees some display corruption. Shortly after that, she finds herself back at the VMware View login screen. The P20 does not reboot, and I haven't been able to find anything in any of the various View logs. However, today I was able to get the following from the event log of the Wyse P20. Anyone got any ideas what this means? I'll also contact Wyse and will post the findings here.

0d,00:00:00.000> Bootloader Version: 2.1

0d,00:00:00.000> Bootloader Build ID: v163

0d,00:00:00.000> Bootloader Build date: Aug 28 2008 16:56:13

0d,00:00:00.000> (MGMT_SYS): ******************************************************

0d,00:00:00.000> (MGMT_SYS): *** CRITICAL ERROR CONTEXT DUMP ***

0d,00:00:00.000> (MGMT_SYS): Reset cause: RTOS

0d,00:00:00.000> Previous Bootloader Build ID: v163 , Version: 2.1

0d,00:00:00.000> Previous Firmware Build ID: v250 , Version: 3.0

0d,00:00:00.000> (MGMT_SYS): GPR[ 1]: 0x804FF01C

0d,00:00:00.000> (MGMT_SYS): GPR[ 2]: 0x1000FF01

0d,00:00:00.000> (MGMT_SYS): GPR[ 3]: 0x00000006

0d,00:00:00.000> (MGMT_SYS): GPR[ 4]: 0x0000000A

0d,00:00:00.000> (MGMT_SYS): GPR[ 5]: 0x806752A0

0d,00:00:00.000> (MGMT_SYS): GPR[ 6]: 0x0000008D

0d,00:00:00.000> (MGMT_SYS): GPR[ 7]: 0x00000001

0d,00:00:00.000> (MGMT_SYS): GPR[ 8]: 0x000001FE

0d,00:00:00.000> (MGMT_SYS): GPR[ 9]: 0x8126AEA8

0d,00:00:00.000> (MGMT_SYS): GPR[10]: 0xA21C2000

0d,00:00:00.000> (MGMT_SYS): GPR[11]: 0x00000005

0d,00:00:00.000> (MGMT_SYS): GPR[12]: 0x806FCFA2

0d,00:00:00.000> (MGMT_SYS): GPR[13]: 0x00000000

0d,00:00:00.000> (MGMT_SYS): GPR[14]: 0x8126AEA8

0d,00:00:00.000> (MGMT_SYS): GPR[15]: 0x00000001

0d,00:00:00.000> (MGMT_SYS): GPR[16]: 0x0000000A

0d,00:00:00.000> (MGMT_SYS): GPR[17]: 0x806F888C

0d,00:00:00.000> (MGMT_SYS): GPR[18]: 0x1000FF01

0d,00:00:00.000> (MGMT_SYS): GPR[19]: 0x1000FF01

0d,00:00:00.000> (MGMT_SYS): GPR[20]: 0x00000002

0d,00:00:00.000> (MGMT_SYS): GPR[21]: 0x8126A584

0d,00:00:00.000> (MGMT_SYS): GPR[22]: 0x00000068

0d,00:00:00.000> (MGMT_SYS): GPR[23]: 0x807139B8

0d,00:00:00.000> (MGMT_SYS): GPR[24]: 0x00000000

0d,00:00:00.000> (MGMT_SYS): GPR[25]: 0x00000000

0d,00:00:00.000> (MGMT_SYS): GPR[26]: 0x08397E94

0d,00:00:00.000> (MGMT_SYS): GPR[27]: 0x04176E8D

0d,00:00:00.000> (MGMT_SYS): GPR[28]: 0x806A4600

0d,00:00:00.000> (MGMT_SYS): GPR[29]: 0x8126ADF0

0d,00:00:00.000> (MGMT_SYS): GPR[30]: 0x8126ADF8

0d,00:00:00.000> (MGMT_SYS): GPR[31]: 0x8005D420

0d,00:00:00.000> (MGMT_SYS): COP0 CAUSE: 0x00800000

0d,00:00:00.000> (MGMT_SYS): COP0 STATUS: 0x1000FF00

0d,00:00:00.000> (MGMT_SYS): COP0 EPC: 0x8050DDD4

0d,00:00:00.000> (MGMT_SYS): COP0 BADVADDR: 0x7D779ED9

0d,00:00:00.000> (MGMT_SYS): Call stack:

0d,00:00:00.000> (MGMT_SYS): func( 0): 0x8005D160

0d,00:00:00.000> (MGMT_SYS): func( 1): 0x8005D420

0d,00:00:00.000> (MGMT_SYS): func( 2): 0x8005D4B4

0d,00:00:00.000> (MGMT_SYS): func( 3): 0x8005C820

0d,00:00:00.000> (MGMT_SYS): func( 4): 0x80390F58

0d,00:00:00.000> (MGMT_SYS): func( 5): 0x801E98B4

0d,00:00:00.000> (MGMT_SYS): func( 6): 0x801E9BB0

0d,00:00:00.000> (MGMT_SYS): func( 7): 0x8050D604

0d,00:00:00.000> (MGMT_SYS): Thread system state: 0x00000000

0d,00:00:00.000> (MGMT_SYS): Current thread executing ptr: 0x8126AEA8

0d,00:00:00.000> (MGMT_SYS): Next thread to execute ptr: 0x8126AEA8

0d,00:00:00.000> (MGMT_SYS): Current thread executing: VRDMA

0d,00:00:00.000> (MGMT_SYS): Next thread to execute: VRDMA

0d,00:00:00.000> (MGMT_SYS): Thread stack check: mgmt_ui_gui_thread (8192/8192)

0d,00:00:00.000> (MGMT_SYS): ******************************************************

0d,00:00:00.000> Firmware Part Number: FW010059

0d,00:00:00.000> Firmware Version: 3.0

0d,00:00:00.000> Firmware Build ID: v250

0d,00:00:00.000> Firmware Build date: Dec 7 2009 15:54:24

0d,00:00:00.000> PCoIP processor ID: 0x1100, revision: 1.0

0d,00:00:00.000> Boot-up complete

0d,00:00:00.000> Unique Identifier: 00-80-64-86-20-D7

0d,00:00:00.000> HDA is enabled

0d,00:00:00.000> PCoIP device name: pcoip-portal-0080648620d7

0d,00:00:00.000> PCoIP device description:

0d,00:00:00.000> Generic tag:

0d,00:00:00.010> POST: HD Audio test PASSED

0d,00:00:00.510> POST: ethernet PHY test PASSED

0d,00:00:00.510> POST: self-test PASSED

0d,00:00:02.900> Network link UP

0d,00:00:02.910> Auto-negotiation disabled, forcing speed and duplex settings

0d,00:00:02.910> Network link rate: 100 Mbit/s, duplex: FULL

0d,00:00:02.910> Requesting DHCP lease

0d,00:00:06.910> Ethernet (LAN) Adapter (10.132.11.53, 00-80-64-86-20-D7)

0d,00:00:08.020> Ready to connect with host

0d,00:00:08.060> DNS based discovery prefix:

0d,00:00:08.060> (DNS SRV) Discovery (DHCP options 15): hma.am.honda.com

0d,00:00:08.060> (DNS SRV) Discovery (DHCP options 12):

0d,00:00:08.350> (DNS SRV: Config Tool) Discovery complete: 207.131.132.185

03/12/2010, 14:14:17> (MGMT_TOD): NTP time acquired, uptime = 89 seconds

All

Can a PCoIP "Zero" Client Crash?