On Wednesday, April 19, 2017 at 12:52:26 PM UTC-4, Reg Tiangha wrote: > On 04/19/2017 10:44 AM, Andrew David Wong wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > On 2017-04-19 09:40, Andrew David Wong wrote: > >> On 2017-04-18 21:11, Reg Tiangha wrote: > >>> On 04/18/2017 10:05 PM, cooloutac wrote: > >>>> Just started today dunno what the heck is up with that. In a > >>>> bunch of my appvms. It wasn't the dom0 update that error ed my > >>>> vms this issue was happening right before that. My Mother had > >>>> told me she had tried to update dom0, or thought she did > >>>> already, but apparently it didn't update. I bet it errored or > >>>> something. She said she had no freezing at all in a few vms > >>>> and updated right before she got off. So I'm thinking it > >>>> started after that failed dom0 update. > >>>> > >>>> But I also had noticed a week prior that chrome was not > >>>> showing, for example, the live chat popup button on > >>>> amazon.com. with no extensions nothing. ah no they probably > >>>> changed their chat to allow some non https connection or > >>>> something I bet. and in the default disposable I use with > >>>> firefox that is not the case. sorry fro the stream of > >>>> consciousness. > >>>> > >>>> Regardless, I'm still using firefox for right now cause the > >>>> freezing in the suspect vms has not happened with firefox for > >>>> some reason. Over the years I always go back and forth to > >>>> whichever one is less abused for the current time being. > >>>> > >>>> But I'm so paranoid right now I'm gonna wipe the entire system. > >>>> Actually even keepassx vault froze on me... I hope its just a > >>>> hardware failure, fedora is good about monitoring hdd > >>>> though...but yikes. > >>>> > >>>> anybody have any encouraging words for me? lol. > >>>> > >>> No encouraging words, but I've noticed freezing today too. Not > >>> in Chrome, but in things like nautilus and gnome-terminal. It's > >>> sporadic, though and I haven't nailed anything down yet except it > >>> was something in the latest batch of stable updates. > >>> My coldkernel VMs won't boot either, and it's very similar to > >>> these threads (ErrorHandler: BadAccess (attempt to access private > >>> resource denied), but they'll boot properly with a dom0 vm > >>> kernel): > >>> grsecurity kernel 4.9.20 not working - Qubes ErrorHandler: > >>> BadAccess MIT-SHM > >>> https://groups.google.com/forum/#!topic/qubes-users/2X8wi5XebJc > >> > >>> [bug] qubes-guid crashes when putting debian-9 VM in true XFCE > >>> fullscreen > >>> https://groups.google.com/forum/#!topic/qubes-users/d0lsqBbDYc0 > >> > >>> Unsolicited feedback on qubes-issue #2455 > >>> https://groups.google.com/forum/#!topic/qubes-users/NSZEZD_k7KE > > I believe this bug is different from the ones described in these other > > three threads. > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > -----BEGIN PGP SIGNATURE----- > > > > iQIcBAEBCgAGBQJY95PeAAoJENtN07w5UDAwY/EP/RxqBGLMxT1vFjLx+bF3ES1E > > Pz+0odzJbVwj3A2Ww9AXPIERhGj74tGmZE2DS7iyxgcYlSvrWAww+M6SdgAZmDR2 > > DSptZeVKtcbRlmNb6WMkBil8MFwL2PlVzNLlAOj0emOKMTIenR+56/H69XUA0FNF > > R3gRdGgD/rJVI0/0jwrupuI1ZGjt3yRmurMxXMSvlFPcfJJypemk7cTm1HHDi+Or > > Kl1OGE9b71ang3Ege4SQrn0lH5d8mX3b+SkjlkebuUXXhJE/Q6RieftFqpv9fgwI > > LkzVadTf/xBxTH9DezOwuGP4AKci+Qdz6TLaHC+Am4c4yG/kaNnqXYVnWCSZ2FEc > > +ZXchiSFxr0M+yCK6rnwEa4n/D5K2/ZznjsQNcm35W5+aHDKNDHye8sLFG65G0Jt > > /rMvQ+d3vlW3gghVTc+NeWRu1/yGHi4Jm5Btv6Wb26W8e1EURzVGUcsKXPKyToAD > > B42j1sXv9TktfwOGzLynnKC9QEbzUsmX5eVid4bJH/U/e8aC48k5gUmNnwxHdMyH > > L/avwmybgXzDozdj2qPj4PaIWRjY8qGugsgb35nQD213YPbySNSwTfeGpTH43W+/ > > 4yy6LFTn1+WBVQhsbq0u3zIBAenyseJzTrwRHygMg8iPQPR3L3ijl99vEx0K23zr > > oFhqe9T3z+a2CwCdRQJI > > =Zbw4 > > -----END PGP SIGNATURE----- > > > Yeah, it's probably a different bug. > > Andrew, what's your hardware configuration? Specifically, RAM and > whether or not you're running on an SSD or a hard drive? > > I'm still trying to resolve some of my other issues that I'm > experiencing because of the update, but I'm noticing a lot more RAM > usage (including a lot of swap being used; 600MB in dom0 right now on my > laptop when in the past, it's usually held at 0MB, but my hard drive > light isn't on when the freezing occurs and there doesn't seem to be > anything abnormal when running top on the VM) and I'm wondering if the > 'freezing' is related, and potentially more noticeable to those who have > a lot of swap in use. Don't have time to really delve into it at the > moment though, so it's also anecdotal. > > I have noticed though that if I launch xterm or any other app on the VM > using Qubes Manager, that as soon as that new window pops up, everything > becomes responsive again. Also, that when the freezes occur, I sometimes > can't connect to the VM with virsh until it becomes unstuck again.
yes I think I noticed this too. When I got the freeze instead of shutting down vm I launched the terminal from it. was going to kill process and then realized it was working again. The machine this is happening on has 500gb ssd and 16gb ram, iommu on, intel gpu, intel 5 cpu. Another machine doesn't have this issue, and it has no iommu, no ssd, and old amd cpu, older nvidia gpu. This machine also never got the missing kernel bug. And has had no restored backup vms. Legacy boot on both. In fact I wonder if the freezing is happening on those vms that were affected. Because it happened when updating my fedora-24 clone from the qubes-manager gui. When I went to hit enter to close the vm, window was frozen so I manually shut it down. This hasn't happened on any of the other templates, and in fact, this was the only template that had a missing kernel problem. Could it be related? Never had any freezing before the day of dom0 update. none of my untrusted vms were affected with the dom0 update bug. I will start using chrome in them and see if it freezes. -- 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/f15a5526-1bf5-4e02-9e69-54ed1b82cb8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
