-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, Nov 14, 2016 at 02:02:31AM -0500, Jean-Philippe Ouellet wrote: > tl;dr - kernel-4.8.7-11 +1 from me! > > On Thu, Oct 13, 2016 at 1:20 AM, Jean-Philippe Ouellet <j...@vt.edu> wrote: > > The laptop fails to resume about once a day and requires a > > hold-the-power-button reset > > I'm hoping that newer kernels fix this (dom0 currently on 4.4.14-11), > > Since last Friday (~3 days) I've been on kernel-4.8.7-11 from > qubes-dom0-testing with only a single full-fan hang while attempting > to resume (not the usual failure mode, and *much* less frequent), as > opposed to the several-per-day just-dead hangs I was consistently > experiencing before, so... progress! :) > > Wireless[1] now sometimes fails to come back after resume with this in > the dmesg: > Freezing user space processes ... (elapsed 0.001 seconds) done. > Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. > PM: freeze of devices complete after 0.090 msecs > suspending xenstore... > PM: late freeze of devices complete after 0.053 msecs > PM: noirq freeze of devices complete after 21.827 msecs > xen:grant_table: Grant tables using version 1 layout > PM: noirq thaw of devices complete after 0.648 msecs > PM: early thaw of devices complete after 0.089 msecs > PM: thaw of devices complete after 0.453 msecs > Restarting tasks ... done. > IPv6: ADDRCONF(NETDEV_UP): wlp0s0: link is not ready > iwlwifi 0000:00:00.0: L1 Enabled - LTR Enabled > iwlwifi 0000:00:00.0: L1 Enabled - LTR Enabled > iwlwifi 0000:00:00.0: Failed to load firmware chunk! > iwlwifi 0000:00:00.0: Could not load the [0] uCode section > iwlwifi 0000:00:00.0: Failed to start INIT ucode: -110 > iwlwifi 0000:00:00.0: Failed to run INIT ucode: -110 > iwlwifi 0000:00:00.0: L1 Enabled - LTR Enabled > iwlwifi 0000:00:00.0: L1 Enabled - LTR Enabled > iwlwifi 0000:00:00.0: Failed to load firmware chunk! > iwlwifi 0000:00:00.0: Could not load the [0] uCode section > iwlwifi 0000:00:00.0: Failed to start INIT ucode: -110 > iwlwifi 0000:00:00.0: Failed to run INIT ucode: -110 > .... > > Rebooting sys-net (so far) reliably makes it work again (and man... I > really wish there were some way to restart it without shutting > everything else down first - it'd be awesome if sys-firewall would > gracefully re-establish whatever it needs. idk what that would be > exactly, or what the challenges are - i haven't looked under the hood > of qubes networking yet).
You can temporarily set sys-firewall netvm to none. This will allow you to shutdown/restart sys-net without consequences. Remember to change sys-firewall netvm back to sys-net afterwards. > Curiously, the wireless didn't hang while i had the 4.4 kernel in > dom0, and now it hangs with 4.8 in dom0 and either 4.4 OR 4.8 in > sys-net. This does not make sense to me, but it is indeed what I have > observed. Perhaps it was also failing before and I just never noticed > because the whole machine would hang so often. I'd guess the later... When it hangs, does the suspend before takes usual not-so-long time, or is significantly longer? > [1]: lspci => 00:00.0 Network controller: Intel Corporation Wireless > 8260 (rev 3a) - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJYKimzAAoJENuP0xzK19csTdMH/iSFWVihOXWVvpaY1743SFYR ODmahDetFwdgPdcRCun8190uP0c0MsE8CCqZOT5EMqnGD3EdVSFYx/zU3yG+Yi6b 3dY1kBcL0jS5ANk1i8DaYis/U5USxHmWHJ4pWkIqiC/u3ErruyUW80hXaHF73QDf 9agjnjSudidbbD7p/3J3BqD7cW9APUEoqPjvTgsrrdEOvc3tKFK6yfYE3WktGhee rbnImBhsjwWz1nR3YsS5tCwmqMBCRfgOqo5sZc5K1lbzrc0d1/ZNKaUGf8lQXE9X S7LYhVBzMMLZAfo13Y/bPYupmOdXqxAqMU6O0KOZ85QQzyvYUFNEf9RwYF+hbsc= =Fo4R -----END PGP SIGNATURE----- -- 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/20161114211635.GA3417%40mail-itl. For more options, visit https://groups.google.com/d/optout.
