SM problem

Products PMP
1

Anyone ever see ping time - ?
Actually I just try to ping my SM and it showed:

Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-15ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-10ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=-17ms TTL=255
Reply from 169.254.1.20: bytes=32 time=3ms TTL=255
Reply from 169.254.1.20: bytes=32 time=2ms TTL=255

2

Canopy’s so fast, it goes back in time!

Actually I’ve heard of it before. I’m willing to bet it’s nothing to do with the SM, and that you have an AMD processor and need to update drivers. TO THE GOOGLEMOBILE!