On Wednesday, February 7, 2018 at 4:02:38 PM UTC-8, Yuraeitha wrote:
> On Wednesday, February 7, 2018 at 8:58:13 PM UTC+1, Dave C wrote:
> > I've upgraded a laptop from 3.2 to 4.0rc4. I didn't have the problem
> > described here in 3.2...
> >
> > When I sleep the laptop (by closing lid), I find that every time I wake it,
> > sys-net is unresponsive.
> >
> > I cannot bring up a terminal in sys-net. Terminals already open are
> > unresponsive to input.
> >
> > Calling `qvm-shutdown sys-net` does nothing. `qvm-kill sys-net` does kill
> > it.
> >
> > I can restart sys-net and call `qvm-prefs -s sys-firewall netvm sys-net`,
> > in order to be connected to internet again.
> >
> > How can I troubleshoot sys-net, given the description above? Which logs
> > should I be looking at?
> >
> > I have tried putting iwlmvm and iwlwifi in
> > /rw/config/suspend-module-blacklist, but that has not changed the behavior.
> > I'm just not sure what else to try. Thanks!
>
> There is another Qubes users discussion going on atm about how to get around
> this bug, over here
> https://groups.google.com/forum/#!topic/qubes-users/1vijiBx0ftU
>
> For the record, I have this new bug too, and it seems quite a few others also
> have it, so it may perhaps just be a question of little time before its
> fixed. I don't have much time atm to look my self, nor do I have much
> experience. But here is what I'd suggest.
>
> My guess is that you can use "sudo journalctl" in sys-net after restarting
> from a crash. You can also do a "man journalctl" or "journalctl --help" to
> find out how to list the system/kernel state history, or further google it
> for how to use journalctl. The --boot attribute will give you everything
> since last boot till you type that command, though its also possible look at
> the second last boot, or any other saved time-stamps as well.
>
> Also if you use something like "-n 100" to journalctl, then it should only
> list the last 100 lines, instead of thousands upon thousands of lines, which
> can take a while to move through with a slow scrolling down by holding the
> enter key down... tick clock, goes the clock. Better limit that huge log, and
> you're only interested in the last few lines before it freezes anyhow :-)
>
> For example, if you use journalctl on the second last boot, and put it to
> something like last 100 lines, then my guess is it could quite likely give
> you some useful information as to what happened.
>
> I don't think this is a bug outside the sys-net, but is a bug involved inside
> the sys-net VM. Whatever happens, it should probably show up in the
> journalctl before it freezes. But I'm not an expert though.
Thanks for all the advice, and for the pointer to other thread.
For the record, the problem does not happen for me with every sleep/wake.
Although for a while earlier today I thought it was. The last several wakes
have not had the problem. When it happens again, I'll take your advice here.
Cheers, -Dave
--
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/b1bbf66e-fe4d-401d-a0a2-9fb59041d42e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
