I actually did it. What happened was that several hours after I had started the miner I found the 7-chain/h number reported by the last new-block message shown in the console to be 6.8, which was much higher that normal. Then I noticed that only 2 (two) 7-chains have been found. I expected much more. I pressed s and saw there have been 2 hours 43 minutes since the miner had been started. I looked at the block number in the last new-block message and found the block number was more than 100 behind the latest block found on ypool. That definitely proved that the miner had been stuck for a long time. And the 6.8 7c/h with 2 chains found means the miner found the last block at 60/6.8*2 =~ 20min . The log showed two 7 chains. The miner usually find about 40 6-chains and 4 7-chains when everything worked. hope this helps.
I am seeing something like this too, After long times connected, in my case ~ 4days 7hours, I see the last block reported being 361823 yet Ypool is reporting data from 362213.
The CPU is humming along at 100% If I turn SPS messaging on I get a steadily declining values per hour the pps and SPS seem to fluctuate, the ACC also seem to fluctuate between 836 and 854, And NPS also appears random I don't get any new blocks reporting being found, no disconnection message. I've been watching it like 40 minutes now.
I've tried one diagnostic test, I manually disconnected my wireless connection the miner doesn't seem to notice. I reconnect, the miner doesn't seem to notice that either.
This isn't the first time I've seen this happen, more like the third time, I've been using JHprimeminer-T17 for a few weeks now.
Thanks for any interest, or solutions.