Obviously something went wrong with the kernel update, because with
Kernel 4.19.100 I get a kernel panic error (failed to mount / ), but
Kernel 4.19.94 works fine. In qubes, how can I reinstall the new kernel?
thanks
--
You received this message because you are subscribed to the Google Groups
after last update my Dell runs in a kernel panic -- reboot spiral. I
retype 4 important lines from a "photo screenshot" :
Initramfs unpacking failed: read error
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
CPU: 3 PID: 1 Comm: swapper/0 Not tainted
On Mon, Oct 7, 2019 at 3:39 PM Charles Peters wrote:
>
>
> I installed Qubes a couple of weeks ago and yesterdays dom0 update causes a
> kernel panic. Looking through grub it appears the new kernel is lacking the
> initramfs image (only the older kernel entries have the gr
Basically my issue is that I am getting a kernel panic when I try installing
qubes-os on my laptop both in UEFI and legacy mode.
The kernel panic can be seen here: https://imagebin.ca/v/3pPwokGAMAVB and I
sadly can't provide a hastebin dump since I have no way to log the error in
text for
On Thursday, 25 January 2018 13:36:18 UTC, WolfSkin wrote:
> Basically my issue is that I am getting a kernel panic when I try installing
> qubes-os on my laptop both in UEFI and legacy mode.
> The kernel panic can be seen here: https://imagebin.ca/v/3pPwokGAMAVB and I
> sadly can
> Have you tried taking out iommu=no-igfx (in both places) and/or
i915.alpha_support=1?
I have just tried this. No change. Using the serial console still
results in the same kernel panic. Without the serial console, there is
no output from Dom0.
I also was recommend pci=nocrs in the cons
> Have you tried taking out iommu=no-igfx (in both places) and/or
> i915.alpha_support=1?
I have just tried this. No change. Using the serial console still
results in the same kernel panic. Without the serial console, there is
no output from Dom0.
I also was recommend pci=nocrs in the c
Good Morning,
Is anyone else getting a kernel panic at "amdgpu_debugfs_init" booting
the new 5.7.4-1 kernel from current-testing with an AMD GPU?
I'm not particularly worried about it because the GPU didn't work with
4.0 anyway and the bug doesn't affect 4.1. I'd li
[email protected]:
> Obviously something went wrong with the kernel update, because with
> Kernel 4.19.100 I get a kernel panic error (failed to mount / ), but
> Kernel 4.19.94 works fine. In qubes, how can I reinstall the new kernel?
>
> thanks
>
Usually it's "sud
I installed Qubes a couple of weeks ago and yesterdays dom0 update causes a
kernel panic. Looking through grub it appears the new kernel is lacking
the initramfs image (only the older kernel entries have the grub line
"module --nounzip /initramfs-4.19.56-1img).Any suggestio
Den torsdag den 25. januar 2018 kl. 14.40.14 UTC+1 skrev WolfSkin:
> On Thursday, 25 January 2018 13:36:18 UTC, WolfSkin wrote:
> > Basically my issue is that I am getting a kernel panic when I try
> > installing qubes-os on my laptop both in UEFI and legacy mode.
> > Th
got this error.
[4.398471] - Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block (0.0)
[4.398508] CPU: 0 PID: 1 Comm: swapper/0Not tainted
4.4.38-11.pvops.qubes.x86_61 #1
[4.398571] 73d2c1cb 8801583fbda8 813b1a93
[4.398667
I have several dom0 kernels installed (on a Dell XPS13) but only one works
fine:
5.11.8-1.fc25.qubes.x86_64 -> boot loop
5.11.4-1.fc25.qubes.x86_64 -> boot loop
5.10.8-1.qubes.x86_64 -> kernel panic
5.4.107-1.fc25.qubes.x86_64 -> does not wake up after suspend
5.4.98-1.fc25.
I have been attempting to get Qubes installed on my Metabox Prime-V
laptop, which has resulted in the following kernel panic on each boot.
https://user-images.githubusercontent.com/43260698/67632046-025ddf00-f896-11e9-9012-e6813789a3f5.jpg
This kernel panic seems to be caused by the interaction
Hello
I am trying to install Qubes on a Lenovo Yoga 300. The USB stick boots to the
initial screen, and after choosing install, I get a kernel panic screen. Any
ideas why this is happening and how to address it?
Thanks
--
You received this message because you are subscribed to the Google
Awokd,
One of the machines is a B117-M and the other is a B116-M. The previous boot
debug is from the B116-M.
1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and
B117-M respectively - still getting the KERNEL PANIC on both machines.
2) Tried disabling all non essential
1.23 and 1.24 on the B116-M and
>> B117-M respectively - still getting the KERNEL PANIC on both machines.
>>
>> 2) Tried disabling all non essential peripherals in the bios (Audio, Wifi,
>> LAN, Webcam, SDcard reader - leaving only the USB ports enabled), but
>> withou
Hello,
I have tried to boot Fedora 29 Silverblue in a HVM from the official ISO. I
have noticed that there is some kernel panic before the HVM shuts down. The
problem is that I cannot read it. Is there any way to read it, e.g., by
disabling the automatic reboot somehow?
Regards,
Vít Šesták
On Fri, March 2, 2018 8:22 am, [email protected] wrote:
> Hello,
>
>
> Unfortunately after the last update of Qubes 4.0 I have a kernel
> panic: "unable to mount root fa on unknown block" and would appreciate
> if somebody here could give me a tip.
I think there is a
says kernel
panic – not syncing: Fatal exception.
Any help would be appreciated. Might just reinstall without a disk password and
see what happens
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
Jarrah Gosbell:
> I have been attempting to get Qubes installed on my Metabox Prime-V
> laptop, which has resulted in the following kernel panic on each boot.
> [qubes-verbose]
> options=console=vga efi=no-rs iommu=no-igfx loglvl=all
> dom0_mem=min:1024M dom0_mem=max:4096M ucode=s
Hi,
Error message :
[3.680649] Call Trace:
[3.680707] dump_stack+0x5c/0x85
[3.680764] panic+0xe4/0x252
[3.681184] mount_block_root+0x35b/0x52c
[3.681601] ? do_early_param+0x16e/0x16e
[3.682018] prepare_namespace+0x278/0x2d5
[3.682434] ? do_early_param+0x16e/0x16e
[3.682851] kernel_init_freeable
.
At 13:16 29/08/2019, Guest wrote:
>Awokd,
>
>One of the machines is a B117-M and the other is a B116-M. The previous boot
>debug is from the B116-M.
>
>1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and
>B117-M respectively - still getting the
s and no, there was
the same kernel panic. So no betterment.
>Wouldn't bother with older. Kernel 5.something is available in the
>testing repo. Easiest way I can think to get it would be to pull the
>laptop hard drive, install Qubes on it from a different machine, update
>kernel,
On 1/29/21 4:35 PM, Jinoh Kang wrote:
> You can collect panic and oops logs with a kernel that has
> CONFIG_EFI_VARS_PSTORE enabled. If you don't already have one, you may
> build qubes-linux-kernel via qubes-builder with the following line
> added
[email protected] wrote on 1/12/19 8:43 PM:
Hi,
Error message :
[3.680649] Call Trace:
[3.680707] dump_stack+0x5c/0x85
[3.680764] panic+0xe4/0x252
[3.681184] mount_block_root+0x35b/0x52c
[3.681601] ? do_early_param+0x16e/0x16e
[3.682018] prepare_namespace+0x278/0x2d5
[3.682434
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Mar 17, 2019 at 04:02:31PM -0700, Vít Šesták wrote:
> Hello,
> I have tried to boot Fedora 29 Silverblue in a HVM from the official ISO. I
> have noticed that there is some kernel panic before the HVM shuts down. The
> probl
Hello,
Unfortunately after the last update of Qubes 4.0 I have a kernel
panic: "unable to mount root fa on unknown block" and would appreciate
if somebody here could give me a tip.
I installed Qubes 4.0-RC1 and since then been only updating.
After the next-to-last update I was n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, May 20, 2019 at 11:27:32AM +1000, haaber wrote:
> after last update my Dell runs in a kernel panic -- reboot spiral. I
> retype 4 important lines from a "photo screenshot" :
>
> Initramfs unpacking failed: read error
>
> From: Frédéric Pierret
> Sent: Wed Jul 22 20:33:36 CEST 2020
> To: Chempes Amt , donoban
> Cc:
> Subject: Re: [qubes-users] Stuck in kernel panic, cannot rescue my system
> with anaconda
>
>
>
>
> On 2020-
yes this was a typo.
it was simple as running grub2-mkconfig again to fix the issue
but thanks for the answer
Quoting awokd :
On Fri, March 2, 2018 8:22 am, [email protected] wrote:
Hello,
Unfortunately after the last update of Qubes 4.0 I have a kernel
panic: "unable to mount root
e updates. Took a while
> but all three was updated. Today I started to launch Qubes again and got this
> error.
>
> [4.398471] - Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block (0.0)
>
> [4.398508] CPU: 0 PID: 1 Comm: swapper/0Not tainted
>
Le samedi 12 janvier 2019 21:43:21 UTC+1, [email protected] a écrit :
> Hi,
>
> Error message :
>
> [3.680649] Call Trace:
> [3.680707] dump_stack+0x5c/0x85
> [3.680764] panic+0xe4/0x252
> [3.681184] mount_block_root+0x35b/0x52c
> [3.681601] ? do_early_pa
e the initramfs for versions up to and including
4.19.42 where about 23M, the 4.19.43 file is only 8.4M ! Is this maybe a
short write (disk full overlooked/ignored in update script??).
That would explain a kernel panic even better :)) Can I checksum
4.19.43 manually? Or should I reinstall it? Ber
audio completely, perhaps try the
>external monitor or blacklist suggestions in here:
>https://github.com/QubesOS/qubes-issues/issues/5247.
No option exists to disable HDMI Audio, or any VGA options for that matter in
the BIOS ;-/
Blacklisting the kernel module had no noticeable effect o
[email protected]:
> Hello,
>
> Unfortunately after the last update of Qubes 4.0 I have a kernel panic:
> "unable to mount root fa on unknown block" and would appreciate if
> somebody here could give me a tip.
>
> I installed Qubes 4.0-RC1 and since then been onl
Le samedi 12 janvier 2019 21:43:21 UTC+1, [email protected] a écrit :
> Hi,
>
> Error message :
>
> [3.680649] Call Trace:
> [3.680707] dump_stack+0x5c/0x85
> [3.680764] panic+0xe4/0x252
> [3.681184] mount_block_root+0x35b/0x52c
> [3.681601] ? do_early_pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 1/31/21 10:28 AM, donoban wrote:
> On 1/29/21 4:35 PM, Jinoh Kang wrote:
>> You can collect panic and oops logs with a kernel that has
>> CONFIG_EFI_VARS_PSTORE enabled. If you don't already have one, you may
>> bu
Le samedi 12 janvier 2019 21:43:21 UTC+1, [email protected] a écrit :
> Hi,
>
> Error message :
>
> [3.680649] Call Trace:
> [3.680707] dump_stack+0x5c/0x85
> [3.680764] panic+0xe4/0x252
> [3.681184] mount_block_root+0x35b/0x52c
> [3.681601] ? do_early_pa
Hello, I am currently locked out of my qubes system because of a "kernel panic"
error I encounter when I boot the system, after the grub screen. I don't really
know what to do.
The only thing I did before this to happen is to try to install AEM (without
success), it may be the
Hi,
Quite a bit of things went wrong - but most of them I was able to revert.
This one however, slaps me in the face and I can't see what the issue is.
> xc: panic: xc_dom_core.c:387: xc_dom_do_gunzip: inflate failed (rc=-5):
> Internal error
> xc: panic: xc_dom_bzima
Guest:
> Dear List,
>
> I have recently re-discovered Qubes and it is wonderful to see how far it has
> come in the past years and I thought it worth to giving it a try.
>
> Alas, a kernel panic on booting the installation media. I have tried all 3
> latest versions (4.
Le samedi 12 janvier 2019 21:43:21 UTC+1, [email protected] a écrit :
> Hi,
>
> Error message :
>
> [3.680649] Call Trace:
> [3.680707] dump_stack+0x5c/0x85
> [3.680764] panic+0xe4/0x252
> [3.681184] mount_block_root+0x35b/0x52c
> [3.681601] ? do_early_pa
On Thursday, January 25, 2018 at 2:36:18 PM UTC+1, WolfSkin wrote:
> Basically my issue is that I am getting a kernel panic when I try installing
> qubes-os on my laptop both in UEFI and legacy mode.
> The kernel panic can be seen here: https://imagebin.ca/v/3pPwokGAMAVB and I
>
ize Qubes, I have to copy manually the
xen.cfg and the xen.efi files at every kernel update (as here :
https://www.qubes-os.org/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing
).
The problem is that at last update I forgot to change the xen.efi file version
and that now I&#
[email protected] wrote on 1/12/19 10:31 PM:
Le samedi 12 janvier 2019 21:43:21 UTC+1, [email protected] a écrit :
Hi,
Error message :
[3.680649] Call Trace:
[3.680707] dump_stack+0x5c/0x85
[3.680764] panic+0xe4/0x252
[3.681184] mount_block_root+0x35b/0x52c
[3.681601] ? do_early_param
On Saturday, 21 April 2018 11:56:04 UTC+10, Manuel Amador (Rudd-O) wrote:
> I haven't had a system crash in months
> while using Qubes OS, and I haven't had a systemd-related crash in Y E A
> R S. Literally YEARS since a systemd bug caused a kernel panic (because
> that
ernel-latest-4.15.6-1 may raise kernel panic errors on Raven Ridge platform,
but kernel-4.14.18-1 works just fine.
Thanks!
D.F.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails f
_core.c:387: xc_dom_do_gunzip: inflate failed (rc=-5):
> > Internal error
> > xc: panic: xc_dom_bzimageloader.c:713: xc_dom_probe_bzimage_kernel: unable
> > to gzip decompress kernel: Invalid kernel
>
> A bit of googling revealed that either the initramfs image is corrupt.
On 3/3/21 3:29 PM, frag face wrote:
Hi all,
I'm running Qubes 4.0
My dom0 doesn't boot anymore (following an aborted Fedora update it
seems...).
Boot runs to kernel panic, see attached image.
From a newly installed Qubes on a different disk, I can mount my
crashed disk, decrypt it
h the other
packages had all already been updated/installed, even though they hadn't.
The next time I tried a reboot, the boot-up failed with a kernel panic and went
into a boot loop. Choosing advanced options and using the older kernel
4.14.57-1 allowed me to boot up, and here I am.
So wha
that matter in
> the BIOS ;-/
>
> Blacklisting the kernel module had no noticeable effect on the KERNEL PANIC
> ;-/
How about connecting the external (HDMI audio supporting) monitor? If
it's the issue I linked, maybe making HDMI audio use an interrupt will
work around it.
> S
On Sun, March 11, 2018 10:03 pm, [email protected] wrote:
> Hello, I am currently locked out of my qubes system because of a "kernel
> panic" error I encounter when I boot the system, after the grub screen. I
> don't really know what to do. The only thing I did befor
22/04/2021 T 20:33, Peter Palensky wrote :
Updating the kernel would remove the working one
Hi Peter,
Fedora, by default, keeps only the 3 last kernel versions. So before
updating the kernel, uninstall the most unwanted version. Or change the
`installonly_limit` (see
https://qubes
nstalling
> ).
>
> The problem is that at last update I forgot to change the xen.efi file
> version and that now I'm stuck with a kernel panic every time I try to boot
> on my QubesOS.
>
> I tried to rescue my OS with anaconda but I'm encountering two problems
Same issue here. Might have o do with the latest dom0 updates. Getting a kernel
panic.
When booting, in grub menu choose "advanced options" and try to boot with an
older kernel. Then it should boot. 4.14.18-1 works fine here, 4.14.35-1 breaks
everything.
Screenshot followin
am testing 5.10.8 and it seems working smooth, better than
>> 5.4.83. Sadly I tried to suspend/resume before sending this email and it
>> crashed. Then I did it again 4 o 5 five times without problems.
>
> You can collect panic and oops logs with a kernel that has
> CONFIG_EFI_V
sful
(20170728/tbxflad-246)
[0.508657] Initramfs unpacking failed: read error
[2.762742] Kernel panic 0 not syncing: UFS: Unable to mount root fs on
unknown-block(0.0)
[2.762769] CPU: Z PID: 1 Comm: swapper/0 Not tainted
4.1474-1.pvops.qubes.x86_64 #1
[2.762790] Hardware name: L
ybody !
>
> From: donoban
> Sent: Tue Jul 21 23:46:29 CEST 2020
> To:
> Subject: Re: [qubes-users] Stuck in kernel panic, cannot rescue my system
> with anaconda
>
>
> On 2020-07-21 21:26, 'Chempes Amt' via qubes-users wrote:
> > Hi everybody,
&
cial for me since I'm on the
> go a lot. I had to build my
> > own Qubes R4.0 ISO to get the installer to work due to it needing a 5.0+
> kernel for the graphics
> > driver. I installed `kernel-latest` from qubes-dom0-current testing but
> still didn't work. After
>
'3vpajfoaga22xc5rf' via qubes-users:
> **BUGS**
>
> * 1. As I've mentioned earlier, systemd fails to load the kernel modules.
>
> The full message is:
> [FAILED] Failed to start Load Kernel Modules.
> See 'systemctl status systemd-modules-load.ser
MESSAGE-
Hash: SHA256
On Mon, May 20, 2019 at 11:27:32AM +1000, haaber wrote:
after last update my Dell runs in a kernel panic -- reboot spiral. I
retype 4 important lines from a "photo screenshot" :
Initramfs unpacking failed: read error
This seems to be the problem. Check if
>
> You don't need to rebuild anything, just add boot_delay=10 to kernel
> command line. In grub you can press "e" to edit the entry, add the
> option to the line with "vmlinuz", then press ctrl+x to boot it.
>
It looks as though this thread went now
ilverblue in a HVM from the official
>ISO. I have noticed that there is some kernel panic before the HVM
>shuts down. The problem is that I cannot read it. Is there any way to
>read it, e.g., by disabling the automatic reboot somehow?
>
>Try pointing kernel at hvc0 console (consol
ace wrote:
> > Hi all,
> >
> > I'm running Qubes 4.0
> > My dom0 doesn't boot anymore (following an aborted Fedora update it
> > seems...).
> > Boot runs to kernel panic, see attached image.
> >
> > From a newly installed Qubes on a different
Le lundi 12 mars 2018 01:21:31 UTC+1, awokd a écrit :
> On Sun, March 11, 2018 10:03 pm, [email protected] wrote:
> > Hello, I am currently locked out of my qubes system because of a "kernel
> > panic" error I encounter when I boot the system, after the grub screen
le to install I get the qubes grub
> screen. Usually it would just boot for me normally but now I get a kernal
> panic and it closes. But if I go to advanced option - plane version 4.8 - xen
> 4.8 and linux 4.14.18-1.pvops
>
> Is the only one that will allow my qubes to start.
[0.179500] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSalt) while loading
> table (20170728/tbxfload-220)
> [0.188039] ACPI Error: 1 table load failures, 11 successful
> (20170728/tbxflad-246)
> [0.508657] Initramfs unpacking failed: read error
> [2.762742] Kernel panic 0 n
1.pvops.qubes.x86_64
> vmlinuz-4.19.128-1.pvops.qubes.x86_64
> xen-4.8.5-19.fc25.config
> xen-4.8.5-19.fc25.gz
> xen-4.8.gz
>
> Thank you in advance and have a nice evening everybody !
> **
>
>
>> --------
>> From: donoban
hough it will power off,
> when I power back on it's still stuck the same way. I have to pull the
> battery and power cable to get it to boot. I've tried:
>
> - shutting down sys-net and sys-usb prior to suspend
> - shutting down just sys-usb (since only those devices have
hough it will power off,
> when I power back on it's still stuck the same way. I have to pull the
> battery and power cable to get it to boot. I've tried:
>
> - shutting down sys-net and sys-usb prior to suspend
> - shutting down just sys-usb (since only those devices have
On 1/31/20 1:11 PM, [email protected] wrote:
Hi everyone!
Is anyone experiencing this issue on resume (VMs being killed randomly
apparently due to clock skew that generates kernel panic) ??
This is happening very often and it makes suspend useless.
I'm using a Lenovo T480s.
Any idea
On 12/31/20 5:02 PM, gluonium via qubes-users wrote:
> Hi!
>
> After the latest xen updates my laptop is stuck in a re-boot loop.
>
> The messages before the reboot are:
>
> Initram unpacking failed: read error
> Kernel panic - not syncing: VFS unable to mount root fs
Vega 10
>> graphics. Everything seems to be
>> > working besides suspend/resume which is crucial for me since I'm on the
>> go a lot. I had to build my
>> > own Qubes R4.0 ISO to get the installer to work due to it needing a
>> 5.0+ kernel for the graphics
&g
R4.0 ISO to get the installer to work due to it needing a 5.0+
> kernel for the graphics
> driver. I installed `kernel-latest` from qubes-dom0-current testing but still
> didn't work. After
> trying every kernel option on the face of this Earth I decided to use an
> experimenta
Hello,
I kindly was referred to this user group, from github for help with a kernel
issue (ISSUE#5272).
Computer boots Linux 4.14.74-1 normally. No issues.
Linux 4.19.67-1 or 5.2.11-1 kernel upgrades cause the CPU to freeze and forces
a reboot once the Boot reaches "Account Services&
4.13.4).
>
> From my side, I had kernel panic in VM with latest version 4.12.14 when
> merging all the options in CONFIG file from stable-4.9 due to
> vlv2_plat_configure_clock related to CONFIG_INTEL_ATOMISP (see
> https://github.com/fepitre/qubes-linux-kernel/commit/3edc1d7
On Sunday, March 11, 2018 at 11:03:02 PM UTC+1, [email protected] wrote:
> Hello, I am currently locked out of my qubes system because of a "kernel
> panic" error I encounter when I boot the system, after the grub screen. I
> don't really know what to do.
> The only
Am 22.02.21 um 20:40 schrieb haaber:
This behaviour might be linked to errors (e.g. my qubes install does not
support 5.x xen kernels: crashes can be caused by "memory stress" and
even if not, they always finish by loads of qmemman log entries, before
deep freeze (not even a kernel p
I have got problems on installing qubes r4.0 on the Lenovo pc. I get a kernel
panic. Where can I publish the photo of the screen? Please help me :)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this grou
EOI with ioapic_ack_old on!
> >
> > Getting ID: 0
> >
> > Getting LVT0: 700
> >
> > Getting LVT1: 400
> >
> > Suppress EOI broadcast on CPU#0
> >
> > enab
s=0002
failed :(.
****
Panic on CPU 0:
IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and send a report.
Then try booting with the 'noapic' option
When I add the `noapic` option to t
led ExtINT on CPU#0
>
> ENABLING IO_APIC IRQs
>
> -> Using old ACK method
>
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>
> CPU0: No irq handler for vector e7 (IRQ -8)
>
> IRQ7 a=0001[0001,] v=60[] t=IO-APIC-edge s=0002
>
> faile
ing resume, and results
in a xen panic on G505s - IMHO due to the static nature how the most recent (0x600111f)
AMD microcodes need to be compiled in Corebooted systems.
It is no use to revert the whole patch, because it'll break the other xen
patches introduced since. But you can:
diff -ur
ul
> (20170728/tbxflad-246)
> [ 0.508657] Initramfs unpacking failed: read error
> [ 2.762742] Kernel panic 0 not syncing: UFS: Unable to mount root fs on
> unknown-block(0.0)
> [ 2.762769] CPU: Z PID: 1 Comm: swapper/0 Not tainted
> 4.1474-1.pvops.qubes.x86_64 #1
> [ 2.
This behaviour might be linked to errors (e.g. my qubes install does not
support 5.x xen kernels: crashes can be caused by "memory stress" and
even if not, they always finish by loads of qmemman log entries, before
deep freeze (not even a kernel panic, just sudden death)
What does &
> 5.4.83. Sadly I tried to suspend/resume before sending this email and it
> crashed. Then I did it again 4 o 5 five times without problems.
You can collect panic and oops logs with a kernel that has
CONFIG_EFI_VARS_PSTORE enabled. If you don't already have one, you may
build qubes-linux
4 is
> > available and also I created the branch for devel-4.13 (currently version
> > 4.13.4).
> >
> > From my side, I had kernel panic in VM with latest version 4.12.14 when
> > merging all the options in CONFIG file from stable-4.9 due to
> > vlv2_pl
On Thursday, 20 July 2017 20:29:11 UTC+8, Patrik Hagara wrote:
> On 07/20/2017 02:08 PM, Patrik Hagara wrote:
> > As for the Linux kernel, you want to use the earlyprintk param,
> > either "earlyprintk=vga,keep" or "earlyprintk=xen,keep" should
> > work.
uld anyone give some advices?
>
> BTW, here is the reason: I have multiple kernels installed and
> kernel-latest-4.15.6-1 may raise kernel panic errors on Raven Ridge platform,
> but kernel-4.14.18-1 works just fine.
>
> Thanks!
> D.F.
Two methods I know of, but there are
I thought there were steps detailing this somewhere, but can't locate.
Anyways:
go to dom0 terminal
awk -F\' '/menuentry / { print i++, $2}' /boot/grub/grub.cfg
sudo grub2-set-default ### [whichever number you want, or the full text
string here in quotes]
Once you get a work
blob/patch-5/user/common-tasks/software-update-dom0.md#changing-default-kernel
--
- 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 G
I updated qubes 4.0 and there were some errors (about transactions on--I
believe--some crypto stuff). Afterwards, I couldn't boot getting the message
kernel panic -- not syncing: VFS unable to mount fs on unknown block (0,0)
the problem is that my backup is a bit old, and if possible I
e since I'm on the go a
>> lot. I had to build my
>> own Qubes R4.0 ISO to get the installer to work due to it needing a 5.0+
>> kernel for the graphics
>> driver. I installed `kernel-latest` from qubes-dom0-current testing but
>> still didn't work. After
&
-4.8.3-4 to
> > xen-4.8.3-5. This patch checks the availability of previous CPU features
> > (..Spectre) during resume, and results in a xen panic on G505s - IMHO due
> > to the static nature how the most recent (0x600111f) AMD microcodes need to
> > be compiled in Core
efore
deep freeze (not even a kernel panic, just sudden death)
What does "your qubes install" mean? Mine has been auto-updated to
kernel 5.4.88-1
mine too. But since this kernel crashes after 2-30 minutes I downgraded
(xen!) kernel back to 4.19.163. That works, at least. My App-VM's ru
ad T495
>>> with an AMD Ryzen Pro
>>> 3700U and Vega 10 graphics. Everything seems to be
>>>> working besides suspend/resume which is crucial for me since I'm on the go
>>>> a lot. I had to build
>>> my
>>>> own Qubes R4.0 ISO to get
rtunately.
> Of course the rubber-duck effect kicks in right after I click send. I was
> able to disable hpet using the `clocksource` flag, but I still got the same
> panic.
>
> I did, however, get a picture of the stack trace I've been getting (which
> in hindsight I
What I did was boot the qubes installation iso and chose troubleshooting. Then
booted into recovery mode prompt.
Then did chroot /mnt/sysimage then did fsck -y /dev/mapper/dom0_root
It went through pages of errors it said it fixed. then I rebooted and qubes
started with no issues.
--
Yo
Hi everyone!
Is anyone experiencing this issue on resume (VMs being killed randomly
apparently due to clock skew that generates kernel panic) ??
This is happening very often and it makes suspend useless.
I'm using a Lenovo T480s.
Any ideas are really appreciated!
Thanks!
December 22, 2
1 - 100 of 209 matches
Mail list logo
