[confirm] TV not working after hibernation, config crashing (1 Viewer)

[doveman]

After resuming from hibernation, I was unable to start LiveTV and was getting "Unknown error".

I loaded TV Server config and stopped and re-started the TV Service, after which TV Server config froze and although services.msc showed thatTV Service was running, the window in config, where the cards and their state is displayed, was blank.

TV Server closed eventually, after which I restarted MP and LiveTV worked.

 

[kevin939]

I have a very similar problem running RC2 - see https://forum.team-mediaportal.com/...nknown-error-starting-tv-after-suspend-81911/

I believe its something to do with the initialisation of the tv card following resume. I have reverted back to 1.0.2 and with the same setting as on RC2 the system works perfectly.....guess I will have to move to RC3 and get some more logs to help get this debugged

Cheers

 

[jameson_uk]

quite possibly an issue with your TV card being detected on resume. Try setting a delay on recognising cards and see if that helps. If this happens again check in device manager to see if your TV card is listed there. If not this is a hardware or driver issue not MP.

If it happens again you can restart TVService but launching command prompt (need to do this as admin in Vista / Win7)
net stop tvservice
net start tvservice

 

[kevin939]

quite possibly an issue with your TV card being detected on resume. Try setting a delay on recognising cards and see if that helps. If this happens again check in device manager to see if your TV card is listed there. If not this is a hardware or driver issue not MP.

If it happens again you can restart TVService but launching command prompt (need to do this as admin in Vista / Win7)
net stop tvservice
net start tvservice

I suspect the problem does revolve around the tv card. However as I indicated having reverted to MP 1.0.2 in exactly the same configuration (I image my installation) it works like a charm - no hang ups, no unknown error just does what its supposed to.

Is it possible that tv server is not taking any notice of the configured delay following resume?


I am about to roll forward again (to RC3) so will let you know what happens

 

[jameson_uk]

Is it possible that tv server is not taking any notice of the configured delay following resume?

That seems to be fine on startup, not sure about resume

2010-05-19 00:45:30.328125 [(4)]: Detecting Cards in 30 seconds
2010-05-19 00:46:00.328125 [(4)]: Detecting Cards
2010-05-19 00:46:00.343750 [(4)]: Detected IP TV Card 0
2010-05-19 00:46:00.375000 [(4)]: Found card:nova-dt dvb-t tuner (dev1 path0) 
2010-05-19 00:46:00.375000 [(4)]: Detected DVB-T card:nova-dt dvb-t tuner (dev1 path0) 
2010-05-19 00:46:00.390625 [(4)]: Found card:nova-dt dvb-t tuner (dev1 path1) 
2010-05-19 00:46:00.390625 [(4)]: Detected DVB-T card:nova-dt dvb-t tuner (dev1 path1)

So TV service did wait 30 seconds (which is what I presume you have delay set to ) and detected tuners...

So looking at logs your machine went into standby at 17:05 yesterday and came out at 17:10. You then had loads of issues trying to watch TV at 17:13? You then restarted TVService at 17:15 ??

Does this sound about right?

Also does config open for you after clean boot? Finally do you have any anti-virus / firewall installed as looks like the config errors are complaining about not being able to connect to the database

Not sure if this has anything to do with it but you probably want to sort it anyway...

"19/05/2010 01:08:24";"Disk";"(0)";"Error";"The device, \Device\Harddisk0\D, has a bad block.";"3221487623"
"19/05/2010 01:08:27";"Disk";"(0)";"Error";"The device, \Device\Harddisk0\D, has a bad block.";"3221487623"

in your system log. Looks like your hard drive has some issues...

 

[kevin939]

So looking at logs your machine went into standby at 17:05 yesterday and came out at 17:10. You then had loads of issues trying to watch TV at 17:13? You then restarted TVService at 17:15 ??

Does this sound about right?

yes that sounds about right.

Also does config open for you after clean boot? Finally do you have any anti-virus / firewall installed as looks like the config errors are complaining about not being able to connect to the database

config works fine after boot
Antivirus/firewall is installed (COMODO). After problems with wireless cards (dropping off and hence dropping the connection to the tvserver) I have installed microsoft loopback adapter configured as 192.168.2.xxx which is a defined zone to comodo with full access for everyone. Just to make things even better there is a specific rule so that MP and tvserver can access any network using any protocol.

[the set up is exactly the same as for 1.0.2]



thanks for the help and the pointer on the bad blocks Hope its not anther bad disc

 

[bounguine]

For me problems with 1.1.0* still exist.
Downgrading to 1.0.2 solves them perfectly.

These are two my today cases.

 

[arion_p]

For me problems with 1.1.0* still exist.
Downgrading to 1.0.2 solves them perfectly.

These are two my today cases.

Your logs are incomplete. Please always post full logs. Even though you might think some of the logs are irrelevant, they may show what happened before the issue.

From your logs I can only see the following:

1. You have serious network connectivity issues.
2. Your system has two IP addresses on the same subnet. If these are not on the same physical network (i.e. on the same network adapter) this configuration will not work, period. This is how IP works, if you don't believe me search the net. Even if both IP addresses are on the same physical network, I still would not recommend such a configuration, it is simply asking for trouble and franky I don't see the point of such configuration.
3. It is impossible to see from your logs what happened during suspend (because they are incomplete) but it is quite obvious that the system suspended before being instructed by PowerScheduler to do so (or PowerScheduler is not being used?). On resume you can see that TVService is being shutdown and then restarted. PowersScheduler stops TVController of TVService BEFORE suspending and then restarts it AFTER resume.

 

[bounguine]

1. What issues? Can you describe, please. To be frank, with 1.0.2 I didn't have any. I wonder why?
2. All IPs are dynamically given by my router (and they are all unique). Except for static SS2 “native” IP from different subnet and static IP from the same subnet for MS loopback adaptor.
3. Yes, I sent my PC to hibernation with the remote, but not with PowerScheduler. I always do that. When resuming, nnCron stops TVServer, restarts the driver and then starts TVServer again, as PowerScheduler fails to do the same (I have driver issues when resuming). I did the same when using other versions of MP without ant trouble.

I would post “complete” log later, when this occur again. Sorry.

 

[arion_p]

1. What issues? Can you describe, please. To be frank, with 1.0.2 I didn't have any. I wonder why?

The client cannot connect to the server. It appears that the connection is refused. This can happen if there is a firewall blocking the connection or it can sometimes happen when TVService is killed/crashes/ends abruptly.

2. All IPs are dynamically given by my router (and they are all unique). Except for static SS2 “native” IP from different subnet and static IP from the same subnet for MS loopback adaptor.

That's the point. You have two network adapters (MS Loopback and physical LAN) sharing the same subnet. But these two adapters are not connected to the same physical network. MS loopback is connected to is own virtual network while the physical LAN adapter is connected to your LAN. This simply does not work, that's the way the IP protocol is designed.

3. Yes, I sent my PC to hibernation with the remote, but not with PowerScheduler. I always do that. When resuming, nnCron stops TVServer, restarts the driver and then starts TVServer again, as PowerScheduler fails to do the same (I have driver issues when resuming). I did the same when using other versions of MP without ant trouble.

Have you tried using only PowerScheduler in RC3? There have been important fixes regarding PowerScheduler.
Please try not using the remote to send your system to hibernation for a while to see if it makes a difference. If you have configured Windows to hibernate when you press the Power button on your remote, you are going to have issues fore sure. When you do that, TVService does not have a chance to prepare for hibernation.
If you do want to use the remote for that, map the Power button to MP's own "Suspend" action instead (and leave it unmapped in Windows).