I tried that kernel on sys-net with no change yes, but dom0's kernel has not changed.
Would it perhaps be an issue with xen's PCI passthrough functionality? Could it be left in a broken state after a suspend and thus sys-net is not able to have proper access to the network device? Thanks for helping with testing and debugging. Andrew Morgan On August 23, 2017 2:02:36 PM PDT, [email protected] wrote: >On Wednesday, August 23, 2017 at 2:38:11 PM UTC-6, Andrew Morgan wrote: >> I did perform a dom0 update a few days ago, but I think this behavior >only started after restarting Qubes fully. >> >> >> >> Do you have security-testing enabled in dom0? Perhaps it is an issue >with an unstable kernel/xen version. >> >I have been exploring that possibility. Right now I'm back at >4.9.35-19.pvops.qubes.x86_64 and seeing the same issue. You said you >rolled back to 4.4.67-13 and were still seeing it, though, right? That >has me wanting to look closer at any qubes-specific changes that may >have been in the last update. I've been seeing this happen on 3 out of >4 identical-hardware systems and trying to figure out why the 4th one >is fine. > >Right now I'm trying to chase down the freezing issues I'm getting on >one system, which seem to be a different problem and not something I'm >seeing on any of the other identical hardware, but I'll look into the >update notes after that. > >Dan -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/B79CD505-D729-43E7-A768-3C4699B67C11%40amorgan.xyz. For more options, visit https://groups.google.com/d/optout.
