MVP crash in 98.8b

[RangerBob]

Hello all,

Still suffering crashout problems with version 98.8b on the MVP im afraid. Was trying to play back a program for the girlfriend, and the MVP would not hold up for more than 10-20 mins at a time. I have attached a log of one of the crashes. I notice some unknown request messages from the MVP, no idea if they are anything to do with it. According to the GBPVR service, the MVP just stops responding. Any ideas anyone?

[ATTACHMENT NOT FOUND]

[JimF]

Without knowing anything about your setup, I would guess a router problem. What type is it? Have you updated the firmware? You are not using wireless are you?

[RangerBob]

Setup is as follows:

My topography is as follows (hope the ascii art works!):

| = Cat5
|| = Powerline


BT DSL line
|
|
Router & DHCP (Netgear DG834PN Wireless rangemax ADSL router)
| |
| +------- (various other PCs)
|
HDX101(1)
||
(downstairs ring main)
||
||===(upstairs ring main)======== HDX101(2) ------ GBPVR server box
||
(downstairs ring main)
||
HDX101(3)
|
|
MVP


I am not running wireless, I am running across Netgear Homeplug AV (200 Mbps). The router firmware is running at the latest stable.

I was having no issues with this setup at version 96.12. I upgraded to version 97.13, to try and help another forum member, and to fix some other issues, and things started to become unstable. Running the latest version I can't even run playback for more than 20 mins. If you check the logs I sent, you can see there are unknown messages coming back from the MVP. I've not seen those before. If I hook up directly by CAT5, I didnt see any improvement.

There was no stuttering, lagging or jumping onplayback, was running smooth as ice, then bam! "Contacting servers". On running a diagnostics I am showing *very very* little to no packet loss.

I unplugged and replugged the MVP several times to ensure the dongle was correct.

Any comments on these unknown messages anyone?

[stefan]

I don't know how the MVP works, but

I unplugged and replugged the MVP several times to ensure the dongle was correct.

did you make sure you "witch back to the default dongle.bin file" (quote from sub). I don't know how you do that, and you might already have done it... just wanting to point out the obvious

[RangerBob]

Yes, I checked. Only one dongle appears in the config selection, so I made sure it was the right one. I'm seeing the "video in a window" stuff so it must be using the latest.

Just to note, I previously applied all tipsters networking tweaks (they worked well btw) for NIC offloading, frame size etc.

[HtV]

Couldn't the Powerlines be suffering from a disturbance on the electric net. Some machine starting or whatever? I've seen reports on problems through "noise" on the line through nearby industry.

[JimF]

I suspect that is the weak link too. The average speed of powerline may be OK, but it could be subject to a lot of momentary disruptions.

[RangerBob]

The Powerline gear was solid before the upgrade from 96.12. Using diagnostics shows very little to no packet loss.

I am more concerned with the "unknown messages" coming back from the MVP. Each time the unit has crashed, upon inspecting the logs, i notice these unknown messages coming back, about 20 seconds before the connection is dropped. I also notice it always crashes directly after the storeLastPlaybackPosition message. Here is a section of the latest log:

12/09/2006 19:20:19.772 VERBOSE [10] Request 200000 bytes (file size:1804220416 file location: 1301921745)
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (8)
12/09/2006 19:20:19.892 VERBOSE [9] Responding to ping
12/09/2006 19:20:19.892 VERBOSE [9] getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (0)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 0
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (0)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 0
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (0)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 0
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (77)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 77
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (156)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 156
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (205)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 205
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (17)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 17
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (0)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 0
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:19.892 VERBOSE [9] MVP data read: 1 (0)
12/09/2006 19:20:19.892 WARNING [9] Received unknown request of type: 0
12/09/2006 19:20:19.892 VERBOSE [9] MVP request processed
12/09/2006 19:20:20.072 VERBOSE [10] Request 200000 bytes (file size:1804220416 file location: 1302121745)
12/09/2006 19:20:20.192 VERBOSE [9] MVP data read: 1 (9)
12/09/2006 19:20:20.192 VERBOSE [9] MVP request processed
12/09/2006 19:20:20.403 VERBOSE [10] Request 200000 bytes (file size:1804220416 file location: 1302321745)

.... edited for brevity

12/09/2006 19:20:24.909 VERBOSE [9] MVP data read: 1 (8)
12/09/2006 19:20:24.909 VERBOSE [9] Responding to ping
12/09/2006 19:20:24.909 VERBOSE [9] getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
12/09/2006 19:20:24.909 VERBOSE [9] MVP request processed
12/09/2006 19:20:25.059 VERBOSE [10] Request 200000 bytes (file size:1804220416 file location: 1305121745)
12/09/2006 19:20:25.180 VERBOSE [9] MVP data read: 1 (9)
12/09/2006 19:20:25.180 VERBOSE [9] MVP request processed
12/09/2006 19:20:25.420 VERBOSE [10] Request 200000 bytes (file size:1804220416 file location: 1305321745)
12/09/2006 19:20:37.037 VERBOSE [11] PlaybackPositionManager.storeLastPlaybackPosition(D:\Recordings\How Do You Solve A Problem Like Maria\How Do You Solve A Problem Like Maria_20060902_19052005.mpg, 2163)
12/09/2006 19:20:45.188 VERBOSE [9] MVP data taking too long, connection must have been dropped!
12/09/2006 19:20:45.188 VERBOSE [9] MVP Control Thread shutting down....
12/09/2006 19:20:45.188 VERBOSE [9] MVP Control Thread shutdown finished
12/09/2006 19:20:45.188 VERBOSE [10] MVP media connection recycle requested
12/09/2006 19:20:45.359 VERBOSE [10] MVP Streaming Thread shutting down...
12/09/2006 19:20:45.359 VERBOSE [10] MVP Streaming Thread shutdown finished


If anyone wants more logs, I can provide several where exactly the same conditions are met before a crash. This to me does not suggest network problems.

[HtV]

Something happening at those times in other logs? e.g recordingservice log

[RangerBob]

No, the recording service, native logs, tray logs, are all clear of events around this.

Nothing is scheduled to run. The disks not fragmented. I cannot account for anything to cause this.