'Evastar' via qubes-users:
Again, what to do now? Never update or try to wait for month and then update?
Short term, continue applying template updates as usual. If you run
"sudo qubes-dom0-update", you can check for updates, but make sure to
choose not to apply them with N. Wait for the
> Did you notice any other errors around the soft lockup? Try searching
> for them; it would be good to figure out what's causing the lockup, but
> it can be hard to do.
Only one error: all system very unresponsive, :) And as I'm already note 100%
cpu usage by some processes. Also I saw strange
evas...@firemail.cc:
By the way, I got the idea and switched to other tty before login to the
system where Qubes Manager and other tasks start. It give me some time
to use the system. And I found the bug at std error output:
!
wachdog: BUG: soft lockup - CPU#3 stuck for 23s!
By the way, I got the idea and switched to other tty before login to the
system where Qubes Manager and other tasks start. It give me some time
to use the system. And I found the bug at std error output:
!
wachdog: BUG: soft lockup - CPU#3 stuck for 23s! [1.xvda-1:4325]
kernel
Maybe it's possible to return to this emergency mode? System freeze
until Qubes Manager start. It can freeze at 45% or at 91% or at any
point. I see high cpu usage. It freeze because of this. I shutdown it
before at this point and filesystem corrupt. Need the way to access
/boot/efi without
Filesystem corruption is a different issue. In the emergency console,
"fsck /dev/mapper/qubes_dom0-root". Answer y to everything it asks,
then "reboot". If that lets you get back into Qubes, DO NOT DO
ANYTHING ELSE UNTIL RUNNING A FULL BACKUP. Then try editing xen.cfg as
previously described.
evas...@firemail.cc:
On 2019-05-26 15:57, 'awokd' via qubes-users wrote:
Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg
it request to run fsch or e2fsck. What I must run first and how?
Then if filesystem will be fixed, how to mount boot to change it? I
guess this emergency console can help
On 2019-05-26 15:57, 'awokd' via qubes-users wrote:
Log(url): i DOT imgur DOT com SLASH Z8GbXLJ.jpg
it request to run fsch or e2fsck. What I must run first and how?
Then if filesystem will be fixed, how to mount boot to change it? I
guess this emergency console can help me, because dom0
On 2019-05-26 16:32, 'awokd' via qubes-users wrote:
Yes, but be aware that it may mount the boot directory you're looking
to edit underneath a different location, so watch the messages when
you do.
What is correct "mount" command to do this?
And to fix filesystem then...
--
You received
evas...@firemail.cc:
On 2019-05-26 15:57, awokd wrote:
First thing to try is to rollback the dom0 kernel update. If you're
using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change
the default kernel line at the top to point to the previous version
number. Save and reboot. If you're
On 2019-05-26 15:57, awokd wrote:
First thing to try is to rollback the dom0 kernel update. If you're
using UEFI boot, "sudo nano /boot/efi/EFI/qubes/xen.cfg" and change
the default kernel line at the top to point to the previous version
number. Save and reboot. If you're not sure how to do
evas...@firemail.cc:
Okey... keep calm...
Time to time I can use dom0 console without troubles (sudo
qubes-dom0-update also still work by no fix still come :( )
I guess now need to somehow change new kernel to old one?
How to do this? I guess I'm at UEFI mode (new notebook)
1) boot from some
Okey... keep calm...
Time to time I can use dom0 console without troubles (sudo
qubes-dom0-update also still work by no fix still come :( )
I guess now need to somehow change new kernel to old one?
How to do this? I guess I'm at UEFI mode (new notebook)
1) boot from some qubes installed usb
13 matches
Mail list logo
