Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1043116" data-attributes="member: 82144">Hello SashaA bug report thread would have been more appropriate. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />On your system it takes approximately 10 seconds for all the power related device change/reconnect messages to settle down. I see errors only when you're attempting to start timeshifting very shortly after the system has resumed. For example:SUCCESS!FAIL!FAIL!SUCCESS!FAIL!SUCCESS!So, first it is not always failing.I don't see that in your log files... at all.This is not true.If you use a static IP address configured on the network adaptor (not in the router!) then it is almost true... but still, the network adaptor driver needs time to reinitialise after resume as well.mm</blockquote>

[QUOTE="mm1352000, post: 1043116, member: 82144"] Hello Sasha A bug report thread would have been more appropriate. ;) On your system it takes approximately 10 seconds for all the power related device change/reconnect messages to settle down. I see errors only when you're attempting to start timeshifting very shortly after the system has resumed. For example: SUCCESS! FAIL! FAIL! SUCCESS! FAIL! SUCCESS! So, first it is not always failing. I don't see that in your log files... at all. This is not true. If you use a static IP address configured on the network adaptor (not in the router!) then it is almost true... but still, the network adaptor driver needs time to reinitialise after resume as well. mm [/QUOTE]

Verification