qubes 4, system freezes

[none]

Hello, I have intel speedstep disabled, and upgraded fans at "full
speed" and a kabylake CPU at 41C in the UEFI/Bios,  I have noted.


But, over the last month I've had to hard reboot the system 5+ times 
because of system freezes, looking at journalctl  I do see:


dom0 systemd-modules-load(219) failed to find module 'xen-acpi-processor'

in Red  Font


and

dom0 kernel setting dangerous option  alpha_support tainting kernel


Not in red font


since the freezes are random bit difficult to track down,  I just
yesterday get a dom0 update, but the freezing had been starting before
that .......


In the past  I never had system freezes on 3.2, nor on 4.x  at all .... 
bit disconcerting


anyone else with this ?

[none]

More freezing , like 3-5 times today, forcing me to hard reboot:
few other things in journalctl

pciback driver tried to write to a read only config space field at
offset xcb2
1) see permissive attribute in sysfs
2) report to xen-devel with your device

xen_pciback cannot enable memory-write-invalidate (-22)

and some memory balance complaints,  there is 32Gb  in the system ;
though I do load up a lot of VMs


last freeze was with SpeedStep  enabled, so it's  both enabled or not
enabled  both freeze the system.

very hard to live with this !

[799]

Hello,

none <yre...@riseup.net> schrieb am Mi., 20. Juni 2018, 04:12:

> In the past  I never had system freezes on 3.2, nor on 4.x  at all
> ....  bit disconcerting

Have you mentioned already what hardware you are running?

Please check against Qubes HCL (Hardware Compatibility List).

As you wrote "in the past I never had system freezes" ... What has been changed from that past to today?

If I run into "strange" problems I would always make sure that my RAM is working.

Swap RAM modules, take some modules out and look if the problems is still the there.

You can also run a tool to stress test the RAM.

What happens if you start no AppVM and just leave dom0 running. Maybe generating some cpu load there?

[799]

[Drew White]

In your VMs, set them to static RAM, not balanced.

After that, make sure you start them up and shut them down.

If that does not resolve, for Dom0, increase the RAM available to it by 512MB.
Then after that decrease it again if able. Test with lower RAM.

This can resolve your memory writing issue because it may have a cached version on the HDD in swap that can't read to write to physical. (if you have HDD SWAP on.)
I don't have HDD SWAP turned on. I used to have freezing, until I changed the default RAM that was assigned to QUBES and stopped using the Qubes Manager that caused a lot of the issues FOR ME with RAM because of it's huge requirements.

[cooloutac]

what cpu specs?

only have had freezing when after pc was in sleep mode. turn that off if using it. also try reinstall if all else fails make sure to do integrity check.

[cooloutac]

what about temps also run a memory check.

[none]

ya that was a really bad idea, I changed 10 AppVMs to  *not memory
balance relaunching the  AppVms, none of the  webbrowser  would load a
page, had to go manually undo it all again,

I did note that sys-net gives a warning  about using memory balancing,

so maybe sys-net, firewall, usb  should not use memory balancing

but and vpn proxy qubes  should ?

I don't really know what the defaults were, but   maybe it was just the
vpn proxys that wanted it engaged, when it wasn't .....

last few days , no freezing, after having had 4 or 5 in 2 days,  so
goes  qubes 4

[john]

I keep trying to update via widget it finishes but the wheel - cogwheel
doesn't disappear, anyone else seeing this behaviour in 4.0.2

debians updated fine and the gear wheel disappears just not fedora, 
doing it via qubes manager just says nothing to update