Current problems with Qubes 4.1

[unman]

There are numerous issues being raised about the current performance of
Qubes - graphical glitches, system hangs, random reboots, unstable
service qubes, etc. Some of these are notable when qubes are starting or
shutting down, (which may explain why some people link this to running
updates.) You can see this in numerous Forum posts and on GitHub.

I think , as djb posted today, this is particularly obvious when
transitioning from 4.0 to current 4.1. (When one of our supporters finds
this, I think we are in trouble.)
I posted about some of the issues in the testing section of Forum, but
no one else commented. I was reporting there issues that affected at
least 5 users, two of them using certified hardware.
Again, if users of certified hardware encounter these problems, we are
in trouble.

For my part I can probably date these issues back to some time in the
past 6 weeks. Prior to that my Lenovos were solid - I was amazed at the
troubles that some users reported, and my support calls were limited.
This isn't the case now.

It could be that these issues only affect older hardware - I don't think
so. Or perhaps the current system stresses components so that some
failing elements show otherwise hidden flaws.

Whatever the case, there's a major issue that needs to be addressed.
I thought of rolling back some systems to see if I can identify a time
before the flood, and then bisect to find which packages might be
responsible.
Would this make sense?
Would it be worthwhile?
Are there any thoughts on the current situation?
What would be the best way forward, and how can we contribute to the
effort?

Dealing with this issue should take precedence over all other development
work. Identifying the root cause(s) should be the highest priority.

unman

[Andrew Clausen]

Hi all,

Unman, can you please post a link where people should send information?

I have also had trouble on my Lenovo X230 over the last few weeks, using 4.1.  I never had any trouble before then, and I've been using Qubes on this computer every day for a few years.   Sometimes my computer gets very slow -- about 10 times slower, even though I can't see any processes actually doing anything.  The problem usually appears when I boot up after running out of battery while sleeping (which happens fairly often -- lousy battery!).  The problem usually goes away when I reboot, although sometimes I need to reboot twice.  I haven't had time to investigate further (e.g. logs).  But restarting all VMs doesn't help.  It's only a minor nuisance, so I didn't report it before.  Please tell me if there's any useful information I can send you.

Cheers,

Andrew

--
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 qubes-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/Y0gnQ01atBxyBhSo%40thirdeyesecurity.org.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Are those by any chance using kernel-latest? There are numerous issues
with 5.19.x kernel, but I believe the default (5.15.x) isn't affected.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmNIjOMACgkQ24/THMrX
1yyIfAgAgf4A2/nw9Bf7wMZ5pjua4S+Fs5fsI+Tz8T7K9aeYmqkZGL8711m2suB2
4Z3d63FHE3pROc6Re4Xj9buDs0omgkyPck0GiB3EtyGmLyvq4f7oDGL9C4Z9VK+a
LU1x6MG0F8twNR8nn2LqR7VVw+MWXqbXb1HF44X2gRbkVscQk6riu3vq5zrxuWPU
MRKRtKN7S7BkwqefVvHSSjsWSMSpuSfXzUf3PyRXP462qBnpvDs84XhsRFHI0dEl
vDyfkWMhs4Oi/5eT9oULMEljRIXfriGOWIwCevMVEuhWXqV/iMgiv0m/12EKLfrZ
+CypSQOIx5Ksfa85zAO25DGiVJXXDw==
=KDu7
-----END PGP SIGNATURE-----

[unman]

> Are those by any chance using kernel-latest? There are numerous issues
> with 5.19.x kernel, but I believe the default (5.15.x) isn't affected.
>

Unfortunately not.
I had thought that at least one issue (inability to link to vif
interfaces after sleep) was kernel related, but I was wrong.
I also see from the Forum that other users report these issues with stock
kernel.