-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Jun 12, 2022 at 05:05:35PM -0400, Demi Marie Obenour wrote:
> On Sun, Jun 12, 2022 at 02:57:49AM -0700, Peter Palensky wrote:
> > 
> > 
> > On Saturday, June 11, 2022 at 7:21:20 PM UTC+2 Demi Marie Obenour wrote:
> > 
> > > -----BEGIN PGP SIGNED MESSAGE----- 
> > > Hash: SHA256 
> > >
> > > On Sat, Jun 11, 2022 at 03:00:09AM -0700, Peter Palensky wrote: 
> > > > 
> > > > On Saturday, June 11, 2022 at 1:09:47 AM UTC+2 haa...@web.de wrote: 
> > > > 
> > > > > > Which kernel version do you need to hold? You can update a subset 
> > > > > > of 
> > > > > > packages by giving them as arguments to qubes-dom0-update, but I 
> > > would 
> > > > > > like to know what the forseeable problems are. 
> > > > > 
> > > > > The reason is simple: all (!) 5.x xen kernels I tested so far 
> > > > > crash/freeze my system in less than 5 minutes, often only seconds 
> > > (open 
> > > > > issue on github since 18 months). Therefore I keep a 4.19 kernel for 
> > > xen 
> > > > > (only) -- until now the updater respected that: it installed some new 
> > > > > 5.x kernel and kernel-latest. Every single time, I bravely try them 
> > > out, 
> > > > > and each time they crash: each time I can revert back to 4.19 by a 
> > > > > linux-life usb hack. 
> > > > > 
> > > > > Last kernel update wants to remove my 4.19 kernel, and no way I can 
> > > > > accept that, given the history. ( again a curse on Intel and Dell for 
> > > > > their buggy hardware ). 
> > > > > 
> > > > > best, Bernhard 
> > > > > 
> > > > > 
> > > > Same here (Dell XPS13). The only usable dom0 kernels are 4.x and 5.4.88 
> > > > (already gone :-0) and 5.4.175 (please let me keep that!). 

There are a couple more options to choose from - for LTS kernels we keep
some of them updated, even after the default is switched to the next
one. For R4.0 there is for example kernel-419. You can check available
options via `qubes-dom0-update --action=search kernel`.


> > > > Everything else either crashes dom0 (e.g., 5.15) or stalls sys-usb 
> > > > (e.g. 
> > > > 5.12.). 
> > > > 
> > > > It says "00:14.0 USB controller problem", might be a usb3.0 problem, 
> > > tried 
> > > > various things, nothing helped, my BIOS has no option to disable xHCI. 
> > >
> > > I am hesitant to ask, since it would require running unsigned code 
> > > (yuck!), but would you be comfortable doing a kernel git bisection? 
> > > That would allow figuring out exactly which commit caused the problem, 
> > > and would vastly improve the likelihood of the bug being fixed. 
> > 
> > Aaehm... It is my work computer, i need it every day and  can not risk 
> > anything...
> > Is there a safe/standard procedure in qubes to compile the bisects, add 
> > them to grub without removing the working kernel, etc.?
> 
> Not that I am aware of, sadly.  Marek (CCd) might have suggestions.

For any tests, I usually place kernel+initramfs under some arbitrary
name that does not interfere with version-based entries. And do that by
installing kernel "manually", exactly to avoid dnf/rpm removing older
packages. For the grub entry, I usually edit
/boot/efi/EFI/qubes/grub.cfg manually (copy existing section and just
replace file names). But regenerating it with grub2-mkconfig should be
safe too.
This does require manual cleaning after testing is finished,
though...

Here is example script to build and install kernel in dom0:

    #!/bin/sh

    set -e
    make olddefconfig
    make -j2
    kver=$(make kernelrelease)
    sudo make modules_install
    sudo cp arch/x86/boot/bzImage /boot/vmlinuz-test
    sudo dracut -f --kver="$kver" /boot/initramfs-test.img

it can be launched from kernel sources.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmKmY0MACgkQ24/THMrX
1yy76AgAgUS+jgFIaNeFSGr7ZMfudTbFNkGvBET6vyem+ddHOais32FHlNcAscmL
qf1MVvl8GmJCH/FozJ6ZEFmFOVcE8/fEok2IL131fzkNTc+YRuH0GmLvH5a0X1o/
mHFRoYvkaD+MKNSFv7gz4n1SadeDoFDyfed9iJaV2PjCIsEohcbDzvtVyTCnFvxM
GUiIPUE+OW/P6AKtR7iEFkNsdnWtahHzPsCuizOW6H/8lWVmOITtWDI1UzVL19zo
jVAUhmUhB9exh17wL/YG1g2MvpN5VxP48yQNuUtQGLJ5ta1AykKrYBqDEZu3Napu
JHfB3xy/WIxVN8kazzq/1khe8Q+LUQ==
=qPpk
-----END PGP SIGNATURE-----

-- 
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/YqZjQxW/UJkjznRd%40mail-itl.

Reply via email to