Edit: I did some research and meant to edit this before I posted. Watchdog 
actually appears to be an NMI and I found one thread about someone 
increasing the threshold? I had thought this was a response error to when I 
tried to disable the firewall/net VM but actually might be an error of its 
own. Are my resources being hogged up somehow? I have made it past user 
account login twice now, both times it will let me move the mouse for a bit 
and then when i try to click on anything the whole system freezes. 

If it's any indicator, I can load debian just fine so I don't think its 
anything hardware related. I must have tweaked with a setting in qubes I 
wasn't supposed to. 


On Monday, January 11, 2021 at 11:07:58 AM UTC TheCrispyToast wrote:

> Was able to disable whonix from startup, that didn't seem to do anything. 
> That's assuming I was supposed to restart after that and try to boot as 
> normal right? Is there a way to then exit terminal and continue signing in 
> with GUI?
>
> I tried to disable firewall/net VM and then got a watchdog error, i'd 
> imagine this is a security feature of qubes? 
> Sorry it's a photo and not text! 
> [image: IMG_3283.JPG]
>
> On Sunday, January 10, 2021 at 7:13:16 PM UTC awokd wrote:
>
>> TheCrispyToast:
>> > On Sunday, January 10, 2021 at 12:18:54 AM UTC awokd wrote:
>> > 
>> >> This seems like it could be a hardware or disk corruption issue. Try
>> >> hitting ctrl-alt-F5 to switch to a text terminal when you are at the
>> >> grey screen. Should hopefully be able to login there and pull logs. If
>> >> your disk was close to filling up, that could point more towards drive
>> >> corruption.
>> >>
>> >> My disk was definitley not close to filling up, but it may have been 
>> one
>> > of the VM partitions that was close to filling up. I have managed to get
>> > into the dom0 terminal upon bootup. Excuse my ignorance, but could you
>> > asssit with the proper commands for pulling logs and/or turning certain 
>> VMs
>> > off from startup? I think itd be better to start a boot with only dom0
>> > running. As I said before, sometimes it will let me even get logged in 
>> and
>> > then once whonix appears to start the whole system freezes.
>> > 
>> "sudo journalctl -b" might be helpful. If you can get into dom0, 
>> "qvm-prefs sys-whonix autostart false" will do that. Might also set 
>> sys-firewall and sys-net autostart to false.
>>
>> -- 
>> - don't top post
>> Mailing list etiquette:
>> - trim quoted reply to only relevant portions
>> - when possible, copy and paste text instead of screenshots
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0d8e52be-857d-4645-a5fc-79615039bcd0n%40googlegroups.com.

Reply via email to