-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sun, Jan 28, 2018 at 10:44:37AM +0200, Ivan Mitev wrote:
> On 01/28/18 02:16, Marek Marczykowski-Górecki wrote:
> > On Thu, Jan 25, 2018 at 02:21:35PM +0200, Ivan Mitev wrote:
> > > On 01/25/18 13:27, Marek Marczykowski-Górecki wrote:
> > > > So, the question is why sys-net crashes. Take a look at
> > > > /var/log/xen/console/guest-sys-net.log and
> > > > /var/log/qubes/vm-sys-net.log.
> > >
> > > /var/log/qubes/vm-sys-net.log didn't have any helpful info, but I see some
> > > panic logs in guest-sys-net.log ; I'll try to debug it when time allows.
> >
> > Can you post this panic messages? I think I've hit exactly the same
> > problem once but mine logs didn't have any details on sys-net crash
> > (just cut during its startup). And I can't reproduce it again...
>
> [logs sent to your email address but feel free to publish them; the panic
> message I saw was in guest-sys-net-dm.log]
Warning at arch/x86/xen/apic.c in sys-net-dm is safe to ignore. It's a
side effect of our memory optimizations there (aggressively disabling
not needed kernel features).
Other than that, I see some hardware initialization problems related to
Intel Wifi interface:
[ 6.028035] WARNING: CPU: 1 PID: 567 at
/home/user/rpmbuild/BUILD/kernel-4.9.56/linux-4.9.56/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1860
iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi]
[ 6.028035] Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)
That might result in hanging sys-net during startup, and consequently
startup timeout. According to the log qrexec was started before that
("Started Qubes remote exec agent" message), so it isn't exactly the
timeout defined by qrexec_timeout property. But maybe about something
else, like connecting network to sys-firewall. Or a crash related to
above, but not logged for some reason...
> After your reply to my original post I rebooted to see if I could notice the
> timing you described (sys-net starting, then sys-firewall, and then sys-net
> crashing). But go figure, while I had this sys-net startup problem *each
> time* since installing 4.0rc3, this time sys-net started successfully and
> since then I haven't been able to reproduce the problem with the past 10+
> reboots.
Ok, so keep trying to notice that timing, this will ensure it will
keep working ;)
> The *only* thing I remember that could be related to the problem was
> updating sys-net's template a bit before my post (dnf update in fedora-26).
> For info here's a list of the updated rpms on Jan 25:
(...)
I don't see anything that could directly affect startup crash...
- --
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-----
iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpt3DgACgkQ24/THMrX
1ywIdQgAi/SKEQzSDQ+xv8K1yVDyv3fDeqyGKq/M1XNo133d3vNKg3KCm8+3OKWd
jXcYcUIxIEZCD1T0rmfl2eDXn+Gk4rwqFdQZBstuWwzGJoG+JNOU4M++ORgDlxzc
3T3wMrEDlAKv9nop6+R6zecNPxtEIqwR7Qa7Ddk4ApGcVB/kHjwtdNef6w3MTmir
KUV5ilqCBAZcUk8Jxh33wN+HNB5g6Z4b0/WYU9Bio/mpPW2LDI0W2gqeGjivjPjL
f5pLgpoJvOvcmdjhK+0NJgOksHvr+dS4o+iht6S6gKTvAplKymmAEaiZjR3Y5j6K
VQAMcO+ZlhJXyQxnzmx4/NxfRQ5shw==
=hcjO
-----END PGP SIGNATURE-----
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" 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-devel/20180128142040.GK2653%40mail-itl.
For more options, visit https://groups.google.com/d/optout.
