Drew White: > On Monday, 21 November 2016 14:31:10 UTC+11, Andrew wrote: >> Drew White: >>> Still getting Dom0 crash / parts not responding. >>> >>> Primarily it's a guest that causes the whole of Dom0 to slow and stop. >>> >>> I have yet to find out what the root cause it, but it's still locking >>> things up. >>> >>> Sometimes after running a guest for a few hours will cause the system to >>> start having a coronary. >>> >>> I'm not doing anything super intensive, only programming. >>> >>> >>> IF I run ANY guest with Firefox, and have it running for a couple of days, >>> I come back from the weekend or sometimes even 1 night, and the PC is >>> locked up solid. At that point, not even the logging in Dom0 is working. >>> Sometimes, as I have said before, the logging in Dom0 is still running and >>> working but I can't get access to the machine any more and have to >>> physically power it down to then start it up again. Which causes an fsck to >>> be run because the filesystem wasn't cleanly unmounted. >>> >>> Any help on these bugs would be greatly appreciated. >>> Mainly I find the issue is with FireFox running. I've found other guests >>> running for days on end don't cause the system to lock up. >>> >>> If information for the developers is required, I would be happy to email >>> you the details, logs, and specs. >>> >> >> Drew, >> >> Is there any chance you are using a recent (Braswell or maybe Broadwell >> or similar) low-end Intel CPU? If so, your problem may actually be due >> to a bug in the Linux kernel. >> >> For example, I recently acquired just such a system and experienced >> seemingly random total system freezes with Qubes 3.2 ranging anywhere >> from 5m to 12h after boot. What fixed the problem, or worked around it, >> was: >> -use the 4.8.* kernel in the unstable repository >> -change the "i915.preliminary_hw_support=1" in the kernel boot command >> line to "intel_idle.max_cstate=1", which limits the CPU to drawing the >> maximum power :-\ >> -(may be unnecessary) disabling DRI in my dom0 Xorg.conf (I had to >> create a new file): >> -"NoAccel" "true" >> -"DRI" "false" >> >> Let me know if you're affected by the same bug. >> >> Cheers, >> Andrew > > I have no second CPU in the system at the moment. Not the extra RAM. That' > shwy it says there is a second, but there is none. > > > I have no Xorg.conf anywhere on my system to alter or move and create a new. > > > So you did EVERYTHING there at once? > Or did you do one thing, check it, then try a different thing, check it, then > when they didn't work on their own you tried them in combination? >
It doesn't look like this is the same bug, but... > I have no Xorg.conf anywhere on my system to alter or move and create a new. Yes, as I said, I had to create one. > So you did EVERYTHING there at once? > Or did you do one thing, check it, then try a different thing, check it, then when they didn't work on their own you tried them in combination? Originally I tried them piecemeal, but this is the only combination I have found that works. I have not tried without the Xorg.conf modifications but with the other two, though. Andrew -- 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 [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-users/d8711cc3-53b2-cee8-16b0-225b1f8823b8%40riseup.net. For more options, visit https://groups.google.com/d/optout.
