[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
Hi, I had the same issue, and the workaround metioned by Reg worked for me: https://www.qubes-os.org/doc/wireless-troubleshooting/#automatically-reloading-drivers-on-suspendresume Maybe there are two differen issues. Just to be sure, do you restarted the sys-net after modify the /rw/config/suspend-module-blacklist file? -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5cc0c7b1-b614-474a-ab5b-6472f022bf99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
> At this point, I'm looking at > https://github.com/QubesOS/qubes-issues/issues/2922 to see if that is related. I decided the previous bug may not be the same so I opened a new issue if you want to follow/join in, Andrew. https://github.com/QubesOS/qubes-issues/issues/3049 -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d2b553dd-74b8-4d21-bc54-ae61deffafa4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. 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.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
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. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/onlfpa%24jsj%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
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, djeff...@linuxfoundation.org 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. 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.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b9a7bb5e-0c0b-4497-b359-3347495c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
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. Andrew Morgan On August 23, 2017 11:00:56 AM PDT, djeff...@linuxfoundation.org wrote: >> As of late (past couple days), I have been unable to connect to WiFi >> networks without a full shutdown and restart of sys-net. After every >> time I suspend the computer I get the message that my WiFi card says >> 'device not ready', and it is unable to scan for WiFi networks. >> Restarting NetworkManager.service does not fix the issue. >> >> Looking at dmesg, it seems to be some problem relating to Intel >> micro-code? I am using an Intel WiFi card (Intel 7260 rev bb) >> >I'm fighting the same problem at the moment (along with some random >freezing) that seems to have started with the last dom0 update. Does >that seem to correlate with the time you saw this behavior start? > >I'm running an Intel 7265 rev 59. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/BC45DCD6-F428-4432-97F7-E2F7F78261A2%40amorgan.xyz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Network Manager: 'Device not ready' after suspend.
> As of late (past couple days), I have been unable to connect to WiFi > networks without a full shutdown and restart of sys-net. After every > time I suspend the computer I get the message that my WiFi card says > 'device not ready', and it is unable to scan for WiFi networks. > Restarting NetworkManager.service does not fix the issue. > > Looking at dmesg, it seems to be some problem relating to Intel > micro-code? I am using an Intel WiFi card (Intel 7260 rev bb) > I'm fighting the same problem at the moment (along with some random freezing) that seems to have started with the last dom0 update. Does that seem to correlate with the time you saw this behavior start? I'm running an Intel 7265 rev 59. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/52e8797c-a381-45df-aadc-5b18848ee6db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
