Why not jump to virtualbox 5.1.6 instead of reverting to 5.1.2? It has fixes for kernel 4.8 in the Linux Additions.

Because 5.1.2 is the latest one _validated_ in core updates.

kernel needs to go out with matching kmods for what is on the mirrors.

and in this case fixes for kernel 4.8 is moot in mga5 as official kernel is 4.4 series....

the other option is to validate 5.1.6 against 4.4.16-1 first, and then redo new kmods for 4.4.21-1

but if 5.1.6 is still broken it needs to be reverted again and 5.1.2 kmods rebuilt again...

Anyway, I'll let QA decide what they want to do...

Thank you Thomas for doing this kernel update.

Ideally we'd fix vbox 5.1.6 and do these together, but it comes down to whether we're able to fix it or not.  I tried and couldn't fix it, and I don't really know where the issue is originating from, because as best I can tell, the offending file hasn't changed since April, so the actual cause of the breakage came from somewhere else, and I don't know if that's in Python itself, or some Python library, or some other part of the VirtualBox code.  I didn't see any new commits upstream to address this issue when I last checked.

So for now, we can proceed with testing this kernel with 5.1.2.  If we manage to get a fix for vbox 5.1.6 before the kernel is validated, then we can move forward with that.

Updated my HP Probook 6550b laptop to kernel-desktop-4.4.21-2, including the firmware packages not listed above, and all seems OK. The wifi problem I saw with kernel 4.4.16 is gone. Firefox and Google Earth both function as they should.

CC: (none) => andrewsfarm

Setting feedback marker, turns out it breaks network teaming using bonding driver

Whiteboard: (none) => feedback

Just as I was about to report success with a 64-bit update on my Dell Dimension E310 (P4 processor, Intel graphics), both 32-bit and 64-bit updates with my desktop with Athlon X2 7750 processor and nvidia graphics card (340 driver), as well as 32-bit vbox Mageia guests in both 32-bit and 64-bit with virtualbox 5.1.2.

Everything I've tried it with so far loves it.

So, I found the commit that broke network bonding, and reverted it for now.

Upstream also released 4.4.22 in the same time, so updated to that...


This is the kernel I think need to be on Mga 5.1 isos for better oob user experience...

Also note the nonfree firmware update in bug 19453 that should go out before or at the same time as this update...

Advisory will follow...


SRPMS:
kernel-4.4.22-1.mga5.src.rpm
kernel-userspace-headers-4.4.22-1.mga5.src.rpm
kmod-vboxadditions-5.1.2-6.mga5.src.rpm
kmod-virtualbox-5.1.2-6.mga5.src.rpm
kmod-xtables-addons-2.10-12.mga5.src.rpm


i586:
cpupower-4.4.22-1.mga5.i586.rpm
cpupower-devel-4.4.22-1.mga5.i586.rpm
kernel-desktop-4.4.22-1.mga5-1-1.mga5.i586.rpm
kernel-desktop586-4.4.22-1.mga5-1-1.mga5.i586.rpm
kernel-desktop586-devel-4.4.22-1.mga5-1-1.mga5.i586.rpm
kernel-desktop586-devel-latest-4.4.22-1.mga5.i586.rpm
kernel-desktop586-latest-4.4.22-1.mga5.i586.rpm
kernel-desktop-devel-4.4.22-1.mga5-1-1.mga5.i586.rpm
kernel-desktop-devel-latest-4.4.22-1.mga5.i586.rpm
kernel-desktop-latest-4.4.22-1.mga5.i586.rpm
kernel-doc-4.4.22-1.mga5.noarch.rpm
kernel-server-4.4.22-1.mga5-1-1.mga5.i586.rpm
kernel-server-devel-4.4.22-1.mga5-1-1.mga5.i586.rpm
kernel-server-devel-latest-4.4.22-1.mga5.i586.rpm
kernel-server-latest-4.4.22-1.mga5.i586.rpm
kernel-source-4.4.22-1.mga5-1-1.mga5.noarch.rpm
kernel-source-latest-4.4.22-1.mga5.noarch.rpm
kernel-userspace-headers-4.4.22-1.mga5.i586.rpm
perf-4.4.22-1.mga5.i586.rpm

vboxadditions-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-4.4.22-desktop586-1.mga5-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-desktop586-latest-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-desktop-latest-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-server-latest-5.1.2-6.mga5.i586.rpm

virtualbox-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-4.4.22-desktop586-1.mga5-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-desktop586-latest-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-desktop-latest-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-server-latest-5.1.2-6.mga5.i586.rpm

xtables-addons-kernel-4.4.22-desktop-1.mga5-2.10-12.mga5.i586.rpm
xtables-addons-kernel-4.4.22-desktop586-1.mga5-2.10-12.mga5.i586.rpm
xtables-addons-kernel-4.4.22-server-1.mga5-2.10-12.mga5.i586.rpm
xtables-addons-kernel-desktop586-latest-2.10-12.mga5.i586.rpm
xtables-addons-kernel-desktop-latest-2.10-12.mga5.i586.rpm
xtables-addons-kernel-server-latest-2.10-12.mga5.i586.rpm


x86_64:
cpupower-4.4.22-1.mga5.x86_64.rpm
cpupower-devel-4.4.22-1.mga5.x86_64.rpm
kernel-desktop-4.4.22-1.mga5-1-1.mga5.x86_64.rpm
kernel-desktop-devel-4.4.22-1.mga5-1-1.mga5.x86_64.rpm
kernel-desktop-devel-latest-4.4.22-1.mga5.x86_64.rpm
kernel-desktop-latest-4.4.22-1.mga5.x86_64.rpm
kernel-doc-4.4.22-1.mga5.noarch.rpm
kernel-server-4.4.22-1.mga5-1-1.mga5.x86_64.rpm
kernel-server-devel-4.4.22-1.mga5-1-1.mga5.x86_64.rpm
kernel-server-devel-latest-4.4.22-1.mga5.x86_64.rpm
kernel-server-latest-4.4.22-1.mga5.x86_64.rpm
kernel-source-4.4.22-1.mga5-1-1.mga5.noarch.rpm
kernel-source-latest-4.4.22-1.mga5.noarch.rpm
kernel-userspace-headers-4.4.22-1.mga5.x86_64.rpm
perf-4.4.22-1.mga5.x86_64.rpm

vboxadditions-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.x86_64.rpm
vboxadditions-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.x86_64.rpm
vboxadditions-kernel-desktop-latest-5.1.2-6.mga5.x86_64.rpm
vboxadditions-kernel-server-latest-5.1.2-6.mga5.x86_64.rpm

virtualbox-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.x86_64.rpm
virtualbox-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.x86_64.rpm
virtualbox-kernel-desktop-latest-5.1.2-6.mga5.x86_64.rpm
virtualbox-kernel-server-latest-5.1.2-6.mga5.x86_64.rpm

xtables-addons-kernel-4.4.22-desktop-1.mga5-2.10-12.mga5.x86_64.rpm
xtables-addons-kernel-4.4.22-server-1.mga5-2.10-12.mga5.x86_64.rpm
xtables-addons-kernel-desktop-latest-2.10-12.mga5.x86_64.rpm
xtables-addons-kernel-server-latest-2.10-12.mga5.x86_64.rpm

Summary: Update Request: kernel-4.4.21-1.mga5 => Update Request: kernel-4.4.22-1.mga5
Whiteboard: feedback => (none)

Already installed the firmwares when testing 4.4.21-2. Still working with my HP laptop and kernel 4.4.22-1. 

Have not installed VirtualBox on this laptop yet - will attempt to do so now, after the upgrade.

Installed virtualbox 5.1.2, giving a rough simulation of someone installing Mageia 5.1 and then installing virtualbox with kernel 4.4.22-1. All installed correctly, and was able to install the downloaded 5.1.2 extension pack. No guests yet, but I have no reason to expect them not to work.

Checked 32-bit and 64-bit server kernels on AMD Athlon X2 7750 processor and nvidia video using 340 driver, with virtualbox on both. Everything seems OK.

Also checked 64-bit desktop kernel with P4 processor and Intel video, also OK.

*** Bug 18734 has been marked as a duplicate of this bug. ***

CC: (none) => listas.apl

Advisory:

Updated kernel packages fixes security vulnerablilities

This update is based on the upstream 4.4.22 kernel and fixes atleast theese
security issues:

sound/core/timer.c in the Linux kernel through 4.6 does not initialize 
certain r1 data structures, which allows local users to obtain sensitive
information from kernel stack memory via crafted use of the ALSA timer
interface, related to the (1) snd_timer_user_ccallback and (2)
snd_timer_user_tinterrupt functions (CVE-2016-4578).

The tipc_nl_compat_link_dump function in net/tipc/netlink_compat.c in the
Linux kernel through 4.6.3 does not properly copy a certain string, which
allows local users to obtain sensitive information from kernel stack memory
by reading a Netlink message (CVE-2016-5243).

The rds_inc_info_copy function in net/rds/recv.c in the Linux kernel through
4.6.3 does not initialize a certain structure member, which allows remote
attackers to obtain sensitive information from kernel stack memory by reading
an RDS message (CVE-2016-5244).

Memory leak in the airspy_probe function in drivers/media/usb/airspy/airspy.c
in the airspy USB driver in the Linux kernel before 4.7 allows local users 
to cause a denial of service (memory consumption) via a crafted USB device
that emulates many VFL_TYPE_SDR or VFL_TYPE_SUBDEV devices and performs many
connect and disconnect operations (CVE-2016-5400).

net/ipv4/tcp_input.c in the Linux kernel before 4.7 does not properly
determine the rate of challenge ACK segments, which makes it easier for
man-in-the-middle attackers to hijack TCP sessions via a blind in-window
attack (CVE-2016-5696).

Race condition in the ioctl_send_fib function in drivers/scsi/aacraid/
commctrl.c in the Linux kernel through 4.7 allows local users to cause a
denial of service (out-of-bounds access or system crash) by changing a
certain size value, aka a "double fetch" vulnerability (CVE-2016-6480).

This update also changes the following:
- enables STRICT_DEVMEM as a security hardening
- disables FW_LOADER_USER_HELPER_FALLBACK again (un-intentionally 
  enabled in 4.4 series upgrade) that slows down boot or even makes
   wireless connection fail with drivers with multiple possible
  firmwares (mga#19390).

For other fixes in this update, see the referenced changelogs.


References:
https://bugs.mageia.org/show_bug.cgi?id=19397
https://bugs.mageia.org/show_bug.cgi?id=19390
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.17
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.18
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.19
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.20
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.21
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22

Oops... 
seems I'm too tired for this... 

I already fixed CVE-2016-5696 in:
http://advisories.mageia.org/MGASA-2016-0271.html  

So advisory should be:

Updated kernel packages fixes security vulnerablilities

This update is based on the upstream 4.4.22 kernel and fixes atleast theese
security issues:

sound/core/timer.c in the Linux kernel through 4.6 does not initialize 
certain r1 data structures, which allows local users to obtain sensitive
information from kernel stack memory via crafted use of the ALSA timer
interface, related to the (1) snd_timer_user_ccallback and (2)
snd_timer_user_tinterrupt functions (CVE-2016-4578).

The tipc_nl_compat_link_dump function in net/tipc/netlink_compat.c in the
Linux kernel through 4.6.3 does not properly copy a certain string, which
allows local users to obtain sensitive information from kernel stack memory
by reading a Netlink message (CVE-2016-5243).

The rds_inc_info_copy function in net/rds/recv.c in the Linux kernel through
4.6.3 does not initialize a certain structure member, which allows remote
attackers to obtain sensitive information from kernel stack memory by reading
an RDS message (CVE-2016-5244).

Memory leak in the airspy_probe function in drivers/media/usb/airspy/airspy.c
in the airspy USB driver in the Linux kernel before 4.7 allows local users 
to cause a denial of service (memory consumption) via a crafted USB device
that emulates many VFL_TYPE_SDR or VFL_TYPE_SUBDEV devices and performs many
connect and disconnect operations (CVE-2016-5400).

Race condition in the ioctl_send_fib function in drivers/scsi/aacraid/
commctrl.c in the Linux kernel through 4.7 allows local users to cause a
denial of service (out-of-bounds access or system crash) by changing a
certain size value, aka a "double fetch" vulnerability (CVE-2016-6480).

This update also changes the following:
- enables STRICT_DEVMEM as a security hardening
- disables FW_LOADER_USER_HELPER_FALLBACK again (un-intentionally 
  enabled in 4.4 series upgrade) that slows down boot or even makes
   wireless connection fail with drivers with multiple possible
  firmwares (mga#19390).

For other fixes in this update, see the referenced changelogs.


References:
https://bugs.mageia.org/show_bug.cgi?id=19397
https://bugs.mageia.org/show_bug.cgi?id=19390
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.17
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.18
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.19
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.20
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.21
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.22

kmod-virtualbox and kmod-vboxadditions are now in Bug 19213 with the VirtualBox 5.1.6 update.  Hopefully it will work OK this time, and then these can go out together.  If not, we'll have to revert it again and rebuild the kmods with the old one.

For what it's worth, kernel 4.4.22-1 is also OK in a 32-bit Mageia 5 guest in 64-bit virtualbox 5.1.2.

x86_64 hardware with nvidia

Installed these:
- dkms-virtualbox-5.1.6-1.mga5.noarch
- kernel-desktop-4.4.22-1.mga5-1-1.mga5.x86_64
- kernel-desktop-latest-4.4.22-1.mga5.x86_64
- kernel-firmware-nonfree-20160914-1.mga5.nonfree.noarch
- radeon-firmware-20160920-1.mga5.nonfree.noarch
- virtualbox-5.1.6-1.mga5.x86_64
- virtualbox-kernel-4.4.22-desktop-1.mga5-5.1.6-1.mga5.x86_64
- virtualbox-kernel-desktop-latest-5.1.6-1.mga5.x86_64
- cpupower
- xtables-addons-kernel
- xtables-addons-kernel-desktop-latest

meta-task-5-28.1.mga5.noarch was already installed.

The system rebooted OK to the new kernel with nvidia352.79 running.

CC: (none) => tarazed25

On real hardware, M5, KDE, 64-bit

Package(s) under test:
kernel-desktop-latest kernel-desktop-devel-latest

default install of kernel-desktop-latest & kernel-desktop-devel-latest

[root@localhost wilcal]# uname -a
Linux localhost.localdomain 4.4.16-desktop-1.mga5 #1 SMP Tue Jul 26 09:23:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop-latest
Package kernel-desktop-latest-4.4.16-1.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi kernel-desktop-devel-latest
Package kernel-desktop-devel-latest-4.4.16-1.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi x11-driver-video-nvidia-current
Package x11-driver-video-nvidia-current-352.79-3.mga5.nonfree.x86_64 is already installed
[root@localhost wilcal]# lspci -k
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device 3518
        Kernel driver in use: nvidia
        Kernel modules: nvidiafb, nouveau, nvidia_current

System boots to a working desktop. Common apps work. Screen dimensions are correct.

install kernel under test from updates_testing using:
urpmi --search-media Testing kernel-desktop-latest kernel-desktop-devel-latest
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "core_updates_testing_64")
  kernel-desktop-4.4.22-1.mga5   1            1.mga5        x86_64  
  kernel-desktop-devel-4.4.22-1> 1            1.mga5        x86_64  
  kernel-desktop-devel-latest    4.4.22       1.mga5        x86_64  
  kernel-desktop-latest          4.4.22       1.mga5        x86_64  
(medium "nonfree_updates_testing_64")
  kernel-firmware-nonfree        20160914     1.mga5.nonfr> noarch  
  radeon-firmware                20160920     1.mga5.nonfr> noarch  

[root@localhost wilcal]# uname -a
Linux localhost.localdomain 4.4.22-desktop-1.mga5 #1 SMP Sat Sep 24 20:22:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop-latest
Package kernel-desktop-latest-4.4.22-1.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi kernel-desktop-devel-latest
Package kernel-desktop-devel-latest-4.4.22-1.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi x11-driver-video-nvidia-current
Package x11-driver-video-nvidia-current-352.79-3.mga5.nonfree.x86_64 is already installed
[root@localhost wilcal]# lspci -k
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device 3518
        Kernel driver in use: nvidia
        Kernel modules: nvidiafb, nouveau, nvidia_current
        
System boots to a working desktop. Common apps work. Screen dimensions are correct.
  
Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)

CC: (none) => wilcal.int

In Vbox, M5, KDE, 32-bit

Package(s) under test:
kernel-desktop586-latest vboxadditions-kernel-desktop586-latest radeon-firmware

default install of kernel-desktop586-latest vboxadditions-kernel-desktop586-latest radeon-firmware

[root@localhost wilcal]# uname -a
Linux localhost.localdomain 4.4.16-desktop586-1.mga5 #1 SMP Tue Jul 26 09:24:28 UTC 2016 i686 i686 i686 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop586-latest
Package kernel-desktop586-latest-4.4.16-1.mga5.i586 is already installed
[root@localhost wilcal]# urpmi vboxadditions-kernel-desktop586-latest
Package vboxadditions-kernel-desktop586-latest-5.1.2-2.mga5.i586 is already installed
[root@localhost wilcal]# urpmi radeon-firmware
Package radeon-firmware-20160712-1.mga5.nonfree.noarch is already installed

System boots to a working desktop. Common apps work. Screen dimensions are correct.

install from updates_testing:
kernel-desktop586-latest vboxadditions-kernel-desktop586-latest radeon-firmware

[root@localhost wilcal]# uname -a
Linux localhost.localdomain 4.4.22-desktop586-1.mga5 #1 SMP Sat Sep 24 20:22:16 UTC 2016 i686 i686 i686 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop586-latest
Package kernel-desktop586-latest-4.4.22-1.mga5.i586 is already installed
[root@localhost wilcal]# urpmi vboxadditions-kernel-desktop586-latest
Package vboxadditions-kernel-desktop586-latest-5.1.6-1.mga5.i586 is already installed
[root@localhost wilcal]# urpmi radeon-firmware
Package radeon-firmware-20160920-1.mga5.nonfree.noarch is already installed
        
System boots to a working desktop. Common apps work. Screen dimensions are correct.

Test platform: VirtualBox Ver: 5.1.2_OSE

In Vbox, M5, KDE, 64-bit

Package(s) under test:
kernel-desktop-latest vboxadditions-kernel-desktop-latest radeon-firmware

default install of kernel-desktop-latest vboxadditions-kernel-desktop-latest radeon-firmware

[root@localhost wilcal]# uname -a
Linux localhost.localdomain 4.4.16-desktop-1.mga5 #1 SMP Tue Jul 26 09:23:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop-latest
Package kernel-desktop-latest-4.4.16-1.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest
Package vboxadditions-kernel-desktop-latest-5.1.2-2.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi radeon-firmware
Package radeon-firmware-20160712-1.mga5.nonfree.noarch is already installed

System boots to a working desktop. Common apps work. Screen dimensions are correct.

install from updates_testing:
kernel-desktop-latest vboxadditions-kernel-desktop-latest radeon-firmware

[root@localhost wilcal]# uname -a
Linux localhost.localdomain 4.4.22-desktop-1.mga5 #1 SMP Sat Sep 24 20:22:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost wilcal]# urpmi kernel-desktop-latest
Package kernel-desktop-latest-4.4.22-1.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest
Package vboxadditions-kernel-desktop-latest-5.1.6-1.mga5.x86_64 is already installed
[root@localhost wilcal]# urpmi radeon-firmware
Package radeon-firmware-20160920-1.mga5.nonfree.noarch is already installed
        
System boots to a working desktop. Common apps work. Screen dimensions are correct.

Test platform: VirtualBox Ver: 5.1.2_OSE

Testing M5 x64 real hardware with AMD/ATI/Radeon HD7310 graphics

While I have the info, updating the following componenents:
- cpupower-4.4.22-1.mga5.x86_64
- kernel-desktop-4.4.22-1.mga5-1-1.mga5.x86_64
- kernel-desktop-devel-4.4.22-1.mga5-1-1.mga5.x86_64
- kernel-desktop-devel-latest-4.4.22-1.mga5.x86_64
- kernel-desktop-latest-4.4.22-1.mga5.x86_64
- kernel-userspace-headers-4.4.22-1.mga5.x86_64
- radeon-firmware-20160920-1.mga5.nonfree.noarch

Result to follow.

CC: (none) => lewyssmith

Not good. I should have specified real *EFI* hardware on Comment 20...

On selecting Mageia 5 from my rEFInd menu, which normally shows the M5 Grub 2 boot menu, I got - yet again- a grub prompt. No possibility of choosing an earlier kernel. This has happened on several prior kernel updates, and I am unsure why.

FWIW Choosing the 'mageia' EFI boot menu entry leads to the most recently *installed* Mageia: 6 Grub2 boot menu (also accessible from rEFInd), not the Mageia 5 one. So kernel updates do not fiddle that far back in the EFI boot process.

To recover: boot another Linux and chroot into the broken one, then
 # update-grub
which takes a full 10m on my box due to a known os-prober problem. I forgot to re-mount the ESP on the chrooted M5 /boot/EFI/ , but that did not seem to matter.

Re-booting the box, choosing Mageia 5 then shows correctly the M5 Grub2 boot menu, and choosing 'advanced otpins' from that shows another menu with all installed kernels, this latest first. Booting the default Mageia entry works again.
But I am not OK'ing this.

@Lewis, 

Sorry to see the problems, but...

those issues are not related to this update as such as we haven't changed anything on the kernel side regarding bootloader stuff...

Kernel install simply notifies drakx about the updated kernel, and drakx is supposed to do the rest.... but it fails somewhat on your setup...

So it's not a kernel bug, but a drakx one.

But I think tv plans to backport grub2 related fixes from upcoming mga6 to mga5 (to be part of the mga5.1 iso rollout)

I've already backported /queued up some nvme and kernel 4.4 support in drakx for the 5.1 isos:
http://gitweb.mageia.org/software/drakx/log/?h=distro/mga5

Testing on mga5-32

- cpupower-4.4.22-1.mga5.i586
- kernel-desktop-4.4.22-1.mga5-1-1.mga5.i586
- kernel-desktop-devel-4.4.22-1.mga5-1-1.mga5.i586
- kernel-desktop-devel-latest-4.4.22-1.mga5.i586
- kernel-desktop-latest-4.4.22-1.mga5.i586
- kernel-firmware-nonfree-20160914-1.mga5.nonfree.noarch
- kernel-userspace-headers-4.4.22-1.mga5.i586

Packages installed cleanly, system rebooted normally, no regressions noted

This update is OK for me on this system:

Mobo: ECS model: GeForce7050M-M v: 1.0 Bios: American Megatrends 
CPU:       Quad core AMD Phenom 9500 (-MCP-)
Graphics:  Card: NVIDIA GF108 [GeForce GT 630]
           Display Server: X.Org 1.16.4 drivers: v4l,nouveau

CC: (none) => jim

thierry, any news on the grub2 fixes backports ? ( see #21 and #22 ).

CC: (none) => mageia, thierry.vignaud

test for mga5 64bit:

Got this error when installing :
Creating: target|kernel|dracut args|basicmodules 
remove-boot-splash: Format of /boot/initrd-4.4.22-desktop-1.mga5.img not recognized

i used the command : urpmi kernel-desktop kernel-firmware-nonfree

i don't know if this error is a real problem or not.

Testing on mga5-64
Reboot OK

No regressions for me.

Testing on mga5-32 on 3 different systems : Dell 600, Fujitsu Lifebook and Asus Eeepc901

Reboot OK

No regressions for now.

CC: (none) => lists.jjorge

This has been running on one machine for nearly two weeks.  The only problem has been firefox (45.4.0) which freezes occasionally for 10 - 20 seconds.

Hardware is x86_64
Intel(R) Core(TM) i7-4790K CPU  4.00GHz, 4 cores, hyperthreading
RAM 2 x DIMM1, total 16GB
nvidia GK104 [GeForce GTX 770]

Hi,

the new kernel - 4.4.22 along with the virtualbox additions updates is working fine on my x86-64 VM. Tested Xfce, firefox, the terminal, etc.

Tested on two systems, both 64-bit/UEFI:

System 1:
Intel(R) Core(TM) i5-3550
Radeon HD 7850 (using both ati and fglrx drivers)
Atheros AR8161 Gigabit Ethernet

System 2:
Intel(R) Core(TM) i7-3630QM
Optimus graphics (only using the intel driver)
Intel Centrino Wireless-N 2230

No regressions seen.

CC: (none) => mageia

Have been using it for several days. No issues found.
All is working as usual on a intel x86_64 system with nvidia card.

System:
Intel(R) Core(TM)2 Quad CPU Q9400
nVidia GeForce 210
Realtek RTL8111/8168/8411
Intel Corporation 82801JI (chipset, USB, HD audio, PCI, etc)
JMicron JMB368 IDE
DragonRise USB joystick/gamepad
Logitech USB wireless keyboard/mouse

# rpm -qa | grep -Ei 'kernel|virtualbox|vbox' | sort
dkms-virtualbox-5.1.6-1.mga5
kernel-desktop-4.4.22-1.mga5-1-1.mga5
kernel-desktop-devel-4.4.22-1.mga5-1-1.mga5
kernel-desktop-devel-latest-4.4.22-1.mga5
kernel-desktop-latest-4.4.22-1.mga5
kernel-firmware-20160409-1.mga5
kernel-firmware-nonfree-20160914-1.mga5.nonfree
kernel-userspace-headers-4.4.22-1.mga5
nvidia340-kernel-desktop-latest-340.96-6.mga5.nonfree
virtualbox-5.1.6-1.mga5
virtualbox-doc-5.1.6-1.mga5

CC: (none) => mageia

Testing on mga5-64 on an Acer 2008 laptop.

Reboot OK

No regressions for now.

unvalidating for now...

as virtualbox 5.1.6 is still broken, 5.1.2 kmods are  restored, so a quick test with:

RPMS:
kmod-vboxadditions-5.1.2-6.mga5.src.rpm
kmod-virtualbox-5.1.2-6.mga5.src.rpm


i586:
vboxadditions-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-4.4.22-desktop586-1.mga5-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-desktop586-latest-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-desktop-latest-5.1.2-6.mga5.i586.rpm
vboxadditions-kernel-server-latest-5.1.2-6.mga5.i586.rpm

virtualbox-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-4.4.22-desktop586-1.mga5-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-desktop586-latest-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-desktop-latest-5.1.2-6.mga5.i586.rpm
virtualbox-kernel-server-latest-5.1.2-6.mga5.i586.rpm


x86_64:
vboxadditions-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.x86_64.rpm
vboxadditions-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.x86_64.rpm
vboxadditions-kernel-desktop-latest-5.1.2-6.mga5.x86_64.rpm
vboxadditions-kernel-server-latest-5.1.2-6.mga5.x86_64.rpm

virtualbox-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5.x86_64.rpm
virtualbox-kernel-4.4.22-server-1.mga5-5.1.2-6.mga5.x86_64.rpm
virtualbox-kernel-desktop-latest-5.1.2-6.mga5.x86_64.rpm
virtualbox-kernel-server-latest-5.1.2-6.mga5.x86_64.rpm




need to be done before pushing

Keywords: validated_update => (none)

Some remnants of 5.1.6 get pulled in:

virtualbox-5.1.2-1.mga5.x86_64 pulls in virtualbox-doc-5.1.6-1.mga5.noarch

virtualbox-guest-additions-5.1.2-1.mga5.x86_64 pulls in x11-driver-video-vboxvideo-5.1.6-1.mga5.x86_64

Sorry, I wasn't specific about it...

I only removed the prebuilt 5.1.6 kmods...
The rest of vbox 5.1.6 is still in testing...

So you need to be specific when you pull in the kmods like only selecting the kmod packages in rpmdrake, or:


_not_ having Testing enabled.

then ensure you have only vbox 5.1.2 on your system

and:


urpmi.update ""
urpmi --media Testing virtualbox-kernel-desktop-latest

or 
urpmi --media Testing vboxadditions-kernel-desktop-latest



should pull in needed kmods

and obviously use desktop/desktop586/server depending on what you test


If this seem to problematic, I guess I can nuke the rest of vbox 5.1.6 from testing

OK here on 4.4.22-desktop-1.mga5 x86_64 host with

  - Intel(R) Core(TM) i5-3550
  - Radeon HD 7850
  - Atheros AR8161 Gigabit Ethernet

and guests:

x86_64  kernel 4.4.16-desktop-1  Mageia 5.1 Live GNOME DVD (UEFI boot)
i586    kernel 4.4.16-desktop-1  Mageia 5.1 Live GNOME DVD (legacy boot)

Could we have a couple other tests (one on i586 and one on x86_64) would be nice to ensure we're good to go with the new kmods for vbox 5.1.2?

FWIW, tested the 32-bit server kernel on my brother's computer, AMD Sempron 3100+ processor, 2GB RAM. Everything seems to work OK. The server kernel has always worked well on this computer. However, as VirtualBox is not installed on this machine, it is no doubt of limited help with regard to the new kmods.

I created a new Mageia 5 32-bit install on a Dell Dimension E310 (64-bit capable P4 processor, 2GB RAM, onboard Intel graphics), updated, then installed VirtualBox 5.1.2, and created a Mageia 5 32-bit guest. (Horribly slow, but it does work.) I then updated to the 4.4.22 desktop kernel, and tried VirtualBox again.

All went well. No problems noted.

Also, the 32-bit install on my Athlon X2 computer has been updated and downgraded again so many times lately that I wasn't sure if maybe I had missed rolling back a package that needed to be done for a valid test. So, I did a new 32-bit install on that hardware, too. Following the same procedure used with the Dell hardware above, except that I used an existing Mageia guest, I eventually updated to the 4.4.22 server kernel. All went well there, too.

I'd say we are good to go (thanks Thomas for the last extensive tests) - I'll leave it to QA members more active than me to confirm and put the validated_update keyword though.

Whiteboard: MGA5-64-OK advisory => MGA5-32-OK MGA5-64-OK advisory

An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGASA-2016-0345.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED