MVP restarting while watching video

[psycik]

Ok, so I ran with the 20070830 version of the mvpmc dongle. Did seem to be going well, and then it started dieing again.

I not sure if it's perception, but live tv seemed a bit more stable.

I caught the logs from it dieing again, and found the error.

Code:

2007-09-19 21:58:51.921    VERBOSE    [6]    MVP data taking too long, connection must have been dropped!

Had a look on the server to see if there were any tcpip errors, and looked at my router - but being a dlink it doesn't tell me much. And the server didn't have any errors.

I'm at a loss, and can only think that you guys will say it looks like a network error - which I would agree with.

So do we think there are any things I can try to diagnose a network problem - some sort of mvp network heart beat?

[mvallevand]

I'm trying to find a missing full minute. Can you check your Event Viewer log to see if the time was updated around 21:06.

Martin

[psycik]

I'm trying to find a missing full minute. Can you check your Event Viewer log to see if the time was updated around 21:06.

Martin

Actually I see no evidence of the time service in the event log, I just forced it manually and nothing went into the event log (Application or system).

I've been pinging the machine with another with some monitoring software - ping every 10 mins or so, and during the 9 am hour, it dropped about 5 times...theres something funny up here, but I'm at a loss as to how to fix it.

[psycik]

Code:

Pinging balrog [192.168.1.50] with 32 bytes of data:

Reply from 192.168.1.50: bytes=32 time=-400ms TTL=128
Reply from 192.168.1.50: bytes=32 time=-400ms TTL=128
Reply from 192.168.1.50: bytes=32 time<1ms TTL=128
Reply from 192.168.1.50: bytes=32 time=-400ms TTL=128

Get some real funny results when I ping another machine - note the negatives. Did see something that this may be related to the dual core....I wonder if some microsoft driver has been put down over a manufacturer one.

[mvallevand]

Code:

Pinging balrog [192.168.1.50] with 32 bytes of data:

Reply from 192.168.1.50: bytes=32 time=-400ms TTL=128
Reply from 192.168.1.50: bytes=32 time=-400ms TTL=128
Reply from 192.168.1.50: bytes=32 time<1ms TTL=128
Reply from 192.168.1.50: bytes=32 time=-400ms TTL=128

Get some real funny results when I ping another machine - note the negatives. Did see something that this may be related to the dual core....I wonder if some microsoft driver has been put down over a manufacturer one.

Is that a down under thing like the toilet flushing backwards? Serviously the only thing I can think would cause that is overclocking too high, a nic card issue, or a mis-match possibly misconfiguration of the duplex setting. mvpmc likes full duplex if you can.

Also do you know what happened when it stopped. Did video freeze and with a lengthy delay or did it drop right to the mvpmc screen?

Martin

[psycik]

With mvpmc the video freezes - once with live tv it recovered. The only resolution is hit the off button on the mvp remote.

Then when turning it on again, sometimes it gets the gbpvr screen (I set the config to go to emulation mode directly) - but other times it only gets as far as the mvpmc screen - then I hit emulation directly.

Full duplex is set as part of the xp network adapters properties isn't it?? The machine is not overclocked and I don't see why it would be the duplex thing as it was fine a couple of weeks ago.....

[mvallevand]

Sub, might have more to add, but if you want to see what mvpmc is doing when the crash is happening I can send you more instructions on getting more debug info. It's great you were able to load the config file.

Martin

[sub]

There isnt too much I can do from here (no access to code etc), but if the problem is still there when I'm back, then we can take a closer look.

[psycik]

I guessing its not a gbpvr/mvp problem, looks like the server has "issues". Ive updated the network drivers and might look at the chipset/amd ones later today.

In the hope that one of the windows updates shagged it.

Failing that it might be rebuild time....

[mvallevand]

I a remember writing debug instruction already so here they are

http://forums.gbpvr.com/showpost.php?p=1...stcount=37

You can help by starting the telnet session by issuing

rdate -s your.favourite.timeserver.name

Then the minutes will match.

Martin