On Wednesday, August 23, 2017 at 9:05:42 PM UTC-6, Reg Tiangha wrote: > On 2017-08-23 3:08 PM, Andrew Morgan wrote: > > 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 > > > > > Have you guys tried blacklisting your wireless driver modules as per > these instructions here: > > https://www.qubes-os.org/doc/wireless-troubleshooting/#automatically-reloading-drivers-on-suspendresume > > The people who have been experiencing the same issues say that this > workaround works.
Thanks, I hadn't found that page yet. Unfortunately, that doesn't seem to fix it. Andrew, in your case, when the wifi locks up, do you sometimes/always get issues in dom0 as well? For example, I can have problems where I can't open or run certain binaries, but not all binaries have problems. Right now I can't open the dom0 terminal. I get: Failed to execute command "exo-open --launch TerminalEmulator" Failed to execute child process "exo-open" (input/output error) The input/output error is what I get if I had the terminal open before suspending and attempt something like lspci or attempting ls/vi a log. At this point, I'm looking at https://github.com/QubesOS/qubes-issues/issues/2922 to see if that is related. -- 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/59982449-a1b8-42f7-8a5e-b1f9653c66e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
