So this one should be in good shape for the 4.14 upgrade... The prebuilt kmods will be added later when virtualbox and xtables-addons bugs are validated and pushed... Advisory to follow later... SRPMS: kernel-4.14.5-1.mga6.src.rpm kernel-userspace-headers-4.14.5-1.mga6.src.rpm i586: cpupower-4.14.5-1.mga6.i586.rpm cpupower-devel-4.14.5-1.mga6.i586.rpm kernel-desktop-4.14.5-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-4.14.5-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-devel-4.14.5-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-devel-latest-4.14.5-1.mga6.i586.rpm kernel-desktop586-latest-4.14.5-1.mga6.i586.rpm kernel-desktop-devel-4.14.5-1.mga6-1-1.mga6.i586.rpm kernel-desktop-devel-latest-4.14.5-1.mga6.i586.rpm kernel-desktop-latest-4.14.5-1.mga6.i586.rpm kernel-doc-4.14.5-1.mga6.noarch.rpm kernel-server-4.14.5-1.mga6-1-1.mga6.i586.rpm kernel-server-devel-4.14.5-1.mga6-1-1.mga6.i586.rpm kernel-server-devel-latest-4.14.5-1.mga6.i586.rpm kernel-server-latest-4.14.5-1.mga6.i586.rpm kernel-source-4.14.5-1.mga6-1-1.mga6.noarch.rpm kernel-source-latest-4.14.5-1.mga6.noarch.rpm kernel-userspace-headers-4.14.5-1.mga6.i586.rpm perf-4.14.5-1.mga6.i586.rpm x86_64: cpupower-4.14.5-1.mga6.x86_64.rpm cpupower-devel-4.14.5-1.mga6.x86_64.rpm kernel-desktop-4.14.5-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-devel-4.14.5-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-devel-latest-4.14.5-1.mga6.x86_64.rpm kernel-desktop-latest-4.14.5-1.mga6.x86_64.rpm kernel-doc-4.14.5-1.mga6.noarch.rpm kernel-server-4.14.5-1.mga6-1-1.mga6.x86_64.rpm kernel-server-devel-4.14.5-1.mga6-1-1.mga6.x86_64.rpm kernel-server-devel-latest-4.14.5-1.mga6.x86_64.rpm kernel-server-latest-4.14.5-1.mga6.x86_64.rpm kernel-source-4.14.5-1.mga6-1-1.mga6.noarch.rpm kernel-source-latest-4.14.5-1.mga6.noarch.rpm kernel-userspace-headers-4.14.5-1.mga6.x86_64.rpm perf-4.14.5-1.mga6.x86_64.rpm
Depends on: (none) => 22100, 22147, 22148, 22149, 22150, 22152, 22164
Installed these packages and all others associated with the desktop kernel 4.14.5 update on a 64-bit system on my HP Probook 6550b. (i3, 8GB, Intel graphics, Intel wifi) The idea was to simulate a user getting these updates all at once. All packages installed cleanly, and everything seems to be functioning as it should. Common apps (Firefox, GIMP, vlc) all work.
CC: (none) => andrewsfarm
Installed all the relevant kernel packages after separate installation of firmware and wifi updates. $ drakboot --boot to sort out the system partitions then rebooted. NFS shares had to be mounted manually otherwise everything seemed to be normal. System: Host: markab Kernel: 4.14.5-desktop-1.mga6 x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Mageia 6 mga6 CPU: Quad core Intel Core i7-5700HQ (-HT-MCP-) speed/max: 2693/3500 MHz Machine: Device: laptop System: GIGABYTE product: X5 Mobo: GIGABYTE model: X5 Graphics: Card-1: NVIDIA GM204M [GeForce GTX 965M] Card-2: NVIDIA GM204M [GeForce GTX 965M] Display Server: Mageia X.org 119.5 drivers: nvidia,v4l Resolution: 2880x1620@59.96hz GLX Renderer: GeForce GTX 965M/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 384.98 RAM: 15.62 GB Single GPU mode. glmark2 score 3031 - par for the course. $ stress -c 3 -t 30 $ stress -m 4 -t 30 $ stress -d 4 -t 30 $ stress -i 5 -t 30 No complaints except from the fans. Played a music video using mplayer and a bluetooth connection to a soundbar. Good for x86_64 here.
CC: (none) => tarazed25
After installing the new nvidia340 driver, I updated the firmware and all other appropriate packages related to the 4.14.5 server kernel update, on 64-bit and 32-bit systems on the same hardware: ASRock motherboard, AMD Athlon X2 7750 processor, 8GB RAM, nvidia 9800GT graphics, Atheros AR9485 wifi adapter. And, I executed the "dracut -f" command on each system. After the reboot, both systems seemed to be running fine. No regressions noted.
On mga6-64 packages installed cleanly: - cpupower-4.14.5-1.mga6.x86_64 - dkms-virtualbox-5.2.2-1.mga6.noarch - kernel-desktop-4.14.5-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-4.14.5-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-latest-4.14.5-1.mga6.x86_64 - kernel-desktop-latest-4.14.5-1.mga6.x86_64 - kernel-userspace-headers-4.14.5-1.mga6.x86_64 - lib64bzip2-devel-1.0.6-10.mga6.x86_64 - lib64elfutils-devel-0.169-1.mga6.x86_64 - lib64lzma-devel-5.2.3-1.mga6.x86_64 - lib64zlib-devel-1.2.11-4.1.mga6.x86_64 - lib64zlib1-1.2.11-4.1.mga6.x86_64 system rebooted normally uname -r 4.14.5-desktop-1.mga6 and seems to be running OK However when I try to launch vbox I see: Access denied to /usr/lib64/virtualbox/Virtualbox There is in fact no such file on my system The module seems to be installed correctly: dkms status -m virtualbox virtualbox, 5.2.2-1.mga6, 4.9.56-desktop-1.mga6, x86_64: installed virtualbox, 5.2.2-1.mga6, 4.14.5-desktop-1.mga6, x86_64: installed virtualbox, 5.2.2-1.mga6, 4.9.56-desktop-1.mga6, x86_64: installed-binary from 4.9.56-desktop-1.mga6 Any ideas as to what is wrong? Possible solutions?
CC: (none) => jim
(In reply to James Kerr from comment #4) > On mga6-64 > Access denied to /usr/lib64/virtualbox/Virtualbox > > There is in fact no such file on my system > The panel link that I was using to launch vbox must have become corrupted somehow. Launching from the menu and a newly created panel link now work correctly. So a plasma glitch?
vbox and client (mga6-32) now working correctly: This update looks good for mga6-64 on this system: Dell product: Precision Tower 3620 Mobo: Dell model: 09WH54 Card: Intel HD Graphics 530 CPU: Quad core Intel Core i7-6700 (-HT-MCP-) PC-BIOS (legacy) boot GPT partitions
4.9.56-desktop-1.mga6 :: x86_64 Updates: - cpupower-4.14.4-1.mga6.x86_64 - dkms-virtualbox-5.2.2-1.mga6.noarch - kernel-desktop-4.14.4-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-4.14.4-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-latest-4.14.4-1.mga6.x86_64 - kernel-desktop-latest-4.14.4-1.mga6.x86_64 - kernel-doc-4.14.4-1.mga6.noarch - kernel-source-4.14.4-1.mga6-1-1.mga6.noarch - kernel-source-latest-4.14.4-1.mga6.noarch - kernel-userspace-headers-4.14.4-1.mga6.x86_64 - perf-4.14.4-1.mga6.x86_64 $ sudo urpmi cpupower-devel $ drakboot --boot $ reboot Rebooted to working desktop. System: Host: difda Kernel: 4.14.4-desktop-1.mga6 x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Mageia 6 mga6 CPU: Quad core Intel Core i7-4790 (-HT-MCP-) speed/max: 3599/4000 MHz RAM: 31.37 GB Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 NFS shares OK. Ran stress tests and hit problems. The cpu and memory tests ran fine but the disk read/write test failed to terminate and could not be killed from the commandline. The io tests also failed to terminate. Had to logout and reboot. Tried $ stress -d 1 -t 10 and that failed to terminate. Killed the process but it respawned immediately. By watching the process id it could be seen that the process did terminate but then respawned with another pid. This actually required a cold boot for recovery. Could I ask other testers who have installed this kernel to try the stress test above and report back? You might have to install stress first. Meanwhile I will try other partitions with earlier kernels, just to confirm that the machine itself is not damaged.
Continuing from comment 7. Moved to another partition after checking that stress -d ran OK on mga5. Installed the new firmware, virtualbox and the 4.14.4.1 kernel and tried the stress test again. It failed as before. Ran ksysguard and noticed that akonadi was running several processes. Now I never use akonadi - don't know what it was doing there. Removed it from the system and tried the stress test again. It worked fine with one hog. Ran it with 4 and it failed to terminate. Checked the processes and found many instances of akonadi running. Removed all traces of akonadi software from the system and rebooted. Still no luck. stress -d fails to terminate.
Now I see that the kernel has morphed to 4.14.5.1 $ kernelinfo System: Host: difda Kernel: 4.14.5-desktop-1.mga6 x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Mageia 6 mga6 Machine: Device: desktop Mobo: MSI model: Z97-G43 (MS-7816) v: 3.0 UEFI: American Megatrends v: V17.8 date: 12/24/2014 Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Mageia 6 : x86_64 : kernel-desktop-4.9.56-1 kernel-firmware already updated. Updated kernel. Rebooted to Mate desktop. System: Host: belexeuli Kernel: 4.14.5-desktop-1.mga6 x86_64 (64 bit) Mobo: Alienware model: 08PG26 v: A00 CPU: Quad core Intel Core i7-2600 (-HT-MCP-) speed/max: 3392/3800 MHz RAM: 7.69 GB Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 Graphics: Card-2: NVIDIA GF114 [GeForce GTX 555] GLX Version: 4.5.0 NVIDIA 384.98 Passed stress tests and glmark2. Mate desktop running fine. OK for 64 bits on Dell Alienware X51.
This kernel has been running on this machine for a while and no problems are apparent. System: Host: vega Kernel: 4.14.5-desktop-1.mga6 x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Mageia 6 mga6 CPU: Quad core Intel Core i7-4790K (-HT-MCP-) speed/max: 4000/4400 MHz Machine: Device: desktop Mobo: Gigabyte model: G1.Sniper Z97 v: x.x UEFI: American Megatrends v: F6 date: 05/30/2014 Ran the stress tests - all functioned properly.
In a Vbox client, M6, Plasma & Mate, 64bit Testing: kernel-desktop-latest vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:55:31 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.1.30-1.mga6.x86_64 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Installed kernel-desktop-latest vboxadditions-kernel-desktop-latest from updates testing Reboot client Does not boot back to a working desktop as a Vbox client. This has occurred both with Plasma and Mate
CC: (none) => wilcal.int
In a Vbox client, M6, Plasma, 32bit Testing: kernel-desktop-latest vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:53:48 UTC 2017 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.i586 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.1.30-1.mga6.i586 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Installed kernel-desktop-latest vboxadditions-kernel-desktop-latest from updates testing Installing: - btrfs-progs-4.14-2.mga6.i586 - glibc-2.22-26.mga6.i586 - iwlwifi-firmware-20171206-1.mga6.nonfree.noarch - kernel-desktop-4.14.5-1.mga6-1-1.mga6.i586 - kernel-desktop-latest-4.14.5-1.mga6.i586 - kernel-firmware-nonfree-20171206-1.mga6.nonfree.noarch - libbtrfs0-4.14-2.mga6.i586 - libzstd1-1.3.2-1.mga6.i586 - radeon-firmware-20171205-1.mga6.nonfree.noarch - vboxadditions-kernel-4.9.56-desktop-1.mga6-5.2.2-1.mga6.i586 - vboxadditions-kernel-desktop-latest-5.2.2-1.mga6.i586 Reboot client Does not boot back to a working desktop as a Vbox client.
From comment#0 "The prebuilt kmods will be added later when virtualbox and xtables-addons bugs are validated and pushed..." Until then, you need to use dkms to build the kernel modules
(In reply to James Kerr from comment #14) > "The prebuilt kmods will be added later when virtualbox and xtables-addons > bugs are validated and pushed..." > > Until then, you need to use dkms to build the kernel modules So this can't be tested, or used, as a Vbox client until that process is completed?
It should be possible if you install dkms-vboxadditions and kernel-desktop-devel-latest in the client
Lets talk about this at the QA meeting tomorrow. Thanks for the help.
On real hardware, M6, Plasma, 64-bit initial install: kernel-desktop-latest kernel-desktop-devel-latest dkms-nvidia-current [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:55:31 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi kernel-desktop-devel-latest Package kernel-desktop-devel-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-nvidia-current Package dkms-nvidia-current-384.98-1.mga6.nonfree.x86_64 is already installed [wilcal@localhost ~]$ 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_drm, nvidia_current install: kernel-desktop-latest kernel-desktop-devel-latest dkms-nvidia-current from updates_testing The following 17 packages are going to be installed: - btrfs-progs-4.14-2.mga6.x86_64 - glibc-2.22-26.mga6.x86_64 - glibc-devel-2.22-26.mga6.x86_64 - iwlwifi-firmware-20171206-1.mga6.nonfree.noarch - kernel-desktop-4.14.5-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-4.14.5-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-latest-4.14.5-1.mga6.x86_64 - kernel-desktop-latest-4.14.5-1.mga6.x86_64 - kernel-firmware-nonfree-20171206-1.mga6.nonfree.noarch - lib64btrfs0-4.14-2.mga6.x86_64 - lib64bzip2-devel-1.0.6-10.mga6.x86_64 - lib64elfutils-devel-0.169-1.mga6.x86_64 - lib64lzma-devel-5.2.3-1.mga6.x86_64 - lib64zlib-devel-1.2.11-4.1.mga6.x86_64 - lib64zlib1-1.2.11-4.1.mga6.x86_64 - lib64zstd1-1.3.2-1.mga6.x86_64 - radeon-firmware-20171205-1.mga6.nonfree.noarch [root@localhost wilcal]# uname -a Linux localhost 4.14.5-desktop-1.mga6 #1 SMP Sun Dec 10 15:44:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.14.5-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi kernel-desktop-devel-latest Package kernel-desktop-devel-latest-4.14.5-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-nvidia-current Package dkms-nvidia-current-384.98-1.mga6.nonfree.x86_64 is already installed [wilcal@localhost ~]$ 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_drm, nvidia_current This all looks good to me. Clearly we've got a Vbox wrinkle here. 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)
Testing M6/64 real hardware AMD/ATI/Radeon video Updated all at the same time, some of which relate to other bugs but recording them here for reference: - btrfs-progs-4.14-2.mga6.x86_64 - cpupower-4.14.5-1.mga6.x86_64 - iwlwifi-firmware-20171206-1.mga6.nonfree.noarch - kernel-desktop-4.14.5-1.mga6-1-1.mga6.x86_64 - kernel-desktop-latest-4.14.5-1.mga6.x86_64 - kernel-firmware-nonfree-20171206-1.mga6.nonfree.noarch - kernel-tmb-desktop-4.14.5-1.mga6-1-1.mga6.x86_64 - kernel-tmb-desktop-latest-4.14.5-1.mga6.x86_64 - kernel-userspace-headers-4.14.5-1.mga6.x86_64 - lib64btrfs0-4.14-2.mga6.x86_64 - lib64zstd1-1.3.2-1.mga6.x86_64 - radeon-firmware-20171205-1.mga6.nonfree.noarch - xfsprogs-4.14.0-1.mga6.x86_64 I do *not* use WiFi, BTRFS, XFS, so those new pkgs should not be exercised. I will report back after re-boot and some usage.
CC: (none) => lewyssmith
Testing M6/84 $ uname -r 4.14.5-desktop-1.mga6 Well, after a variety of usage testing updates etc, video DVD, sound OK but a bit weak; also the following tests ex comments 2 & 7 (thank you Len for the edification): $ stress -c 3 -t 30 stress: info: [13716] dispatching hogs: 3 cpu, 0 io, 0 vm, 0 hdd stress: info: [13716] successful run completed in 30s $ stress -m 4 -t 30 stress: info: [14054] dispatching hogs: 0 cpu, 0 io, 4 vm, 0 hdd stress: info: [14054] successful run completed in 30s $ stress -d 4 -t 30 stress: info: [14252] dispatching hogs: 0 cpu, 0 io, 0 vm, 4 hdd stress: info: [14252] successful run completed in 33s $ stress -i 5 -t 30 stress: info: [14851] dispatching hogs: 0 cpu, 5 io, 0 vm, 0 hdd stress: info: [14851] successful run completed in 30s $ stress -d 1 -t 10 stress: info: [16650] dispatching hogs: 0 cpu, 0 io, 0 vm, 1 hdd stress: info: [16650] successful run completed in 11s this looks OK for me. Accepting the pending VBox problem resolution (comments 13-16), Lens's problem comments 7-8 were for 4.14.4.1 ; from C9 onwards with 4.14.5.1 - what we are issuing - all his tests were good. This is OK for 64-bit.
Whiteboard: (none) => MAG6-64-OK
Whiteboard: MAG6-64-OK => MGA6-64-OK
Created attachment 9845 [details] log from failed dkms build of vboxadditions Using dkms instead of the pre-built kernel modules (needed for some kernels) fails under virtualbox. Attching the make.log
CC: (none) => davidwhodgins
(In reply to Dave Hodgins from comment #21) > Created attachment 9845 [details] > log from failed dkms build of vboxadditions > > Using dkms instead of the pre-built kernel modules (needed for some kernels) > fails under virtualbox. Attching the make.log wrong dkms package... you need 5.2.2 series
Thanks. Now using ... # rpm -qa|grep dkms dkms-2.0.19-39.mga6 dkms-vboxadditions-5.2.2-1.mga6 dkms-minimal-2.0.19-39.mga6 Found that X still fails to start. Works ok if I add nokmsboot With 4.9.56-desktop-1.mga6 and prior, X works without nokmsboot With 4.14.5-desktop-1.mga6 X requires nokmsboot This is in a Mageia 6 vb x86_64 guest on a Mageia 5 x86_64 host. Doubt it will make any difference if I switch to Mageia 6 on the host.
I do. the vboxadditions and the x11 vboxvideo package should match the host.... So now you have a 5.1.30 host with 5.2.x driver set in the guest... and upstream Vbox does not guarantee ABI/API stability in 5.1 series... that is only coming with the vbox code landing in upstream kernels... heading for 4.15/16/...
Confirmed. Using Mageia 6 on the host with the vb update nokmsboot is not required in the guest. I'll go ahead and validate the update for vb on Mageia 6, but what to do with these kernels? I see three options. 1. Update vb on Mageia 5 too. 2. Hold the kernel update till Mageia 5 is eol. 3. Validate and release the updated kernels for Mageia 6, knowing that it will break X for Mageia 6 guests on Mageia 5 hosts and try to inform users that they need to add nokmsboot to the kernel options for Mageia 6 guests, until they update to Mageia 6 on the host. My preference would be option 1.
All kernels tested on both arches, so ready to validate once the action per comment 25 is decided on.
Virtualbox kmods now built for this kernel: SRPMS: kmod-vboxadditions-5.2.2-2.mga6.src.rpm kmod-virtualbox-5.2.2-2.mga6.src.rpm i586: vboxadditions-kernel-4.14.5-desktop-1.mga6-5.2.2-2.mga6.i586.rpm vboxadditions-kernel-4.14.5-desktop586-1.mga6-5.2.2-2.mga6.i586.rpm vboxadditions-kernel-4.14.5-server-1.mga6-5.2.2-2.mga6.i586.rpm vboxadditions-kernel-desktop586-latest-5.2.2-2.mga6.i586.rpm vboxadditions-kernel-desktop-latest-5.2.2-2.mga6.i586.rpm vboxadditions-kernel-server-latest-5.2.2-2.mga6.i586.rpm virtualbox-kernel-4.14.5-desktop-1.mga6-5.2.2-2.mga6.i586.rpm virtualbox-kernel-4.14.5-desktop586-1.mga6-5.2.2-2.mga6.i586.rpm virtualbox-kernel-4.14.5-server-1.mga6-5.2.2-2.mga6.i586.rpm virtualbox-kernel-desktop586-latest-5.2.2-2.mga6.i586.rpm virtualbox-kernel-desktop-latest-5.2.2-2.mga6.i586.rpm virtualbox-kernel-server-latest-5.2.2-2.mga6.i586.rpm x86_64: vboxadditions-kernel-4.14.5-desktop-1.mga6-5.2.2-2.mga6.x86_64.rpm vboxadditions-kernel-4.14.5-server-1.mga6-5.2.2-2.mga6.x86_64.rpm vboxadditions-kernel-desktop-latest-5.2.2-2.mga6.x86_64.rpm vboxadditions-kernel-server-latest-5.2.2-2.mga6.x86_64.rpm virtualbox-kernel-4.14.5-desktop-1.mga6-5.2.2-2.mga6.x86_64.rpm virtualbox-kernel-4.14.5-server-1.mga6-5.2.2-2.mga6.x86_64.rpm virtualbox-kernel-desktop-latest-5.2.2-2.mga6.x86_64.rpm virtualbox-kernel-server-latest-5.2.2-2.mga6.x86_64.rpm
xtables-addons + kmods still need to be validated fro 4.9 series before I can build the kmods for this kernel: https://bugs.mageia.org/show_bug.cgi?id=22152
As already stated when we extended mga5 support, there will be no vbox 5.2 in mga5.... thats a way too huge feature update for a release that gets eol in ~10 days... Delaying kernel 4.14 series until mga5 is eol means invalidating all currently tested kernels as I then will rebuild new kernels with more upstream fixes all over.
(In reply to Thomas Backlund from comment #27) > Virtualbox kmods now built for this kernel: > > So, some questions: I have already updated some systems to the 4.14.5 kernel, using dkms-virtualbox to build the kernel modules locally, and they seem to be working just fine. Now, I realize that I don't need BOTH the pre-built modules and the locally-built ones to run virtualbox, but what happens if I now install the pre-built kmods? Which modules will be used? Is there any reason to avoid having both? Is it a valid test if the pre-built ones are just going to sit there, unused?
(In reply to Thomas Andrews from comment #30) > (In reply to Thomas Backlund from comment #27) > > Virtualbox kmods now built for this kernel: > > > > > So, some questions: > > I have already updated some systems to the 4.14.5 kernel, using > dkms-virtualbox to build the kernel modules locally, and they seem to be > working just fine. Now, I realize that I don't need BOTH the pre-built > modules and the locally-built ones to run virtualbox, but what happens if I > now install the pre-built kmods? Which modules will be used? Is there any > reason to avoid having both? Is it a valid test if the pre-built ones are > just going to sit there, unused? the dkms package takes priority (in case someone patches the code but forgets bump rel) If you dont use kernel-linus or kernel-tmb, you dont need the dkms packages, only the prebuilt ones.
Advisory, also added to svn: type: security subject: kernel update provides 4.14 series and fixes security vulnerabilities CVE: - CVE-2017-0786 - CVE-2017-7518 - CVE-2017-12188 - CVE-2017-12190 - CVE-2017-12193 - CVE-2017-13080 - CVE-2017-15115 - CVE-2017-15265 - CVE-2017-15299 - CVE-2017-16939 - CVE-2017-16994 src: 6: core: - kernel-4.14.5-1.mga6 - kernel-userspace-headers-4.14.5-1.mga6 - kmod-vboxadditions-5.2.2-2.mga6 - kmod-virtualbox-5.2.2-2.mga6 - kmod-xtables-addons-2.13-4.mga6 - wireguard-tools-0.0.20171127-1.mga6 description: | This kernel update provides an upgrade to the 4.14 longterm branch, currently based on 4.14.5. It also fixes atleast the following security issues: An elevation of privilege vulnerability in the Broadcom wi-fi driver (CVE-2017-0786). Linux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM) support is vulnerable to an incorrect debug exception(#DB) error. It could occur while emulating a syscall instruction. A user/process inside guest could use this flaw to potentially escalate their privileges inside guest. Linux guests are not affected.(CVE-2017-7518). arch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested virtualisation is used, does not properly traverse guest pagetable entries to resolve a guest virtual address, which allows L1 guest OS users to execute arbitrary code on the host OS or cause a denial of service (incorrect index during page walking, and host OS crash), aka an "MMU potential stack buffer overrun" (CVE-2017-12188). The bio_map_user_iov and bio_unmap_user functions in block/bio.c in the Linux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O vector has small consecutive buffers belonging to the same page. The bio_add_pc_page function merges them into one, but the page reference is never dropped. This causes a memory leak and possible system lockup (exploitable against the host OS by a guest OS user, if a SCSI disk is passed through to a virtual machine) due to an out-of-memory condition (CVE-2017-12190). The assoc_array_insert_into_terminal_node function in lib/assoc_array.c in the Linux kernel before 4.13.11 mishandles node splitting, which allows local users to cause a denial of service (NULL pointer dereference and panic) via a crafted application, as demonstrated by the keyring key type, and key addition and link creation operations (CVE-2017-12193). Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group Temporal Key (GTK) during the group key handshake, allowing an attacker within radio range to replay frames from access points to clients (CVE-2017-13080). The sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel before 4.14 does not check whether the intended netns is used in a peel-off action, which allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls (CVE-2017-15115). Race condition in the ALSA subsystem in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted /dev/snd/seq ioctl calls, related to sound/core/seq/seq_clientmgr.c and sound/core/seq/seq_ports.c (CVE-2017-15265) The KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of add_key for a key that already exists but is uninstantiated, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a crafted system call (CVE-2017-15299). The XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux kernel before 4.13.11 allows local users to gain privileges or cause a denial of service (use-after-free) via a crafted SO_RCVBUF setsockopt system call in conjunction with XFRM_MSG_GETPOLICY Netlink messages (CVE-2017-16939). The walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel before 4.14.2 mishandles holes in hugetlb ranges, which allows local users to obtain sensitive information from uninitialized kernel memory via crafted use of the mincore() system call (CVE-2017-16994). This update also adds support for WireGuard VPN. For other changes in this update, read the referenced changelogs. references: - https://bugs.mageia.org/show_bug.cgi?id=22166 - https://kernelnewbies.org/Linux_4.10 - https://kernelnewbies.org/Linux_4.11 - https://kernelnewbies.org/Linux_4.12 - https://kernelnewbies.org/Linux_4.13 - https://kernelnewbies.org/Linux_4.14 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.1 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.2 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.3 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.4 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.5 - https://www.wireguard.com/
Keywords: (none) => advisory
Created a 64-bit Mageia 6 Xfce guest on a 64-bit Mageia 6 host that had already been updated to the 4.14.5 desktop kernel, with locally-built Virtualbox 5.2.2 kernel modules. After getting all updates, including the new virtualbox 5.2.2 guest additions for the 4.9.56 kernel, and rebooting, I updated the guest to the the 4.14.5 desktop kernel and associated packages, including the new guest additions module. After the reboot, all seems well. No problems noted.
Pulling the plug on this one... Turns out there is a potential bug cripling atleast some Lenovo laptops in this kernel
Whiteboard: MGA6-64-OK => (none)Assignee: qa-bugs => tmbKeywords: (none) => feedback
Depends on: (none) => 22256
Updated advisory in svn for 4.14.9 series: type: security subject: kernel update provides 4.14 series and fixes security vulnerabilities CVE: - CVE-2017-0786 - CVE-2017-0861 - CVE-2017-7518 - CVE-2017-12188 - CVE-2017-12190 - CVE-2017-12193 - CVE-2017-13080 - CVE-2017-15115 - CVE-2017-15265 - CVE-2017-15299 - CVE-2017-16939 - CVE-2017-16994 - CVE-2017-16995 - CVE-2017-16996 - CVE-2017-17741 - CVE-2017-17852 - CVE-2017-17853 - CVE-2017-17854 - CVE-2017-17855 - CVE-2017-17856 - CVE-2017-17857 - CVE-2017-17862 - CVE-2017-17863 - CVE-2017-17864 - CVE-2017-1000407 src: 6: core: - kernel-4.14.9-1.mga6 - kernel-userspace-headers-4.14.9-1.mga6 - kmod-vboxadditions-5.2.2-4.mga6 - kmod-virtualbox-5.2.2-4.mga6 - kmod-xtables-addons-2.13-6.mga6 - wireguard-tools-0.0.20171221-1.mga6 description: | This kernel update provides an upgrade to the 4.14 longterm branch, currently based on 4.14.9. It also fixes atleast the following security issues: An elevation of privilege vulnerability in the Broadcom wi-fi driver (CVE-2017-0786). Use-after-free vulnerability in the snd_pcm_info function in the ALSA subsystem in the Linux kernel allows attackers to gain privileges via unspecified vectors (CVE-2017-0861). Linux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM) support is vulnerable to an incorrect debug exception(#DB) error. It could occur while emulating a syscall instruction. A user/process inside guest could use this flaw to potentially escalate their privileges inside guest. Linux guests are not affected.(CVE-2017-7518). arch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested virtualisation is used, does not properly traverse guest pagetable entries to resolve a guest virtual address, which allows L1 guest OS users to execute arbitrary code on the host OS or cause a denial of service (incorrect index during page walking, and host OS crash), aka an "MMU potential stack buffer overrun" (CVE-2017-12188). The bio_map_user_iov and bio_unmap_user functions in block/bio.c in the Linux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O vector has small consecutive buffers belonging to the same page. The bio_add_pc_page function merges them into one, but the page reference is never dropped. This causes a memory leak and possible system lockup (exploitable against the host OS by a guest OS user, if a SCSI disk is passed through to a virtual machine) due to an out-of-memory condition (CVE-2017-12190). The assoc_array_insert_into_terminal_node function in lib/assoc_array.c in the Linux kernel before 4.13.11 mishandles node splitting, which allows local users to cause a denial of service (NULL pointer dereference and panic) via a crafted application, as demonstrated by the keyring key type, and key addition and link creation operations (CVE-2017-12193). Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group Temporal Key (GTK) during the group key handshake, allowing an attacker within radio range to replay frames from access points to clients (CVE-2017-13080). The sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel before 4.14 does not check whether the intended netns is used in a peel-off action, which allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via crafted system calls (CVE-2017-15115). Race condition in the ALSA subsystem in the Linux kernel before 4.13.8 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted /dev/snd/seq ioctl calls, related to sound/core/seq/seq_clientmgr.c and sound/core/seq/seq_ports.c (CVE-2017-15265) The KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of add_key for a key that already exists but is uninstantiated, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a crafted system call (CVE-2017-15299). The XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux kernel before 4.13.11 allows local users to gain privileges or cause a denial of service (use-after-free) via a crafted SO_RCVBUF setsockopt system call in conjunction with XFRM_MSG_GETPOLICY Netlink messages (CVE-2017-16939). The walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel before 4.14.2 mishandles holes in hugetlb ranges, which allows local users to obtain sensitive information from uninitialized kernel memory via crafted use of the mincore() system call (CVE-2017-16994). The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension (CVE-2017-16995). kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging register truncation mishandling (CVE-2017-16996). The KVM implementation in the Linux kernel through 4.14.7 allows attackers to obtain potentially sensitive information from kernel memory, aka a write_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c and include/trace/events/kvm.h (CVE-2017-17741). kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging mishandling of 32-bit ALU ops (CVE-2017-17852). kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect BPF_RSH signed bounds calculations (CVE-2017-17853). kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (integer overflow and memory corruption) or possibly have unspecified other impact by leveraging unrestricted integer values for pointer arithmetic (CVE-2017-17854). kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging improper use of pointers in place of scalars (CVE-2017-17855). kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement (CVE-2017-17856). The check_stack_boundary function in kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging mishandling of invalid variable stack read operations (CVE-2017-17857). kernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores unreachable code, even though it would still be processed by JIT compilers. This behavior, also considered an improper branch-pruning logic issue, could possibly be used by local users for denial of service (CVE-2017-17862). kernel/bpf/verifier.c in the Linux kernel 4.9.x through 4.9.71 does not check the relationship between pointer values and the BPF stack, which allows local users to cause a denial of service (integer overflow or invalid memory access) or possibly have unspecified other impact (CVE-2017-17863). kernel/bpf/verifier.c in the Linux kernel before 4.14 mishandles states_equal comparisons between the pointer data type and the UNKNOWN_VALUE data type, which allows local users to obtain potentially sensitive address information, aka a "pointer leak" (CVE-2017-17864). The Linux Kernel 2.6.32 and later are affected by a denial of service, by flooding the diagnostic port 0x80 an exception can be triggered leading to a kernel panic (CVE-2017-1000407). This update also adds support for WireGuard VPN. For other changes in this update, read the referenced changelogs. references: - https://bugs.mageia.org/show_bug.cgi?id=22166 - https://kernelnewbies.org/Linux_4.10 - https://kernelnewbies.org/Linux_4.11 - https://kernelnewbies.org/Linux_4.12 - https://kernelnewbies.org/Linux_4.13 - https://kernelnewbies.org/Linux_4.14 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.1 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.2 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.3 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.4 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.5 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.6 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.7 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.8 - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.9 - https://www.wireguard.com/
Component: RPM Packages => SecurityAssignee: tmb => qa-bugsKeywords: feedback => (none)Summary: Update request: kernel 4.14 => Update request: kernel 4.14.9QA Contact: (none) => security
and the updated rpms list: SRPMS: kernel-4.14.9-1.mga6.src.rpm kernel-userspace-headers-4.14.9-1.mga6.src.rpm kmod-vboxadditions-5.2.2-4.mga6.src.rpm kmod-virtualbox-5.2.2-4.mga6.src.rpm kmod-xtables-addons-2.13-6.mga6.src.rpm wireguard-tools-0.0.20171221-1.mga6.src.rpm i586: cpupower-4.14.9-1.mga6.i586.rpm cpupower-devel-4.14.9-1.mga6.i586.rpm kernel-desktop-4.14.9-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-4.14.9-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-devel-4.14.9-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-devel-latest-4.14.9-1.mga6.i586.rpm kernel-desktop586-latest-4.14.9-1.mga6.i586.rpm kernel-desktop-devel-4.14.9-1.mga6-1-1.mga6.i586.rpm kernel-desktop-devel-latest-4.14.9-1.mga6.i586.rpm kernel-desktop-latest-4.14.9-1.mga6.i586.rpm kernel-doc-4.14.9-1.mga6.noarch.rpm kernel-server-4.14.9-1.mga6-1-1.mga6.i586.rpm kernel-server-devel-4.14.9-1.mga6-1-1.mga6.i586.rpm kernel-server-devel-latest-4.14.9-1.mga6.i586.rpm kernel-server-latest-4.14.9-1.mga6.i586.rpm kernel-source-4.14.9-1.mga6-1-1.mga6.noarch.rpm kernel-source-latest-4.14.9-1.mga6.noarch.rpm kernel-userspace-headers-4.14.9-1.mga6.i586.rpm perf-4.14.9-1.mga6.i586.rpm vboxadditions-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.i586.rpm vboxadditions-kernel-4.14.9-desktop586-1.mga6-5.2.2-4.mga6.i586.rpm vboxadditions-kernel-4.14.9-server-1.mga6-5.2.2-4.mga6.i586.rpm vboxadditions-kernel-desktop586-latest-5.2.2-4.mga6.i586.rpm vboxadditions-kernel-desktop-latest-5.2.2-4.mga6.i586.rpm vboxadditions-kernel-server-latest-5.2.2-4.mga6.i586.rpm virtualbox-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.i586.rpm virtualbox-kernel-4.14.9-desktop586-1.mga6-5.2.2-4.mga6.i586.rpm virtualbox-kernel-4.14.9-server-1.mga6-5.2.2-4.mga6.i586.rpm virtualbox-kernel-desktop586-latest-5.2.2-4.mga6.i586.rpm virtualbox-kernel-desktop-latest-5.2.2-4.mga6.i586.rpm virtualbox-kernel-server-latest-5.2.2-4.mga6.i586.rpm xtables-addons-kernel-4.14.9-desktop-1.mga6-2.13-6.mga6.i586.rpm xtables-addons-kernel-4.14.9-desktop586-1.mga6-2.13-6.mga6.i586.rpm xtables-addons-kernel-4.14.9-server-1.mga6-2.13-6.mga6.i586.rpm xtables-addons-kernel-desktop586-latest-2.13-6.mga6.i586.rpm xtables-addons-kernel-desktop-latest-2.13-6.mga6.i586.rpm xtables-addons-kernel-server-latest-2.13-6.mga6.i586.rpm wireguard-tools-0.0.20171221-1.mga6.i586.rpm x86_64: cpupower-4.14.9-1.mga6.x86_64.rpm cpupower-devel-4.14.9-1.mga6.x86_64.rpm kernel-desktop-4.14.9-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-devel-4.14.9-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-devel-latest-4.14.9-1.mga6.x86_64.rpm kernel-desktop-latest-4.14.9-1.mga6.x86_64.rpm kernel-doc-4.14.9-1.mga6.noarch.rpm kernel-server-4.14.9-1.mga6-1-1.mga6.x86_64.rpm kernel-server-devel-4.14.9-1.mga6-1-1.mga6.x86_64.rpm kernel-server-devel-latest-4.14.9-1.mga6.x86_64.rpm kernel-server-latest-4.14.9-1.mga6.x86_64.rpm kernel-source-4.14.9-1.mga6-1-1.mga6.noarch.rpm kernel-source-latest-4.14.9-1.mga6.noarch.rpm kernel-userspace-headers-4.14.9-1.mga6.x86_64.rpm perf-4.14.9-1.mga6.x86_64.rpm vboxadditions-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.x86_64.rpm vboxadditions-kernel-4.14.9-server-1.mga6-5.2.2-4.mga6.x86_64.rpm vboxadditions-kernel-desktop-latest-5.2.2-4.mga6.x86_64.rpm vboxadditions-kernel-server-latest-5.2.2-4.mga6.x86_64.rpm virtualbox-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.x86_64.rpm virtualbox-kernel-4.14.9-server-1.mga6-5.2.2-4.mga6.x86_64.rpm virtualbox-kernel-desktop-latest-5.2.2-4.mga6.x86_64.rpm virtualbox-kernel-server-latest-5.2.2-4.mga6.x86_64.rpm xtables-addons-kernel-4.14.9-desktop-1.mga6-2.13-6.mga6.x86_64.rpm xtables-addons-kernel-4.14.9-server-1.mga6-2.13-6.mga6.x86_64.rpm xtables-addons-kernel-desktop-latest-2.13-6.mga6.x86_64.rpm xtables-addons-kernel-server-latest-2.13-6.mga6.x86_64.rpm wireguard-tools-0.0.20171221-1.mga6.x86_64.rpm
In a Vbox client, M6, Plasma & Mate, 64bit Testing: kernel-desktop-latest vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:53:48 UTC 2017 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.i586 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-1.mga6.i586 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Installed kernel-desktop-latest vboxadditions-kernel-desktop-latest from updates testing Reboot client [root@localhost wilcal]# uname -a Linux localhost 4.14.9-desktop-1.mga6 #1 SMP Mon Dec 25 17:20:31 UTC 2017 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.14.9-1.mga6.i586 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-4.mga6.i586 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Test platform: Intel Core i5-4460 Haswell Quad-Core 3.2GHz LGA 115 Gigabyte GA-B85M-D3H LGA 1150 Intel B85 chipset Integrated Graphics Processor - Intel HD Graphics support Audito chipset - Realtek ALC892, 7.1 channels Corsair Vengeance 8GB ( 2 x 4GB ) 240-pin DDR3 SDRAM 1600
Correction in Comment 37: is: In a Vbox client, M6, Plasma & Mate, 64bit s/b: In a Vbox client, M6, Plasma & Mate, 32bit
Had to change mirrors to find this. Installed all the packages except those server-related. Real hardware - UEFI. $ drakboot --boot Rebooted without problems. Working desktop. System: Host: vega Kernel: 4.14.9-desktop-1.mga6 x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Mageia 6 mga6 CPU: Quad core Intel Core i7-4790K (-HT-MCP-) speed/max: 4000/4400 MHz Machine: Device: desktop Mobo: Gigabyte model: G1.Sniper Z97 v: x.x UEFI: American Megatrends v: F6 date: 05/30/2014 Graphics: Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GK104 [GeForce GTX 770] Display Server: Mageia X.org 119.5 drivers: nvidia,v4l,intel Resolution: 2560x1440, 1024x768 GLX Renderer: GeForce GTX 770/PCIe/SSE2 GLX Version: 4.4.0 NVIDIA 340.104 Ran a few stress tests. Booted 32-bit mga5 in virtualbox. Networking and NFS OK. No problems yet.
In a Vbox client, M6, Plasma & Mate, 64bit Testing: kernel-desktop-latest vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:55:31 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-1.mga6.x86_64 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Installed kernel-desktop-latest vboxadditions-kernel-desktop-latest from updates testing Reboot client [root@localhost wilcal]# uname -a Linux localhost 4.14.9-desktop-1.mga6 #1 SMP Mon Dec 25 17:20:31 UTC 2017 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.14.9-1.mga6.i586 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-4.mga6.i586 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Test platform: Intel Core i5-4460 Haswell Quad-Core 3.2GHz LGA 115 Gigabyte GA-B85M-D3H LGA 1150 Intel B85 chipset Integrated Graphics Processor - Intel HD Graphics support Audito chipset - Realtek ALC892, 7.1 channels Corsair Vengeance 8GB ( 2 x 4GB ) 240-pin DDR3 SDRAM 1600
No regression for me on x86_64: i3-2330M
The following 25 packages are going to be installed: - btrfs-progs-4.14-2.mga6.x86_64 - gcc-5.4.0-5.mga6.x86_64 - gcc-cpp-5.4.0-5.mga6.x86_64 - glibc-devel-2.22-26.mga6.x86_64 - isl-0.16.1-1.mga6.x86_64 - kernel-desktop-4.14.9-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-4.14.9-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-latest-4.14.9-1.mga6.x86_64 - kernel-desktop-latest-4.14.9-1.mga6.x86_64 - kernel-firmware-nonfree-20171220-1.mga6.nonfree.noarch - kernel-userspace-headers-4.14.9-1.mga6.x86_64 - lib64btrfs0-4.14-2.mga6.x86_64 - lib64bzip2-devel-1.0.6-10.mga6.x86_64 - lib64elfutils-devel-0.169-1.mga6.x86_64 - lib64isl15-0.16.1-1.mga6.x86_64 - lib64lzma-devel-5.2.3-1.mga6.x86_64 - lib64mpc3-1.0.3-1.mga6.x86_64 - lib64ncurses-devel-6.0-8.mga6.x86_64 - lib64zlib-devel-1.2.11-4.1.mga6.x86_64 - lib64zstd1-1.3.2-1.mga6.x86_64 - libstdc++-devel-5.4.0-5.mga6.x86_64 - vboxadditions-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.x86_64 - vboxadditions-kernel-desktop-latest-5.2.2-4.mga6.x86_64 - virtualbox-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.x86_64 - virtualbox-kernel-desktop-latest-5.2.2-4.mga6.x86_64 224MB of additional disk space will be used. 137MB of packages will be retrieved. Is it ok to continue? $ uname -a Linux localhost 4.14.9-desktop-1.mga6 #1 SMP Mon Dec 25 15:27:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux RS780L [Radeon 3000] AMD Athlon(tm) II X3 450 Processor RS780/RS880 PCI to PCI bridge (int gfx) --- No regressions so far.
CC: (none) => brtians1
On real hardware, M6, Plasma, 64-bit initial install: kernel-desktop-latest virtualbox vboxadditions-kernel-desktop-latest dkms-virtualbox virtualbox-guest-additions virtualbox-kernel-desktop-latest x11-driver-video-vboxvideo kernel-desktop-devel-latest dkms-nvidia-current [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:55:31 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox Package virtualbox-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-virtualbox Package dkms-virtualbox-5.2.2-1.mga6.noarch is already installed [root@localhost wilcal]# urpmi virtualbox-guest-additions Package virtualbox-guest-additions-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox-kernel-desktop-latest Package virtualbox-kernel-desktop-latest-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi x11-driver-video-vboxvideo Package x11-driver-video-vboxvideo-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi kernel-desktop-devel-latest Package kernel-desktop-devel-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-nvidia-current Package dkms-nvidia-current-384.98-1.mga6.nonfree.x86_64 is already installed [wilcal@localhost ~]$ 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_drm, nvidia_current M6 i586 Xfce Live-DVD runs as a Vbox client. Boots to a working desktop. Common apps work. Screen sizes are correct. update: kernel-desktop-latest virtualbox vboxadditions-kernel-desktop-latest dkms-virtualbox virtualbox-guest-additions virtualbox-kernel-desktop-latest x11-driver-video-vboxvideo kernel-desktop-devel-latest dkms-nvidia-current from updates_testing [root@localhost wilcal]# uname -a Linux localhost 4.14.9-desktop-1.mga6 #1 SMP Mon Dec 25 15:27:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.14.9-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox Package virtualbox-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-4.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-virtualbox Package dkms-virtualbox-5.2.2-1.mga6.noarch is already installed [root@localhost wilcal]# urpmi virtualbox-guest-additions Package virtualbox-guest-additions-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox-kernel-desktop-latest Package virtualbox-kernel-desktop-latest-5.2.2-4.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi x11-driver-video-vboxvideo Package x11-driver-video-vboxvideo-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi kernel-desktop-devel-latest Package kernel-desktop-devel-latest-4.14.9-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-nvidia-current Package dkms-nvidia-current-384.98-2.mga6.nonfree.x86_64 is already installed [wilcal@localhost ~]$ 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_drm, nvidia_current M6 i586 Xfce LiveDVD still runs as a Vbox client. M6 x86_64 Gnome LiveDVD runs as a Vbox client. Boots to a working desktop. Common apps work. Screen sizes are correct. M6 x86_64 CI installs and runs as a Vbox client. Updates then reboots back to a working desktop. Screen sizes 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) Looks good
On real hardware, HP Probook 6550b, i3, 8GB, Intel graphics, Intel wifi. Kernel 4.14.5, previously under test, had been removed. Packages under test: cpupower-4.14.9-1.mga6.x86_64 - kernel-desktop-4.14.9-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-4.14.9-1.mga6-1-1.mga6.x86_64 - kernel-desktop-devel-latest-4.14.9-1.mga6.x86_64 - kernel-desktop-latest-4.14.9-1.mga6.x86_64 - kernel-userspace-headers-4.14.9-1.mga6.x86_64 - virtualbox-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.x86_64 - virtualbox-kernel-desktop-latest-5.2.2-4.mga6.x86_64 (other 4.14-related packages already installed from kernel 4.14.5 test) Boots to a working desktop, common apps work, including Virtualbox and a Windpows XP guest. Looks good on this hardware.
On same hardware as Comment 44, 32-bit install: The following 14 packages are going to be installed: - btrfs-progs-4.14-2.mga6.i586 - cpupower-4.14.9-1.mga6.i586 - iproute2-4.14.1-1.mga6.i586 - iwlwifi-firmware-20171220-1.mga6.nonfree.noarch - kernel-firmware-nonfree-20171220-1.mga6.nonfree.noarch - kernel-server-4.14.9-1.mga6-1-1.mga6.i586 - kernel-server-latest-4.14.9-1.mga6.i586 - libbtrfs0-4.14-2.mga6.i586 - libxfs1-4.14.0-1.mga6.i586 - libzstd1-1.3.2-1.mga6.i586 - radeon-firmware-20171205-1.mga6.nonfree.noarch - ralink-firmware-20171220-1.mga6.nonfree.noarch - rtlwifi-firmware-20171220-1.mga6.nonfree.noarch - xfsprogs-4.14.0-1.mga6.i586 Boots to a working Plasma desktop. Common apps work. Looks good for 32-bit on this hardware.
On real hardware, ASRock motherboard, Athlon X2 7750 processor, 8GB, nvidia Geforce 9800GT graphics, Atheros wifi. The following 12 packages are going to be installed: - cpupower-4.14.9-1.mga6.x86_64 - iwlwifi-firmware-20171220-1.mga6.nonfree.noarch - kernel-firmware-nonfree-20171220-1.mga6.nonfree.noarch - kernel-server-4.14.9-1.mga6-1-1.mga6.x86_64 - kernel-server-devel-4.14.9-1.mga6-1-1.mga6.x86_64 - kernel-server-devel-latest-4.14.9-1.mga6.x86_64 - kernel-server-latest-4.14.9-1.mga6.x86_64 - kernel-userspace-headers-4.14.9-1.mga6.x86_64 - ralink-firmware-20171220-1.mga6.nonfree.noarch - rtlwifi-firmware-20171220-1.mga6.nonfree.noarch - virtualbox-kernel-4.14.9-server-1.mga6-5.2.2-4.mga6.x86_64 - virtualbox-kernel-server-latest-5.2.2-4.mga6.x86_64 Boots to a working desktop. Common apps work, including VirtualBox and a Windows XP guest. Looks good for 64-bit on this hardware.
On the same hardware as Comment 46, but 32-bit install, he following 10 packages are going to be installed: - cpupower-4.14.9-1.mga6.i586 - iwlwifi-firmware-20171220-1.mga6.nonfree.noarch - kernel-firmware-nonfree-20171220-1.mga6.nonfree.noarch - kernel-server-4.14.9-1.mga6-1-1.mga6.i586 - kernel-server-devel-4.14.9-1.mga6-1-1.mga6.i586 - kernel-server-devel-latest-4.14.9-1.mga6.i586 - kernel-server-latest-4.14.9-1.mga6.i586 - kernel-userspace-headers-4.14.9-1.mga6.i586 - ralink-firmware-20171220-1.mga6.nonfree.noarch - rtlwifi-firmware-20171220-1.mga6.nonfree.noarch Boots to a working Plasma desktop. Common apps work. Looks good for 32-bit on this hardware.
Installed the nvidia 304.137, xfs updates, btrfs updates (this system runs xfs for / and btrfs for /home. this AMD x2-3800 LE 6150 Nvidia I get a Kernel Panic on 4.14.9-1 Kernel $ uname -a Linux localhost 4.14.9-desktop-1.mga6 #1 SMP Mon Dec 25 17:20:31 UTC 2017 i686 i686 i686 GNU/Linux I have to over-ride the default boot with noapic to get it to start without locking up. What do you need from me to help debug this? Regards, Brian
(In reply to Brian Rockwell from comment #48) > Installed the nvidia 304.137, xfs updates, btrfs updates (this system runs > xfs for / and btrfs for /home. > > this AMD x2-3800 > LE 6150 Nvidia > > I get a Kernel Panic on 4.14.9-1 Kernel > ouch. > $ uname -a > Linux localhost 4.14.9-desktop-1.mga6 #1 SMP Mon Dec 25 17:20:31 UTC 2017 > i686 i686 i686 GNU/Linux > > > I have to over-ride the default boot with noapic to get it to start without > locking up. > ok, so it works atleast partly... > What do you need from me to help debug this? > I want to see the panic. Either check if it got logged or remove "splash silent" from kernel command line and take a photo of the panic
Ouch! I was about to validate the kernel updates. I've tested all kernels for both arches on real hardware and under virtualbox with no problems found.
Whiteboard: (none) => MGA6-64-OK MGA6-32-OKKeywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Dropping validation because of comment 49 for new
Keywords: validated_update => (none)
... for *now* ... atleast until I get to see the crash
Hi - it told me to do apic=DEBUG. I did that, where does it dump to? I'll attach that as well as a photo if needed. Brian
Created attachment 9856 [details] Photo of Kernel Panic Took the picture this morning. Let me know what you need, I can try the apic=debug if you can tell me where to capture the dump from it.
(In reply to Brian Rockwell from comment #53) > Hi - it told me to do apic=DEBUG. I did that, where does it dump to? > > it should show up in the log or on the screen, so please boot with apic=debug and post a photo of it
Created attachment 9857 [details] dmsg output nothing in journalctl as it seems to freeze before that. Did include dmsg and see if you get anything out of that.
(In reply to Brian Rockwell from comment #56) > Created attachment 9857 [details] > dmsg output > > nothing in journalctl as it seems to freeze before that. Did include dmsg > and see if you get anything out of that. And the photo of kernel panic when booted with "apic=debug" ?
Created attachment 9858 [details] Second picture I snapped another, nothing I can see different.
From a thread in qa-discuss, when Brian originally installed the update, he didn't install the kernel-devel packages. That would mean that the nvidia304 module wasn't built. But, "nokmsboot" should have still been in the kernel options at boot time. Could this have resulted in the kernel panic he's seeing?
On real hardware, Intel Core2Duo, 8GB, Intel graphics, wired Internet: The following 9 packages are going to be installed: - cpupower-4.14.9-1.mga6.x86_64 - iwlwifi-firmware-20171220-1.mga6.nonfree.noarch - kernel-desktop-4.14.9-1.mga6-1-1.mga6.x86_64 - kernel-desktop-latest-4.14.9-1.mga6.x86_64 - kernel-firmware-nonfree-20171220-1.mga6.nonfree.noarch - ralink-firmware-20171220-1.mga6.nonfree.noarch - rtlwifi-firmware-20171220-1.mga6.nonfree.noarch - virtualbox-kernel-4.14.9-desktop-1.mga6-5.2.2-4.mga6.x86_64 - virtualbox-kernel-desktop-latest-5.2.2-4.mga6.x86_64 System boots to a working Plasma desktop. Common apps work properly, including a Windows XP guest in VirtualBox. Looks good for 64-bit on this hardware.
(In reply to Thomas Andrews from comment #59) > From a thread in qa-discuss, when Brian originally installed the update, he > didn't install the kernel-devel packages. That would mean that the nvidia304 > module wasn't built. But, "nokmsboot" should have still been in the kernel > options at boot time. > > Could this have resulted in the kernel panic he's seeing? It shouldn't, but in order to really rule it out,.. @Brian, can you boot your system with the 4.14.9 using noapic, then use XFdrake to reconfigure your system to use the free drivers, either nouveau, modesetting or vesa. Then uninstall any nvidia304 package with: rpm -qa |grep nvidia304 |xargs urpme recreate a clean initrd with: dracut -f and reboot... does it boot up then? Also you can try to boot to runlevel 3 by adding a number: 3 on kernel command line...
CC: lewyssmith => (none)
Just another OK 64 bit 4.14.9-desktop-1.mga6 in real use; 1) Successful and no hickup update on my i7 workstation including latest nvidia-current (nonfree testing), running LVM on LUKS, VirtualBox, BOINC using CUDA 2) Thinkpad T400, intel graphics, multiboot, all OK.
CC: (none) => fri
@comment 61 - Thomas Tried the recommended options. Run level 3 - no luck, same lockup Uninstall 304 and try another driver - failed noapic - kernel boots and works fine. That's been my go to at the command line. Is this related to the unusual nvidia hardware set for usb, video, etc.?
(In reply to Brian Rockwell from comment #63) > @comment 61 - Thomas > > Is this related to the unusual nvidia hardware set for usb, video, etc.? Nope, thats why I wanted to remove the nvidia304 driver from it to rule out proprietary driver messing it up. There has been a few reports upstream about 4.14.9 not booting properly.. Can you test a 4.14.9-2.mga6 from: http://tmb2.mine.nu/Cauldron/x86_64/ It has 4.14.10-rc1 applied that removed some buggy patches that landed in 4.14.9 and some more missing fixes...
@Thomas This machine is running 32-bit. Do you have the 32-bit ones ready?
(In reply to Brian Rockwell from comment #65) > @Thomas > This machine is running 32-bit. > > Do you have the 32-bit ones ready? Ah, sorry abot that... There is now: http://tmb2.mine.nu/6/i586/
(@Thomas - Comment 66) Installed in the following order using basic <click rpm> and select <Install> kernel-desktop-4.14.9-2.mga6-1-1.mga6.i586 kernel-desktop-devel-4.14.9-2.mga6-1-1.mga6.i586 kernel-desktop-latest-4.14.9-2.mga6.i586 kernel-desktop-devel-latest-4.14.9-2.mga6.i586 Rebooted, went to advanced and checked edits and started 4.14.9-2. Hangs there with a flashing cursor, but doesn't freeze, which is different from before. Not XFS / and btrfs /home. My guess, I didn't install right. Suggestions? ---- I'm going to see if a have a drive for this machine with 64-bit version and see what happens with 4.14.9-1.
(In reply to Brian Rockwell from comment #67) > (@Thomas - Comment 66) > > Installed in the following order using basic <click rpm> and select <Install> > > kernel-desktop-4.14.9-2.mga6-1-1.mga6.i586 > kernel-desktop-devel-4.14.9-2.mga6-1-1.mga6.i586 > kernel-desktop-latest-4.14.9-2.mga6.i586 > kernel-desktop-devel-latest-4.14.9-2.mga6.i586 > > Rebooted, went to advanced and checked edits and started 4.14.9-2. > > Hangs there with a flashing cursor, but doesn't freeze, which is different > from before. Not XFS / and btrfs /home. > Are you using nVidia or nouveau driver? Can you remove: splash quiet noapic from kernel command line, and also nokmsboot if you are using nouveau And post a pic of the crash/hang if it crashes/hangs
btw @Brian, what was the last kernel that worked for you ?
@Thomas 1. nvidia as Nouveau doesn't work. 2. I did, it hung on 4.14.9.2 before displaying first effort, makes me thing grub hung on /boot 3. Tried that still hung 4. I'll describe it, cursor in upper left-hand corner Last functional Kernel - 4.9.56 noapic allows me to use 4.14.9.1 (I'll need to look up that option to learn more). Just finished building 64-bit on a spare drive with this machine. Will try upgrades now. I'm theorizing I may have something else whacky that is a red herring for the Kernel.
Created attachment 9861 [details] dmsg -> 4.14.9.1 Kernel - 64bit Freezing Well, same issue on 64-bit. noapic worked though, so the system is up. nvidia running # lsmod | grep nvidia nvidia 11423744 30 drm 425984 2 nvidia # uname -a Linux localhost.localdomain 4.14.9-desktop-1.mga6 #1 SMP Mon Dec 25 15:27:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
(In reply to Brian Rockwell from comment #70) > Last functional Kernel - 4.9.56 Ok, can you attach dmesg from that kernel too so I can compare hw init
This is my ignorance speaking. Will a reboot and dmesg be enough? I'll do that now and attach in a few minutes, if it involves more, may be late tonight or on Saturday.
Created attachment 9862 [details] dmesg 4.9.56 Kernel - 64bit Attaching the dmesg after reboot to 4.9.56
4.14.10-desktop-1.mga6 quick tests OK @ machines and tests as my comment 62.
updated to 4.14.10 for additional fixes. advisory in svn updated. new rpms to test: SRPMS: kernel-4.14.10-1.mga6.src.rpm kernel-userspace-headers-4.14.10-1.mga6.src.rpm kmod-vboxadditions-5.2.2-5.mga6.src.rpm kmod-virtualbox-5.2.2-5.mga6.src.rpm kmod-xtables-addons-2.13-8.mga6.src.rpm cpupower-4.14.10-1.mga6.i586.rpm cpupower-devel-4.14.10-1.mga6.i586.rpm kernel-desktop-4.14.10-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-4.14.10-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-devel-4.14.10-1.mga6-1-1.mga6.i586.rpm kernel-desktop586-devel-latest-4.14.10-1.mga6.i586.rpm kernel-desktop586-latest-4.14.10-1.mga6.i586.rpm kernel-desktop-devel-4.14.10-1.mga6-1-1.mga6.i586.rpm kernel-desktop-devel-latest-4.14.10-1.mga6.i586.rpm kernel-desktop-latest-4.14.10-1.mga6.i586.rpm kernel-doc-4.14.10-1.mga6.noarch.rpm kernel-server-4.14.10-1.mga6-1-1.mga6.i586.rpm kernel-server-devel-4.14.10-1.mga6-1-1.mga6.i586.rpm kernel-server-devel-latest-4.14.10-1.mga6.i586.rpm kernel-server-latest-4.14.10-1.mga6.i586.rpm kernel-source-4.14.10-1.mga6-1-1.mga6.noarch.rpm kernel-source-latest-4.14.10-1.mga6.noarch.rpm kernel-userspace-headers-4.14.10-1.mga6.i586.rpm perf-4.14.10-1.mga6.i586.rpm vboxadditions-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6.i586.rpm vboxadditions-kernel-4.14.10-desktop586-1.mga6-5.2.2-5.mga6.i586.rpm vboxadditions-kernel-4.14.10-server-1.mga6-5.2.2-5.mga6.i586.rpm vboxadditions-kernel-desktop586-latest-5.2.2-5.mga6.i586.rpm vboxadditions-kernel-desktop-latest-5.2.2-5.mga6.i586.rpm vboxadditions-kernel-server-latest-5.2.2-5.mga6.i586.rpm virtualbox-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6.i586.rpm virtualbox-kernel-4.14.10-desktop586-1.mga6-5.2.2-5.mga6.i586.rpm virtualbox-kernel-4.14.10-server-1.mga6-5.2.2-5.mga6.i586.rpm virtualbox-kernel-desktop586-latest-5.2.2-5.mga6.i586.rpm virtualbox-kernel-desktop-latest-5.2.2-5.mga6.i586.rpm virtualbox-kernel-server-latest-5.2.2-5.mga6.i586.rpm xtables-addons-kernel-4.14.10-desktop-1.mga6-2.13-8.mga6.i586.rpm xtables-addons-kernel-4.14.10-desktop586-1.mga6-2.13-8.mga6.i586.rpm xtables-addons-kernel-4.14.10-server-1.mga6-2.13-8.mga6.i586.rpm xtables-addons-kernel-desktop586-latest-2.13-8.mga6.i586.rpm xtables-addons-kernel-desktop-latest-2.13-8.mga6.i586.rpm xtables-addons-kernel-server-latest-2.13-8.mga6.i586.rpm x86_64: cpupower-4.14.10-1.mga6.x86_64.rpm cpupower-devel-4.14.10-1.mga6.x86_64.rpm kernel-desktop-4.14.10-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-devel-4.14.10-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-devel-latest-4.14.10-1.mga6.x86_64.rpm kernel-desktop-latest-4.14.10-1.mga6.x86_64.rpm kernel-doc-4.14.10-1.mga6.noarch.rpm kernel-server-4.14.10-1.mga6-1-1.mga6.x86_64.rpm kernel-server-devel-4.14.10-1.mga6-1-1.mga6.x86_64.rpm kernel-server-devel-latest-4.14.10-1.mga6.x86_64.rpm kernel-server-latest-4.14.10-1.mga6.x86_64.rpm kernel-source-4.14.10-1.mga6-1-1.mga6.noarch.rpm kernel-source-latest-4.14.10-1.mga6.noarch.rpm kernel-userspace-headers-4.14.10-1.mga6.x86_64.rpm perf-4.14.10-1.mga6.x86_64.rpm vboxadditions-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6.x86_64.rpm vboxadditions-kernel-4.14.10-server-1.mga6-5.2.2-5.mga6.x86_64.rpm vboxadditions-kernel-desktop-latest-5.2.2-5.mga6.x86_64.rpm vboxadditions-kernel-server-latest-5.2.2-5.mga6.x86_64.rpm virtualbox-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6.x86_64.rpm virtualbox-kernel-4.14.10-server-1.mga6-5.2.2-5.mga6.x86_64.rpm virtualbox-kernel-desktop-latest-5.2.2-5.mga6.x86_64.rpm virtualbox-kernel-server-latest-5.2.2-5.mga6.x86_64.rpm xtables-addons-kernel-4.14.10-desktop-1.mga6-2.13-8.mga6.x86_64.rpm xtables-addons-kernel-4.14.10-server-1.mga6-2.13-8.mga6.x86_64.rpm xtables-addons-kernel-desktop-latest-2.13-8.mga6.x86_64.rpm xtables-addons-kernel-server-latest-2.13-8.mga6.x86_64.rpm
Summary: Update request: kernel 4.14.9 => Update request: kernel 4.14.10Whiteboard: MGA6-64-OK MGA6-32-OK => (none)
(In reply to Brian Rockwell from comment #74) > Created attachment 9862 [details] > dmesg 4.9.56 Kernel - 64bit > > Attaching the dmesg after reboot to 4.9.56 ok, now I'm confused... according to this you are using noapic on 4.9.56 too so it's not a regression then ... (even if it would be nice to fix) The upstream reported regressions turned out to be all running gentoo hardened with a broken toolchain that tries to enforce a broken stack checking on the kernel... Anyway, as I haven't seen any other issues with this kernel I think as soon as 4.14.10 is tested on both arches I think it can be validated... @Brian, we should still try to figure out why it breaks without noapic for you, but preferably in a new bug so we dont flood this one...
Interesting noapic must of been loaded into 4.9.56 as well then. :-( ok - I'll see what 4.14.10 does.
Created attachment 9869 [details] dmsg 4.9.56 with noapic disabled I used the boot routine to setup noapic, it must of added it to all options. I've over-ridden it and restarted 4.9.56 with noapic removed. New dmsg attached.
AMD x2-3800, nvidia 6150 le This is the box that requires noapic set. $ uname -a Linux localhost.localdomain 4.14.10-desktop-1.mga6 #1 SMP Sat Dec 30 01:10:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux no regressions. Will test the intel i3 laptop.
video: Core Processor Integrated Graphics Controller Intel(R) Core(TM) i3 CPU M 350 @ 2.27GHz wifi: RTL8191SEvB Wireless LAN Controller The following 6 packages are going to be installed: - cpupower-4.14.10-1.mga6.i586 - kernel-desktop-4.14.10-1.mga6-1-1.mga6.i586 - kernel-desktop-latest-4.14.10-1.mga6.i586 - vboxadditions-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6.i586 - virtualbox-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6.i586 - virtualbox-kernel-desktop-latest-5.2.2-5.mga6.i586 51MB of additional disk space will be used. 51MB of packages will be retrieved. Is it ok to continue? $ uname -a Linux localhost.localdomain 4.14.10-desktop-1.mga6 #1 SMP Sat Dec 30 00:56:37 UTC 2017 i686 i686 i686 GNU/Linux Mga6-32 Plasma Libreoffice works, Firefox working, Chromium working, wifi is working, screen is at normal resolution. Working as designed.
Okay - maybe a regression here on the laptop. When I close the lid, the system appears to go to sleep (this is normal). I open the lid, it restarts instead of waking up. Can someone else with a laptop confirm this?
Whiteboard: (none) => feedback
64-bit desktop kernel working OK on my HP Probook 6550b. (i3, 8GB, Intel graphics, Intel wifi) No problems when closing and opening lid. Will try 32-bit next, though it will be the server kernel because of the amount of RAM.
@TMB I concur - noapic regression is an easy solution, so let's move forward with the 4.14.10. TJ - is your laptop sleeping and waking up fine? If so, wondering if I failed to install a key component as part of the upgrade. @all - sorry to be such a problem child on this one...no idea why I get to be the fun person this time around..... :-(
With the 32-bit server kernel 4.14.10, same hardware as Comment 83. Seems to be working OK. At first, when I closed the lid the screen locked when it came back up, but I had failed to check the behavior prior to installing the updated kernel. Going to System Settings/Desktop Behavior/Screen Locking and unchecking the "Lock screen on resume" box stopped it from locking again when the screen was closed. I am inclined to think that this behavior was not because of the kernel update, but because of a setting that carried through. Therefore, I am saying that this kernel is OK on this hardware.
ok - booted back to 4.9.56 and the suspend / restore works properly on this laptop. 4.14.10 seems to fail. what do you need to debug this?
On real hardware, ASRock motherboard, Athlon X2 7750, 8GB, nvidia Geforce 9800 GT graphics, Atheros wifi: Both 32-bit and 64-bit server kernels 4.14.10 are looking good, with the nvidia340 driver that is also being tested.
Installed kernel-tmb-desktop-4.14.10-1 It works with suspend mode (sleep) when lid is closed. I guess I'll update that testing. :-) Happy New Years everyone (already there in NZ, AU, and Eastern Europe I guess).
Updated all packages $ drakboot --boot Rebooted to Mate desktop - nvidia kmod had been built already. System: Host: difda Kernel: 4.14.10-desktop-1.mga6 x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Mageia 6 mga6 Machine: Device: desktop Mobo: MSI model: Z97-G43 (MS-7816) v: 3.0 UEFI: American Megatrends v: V17.8 date: 12/24/2014 Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 RAM: 31.37 GB Ran stress tests for about 20 seconds each. As before on this particular hardware the disk io test failed to terminate, respawning every 20 seconds, but it ran out of steam eventually. Ran glmark2, stellarium and several common applications. No problems. NFS shares OK. ssh remote login and scp. Installed dkms-virtualbox which built vboxdrv and other modules. Launched a vbox OK. Working fine for Mageia 6 on 64-bit hardware.
Updated desktop packages and ran 'drakboot --boot'. Rebooted to working Mate desktop. System: Host: markab Kernel: 4.14.10-desktop-1.mga6 x86_64 (64 bit) Desktop: MATE 1.18.0 Distro: Mageia 6 mga6 CPU: Quad core Intel Core i7-5700HQ (-HT-MCP-) Machine: Device: laptop System: GIGABYTE product: X5 Mobo: GIGABYTE model: X5 Graphics: Card-1: NVIDIA GM204M [GeForce GTX 965M] Card-2: NVIDIA GM204M [GeForce GTX 965M] Resolution: 2880x1620@59.96hz GLX Version: 4.5.0 NVIDIA 384.98 Network: Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx Card-2: Intel Wireless 7265 driver: iwlwifi stress tests and glmark2 ran smoothly. Desktop applications worked fine. 64-bit OK on this machine.
re comment 90: closed the lid on this laptop and opened it a little later - session resumed normally.
(In reply to Brian Rockwell from comment #86) > ok - booted back to 4.9.56 and the suspend / restore works properly on this > laptop. > > 4.14.10 seems to fail. > > what do you need to debug this? It can be a fallout of having to run with noapic. I'll check with upstream if they have some ideas about the apic stuff or if a bisection is the way to go... Anyway, we wont hold back this kernel update for this issue as it also closes several security issues and the "noapic" is an acceptable workaround for now.
Whiteboard: feedback => (none)
it's not the fall-out from noapic as this is a different machine that had no issues with the apic aspect of the kernel. yes - move ahead, but I suspect the sleep thing will hit older generation core ix processors.
(In reply to Brian Rockwell from comment #93) > it's not the fall-out from noapic as this is a different machine that had no > issues with the apic aspect of the kernel. > Ah, sorry, I mixed the reports. > yes - move ahead, but I suspect the sleep thing will hit older generation > core ix processors. Maybe, maybe not... whats the hw specs
(In reply to Brian Rockwell from comment #93) > it's not the fall-out from noapic as this is a different machine that had no > issues with the apic aspect of the kernel. > > yes - move ahead, but I suspect the sleep thing will hit older generation > core ix processors. Maybe not, Brian. The i3 in my Probook is an M 350, same as yours. And it uses the integrated Intel graphics. One difference: mine uses Intel wifi, but I can't see that causing the lid problem.
64-bit desktop kernel 4.14.10 is working fine with my Intel Core2Duo Plasma desktop. Intel motherboard, Intel graphics, wired Internet.
In a Vbox client, M6, Plasma, 32bit Testing: kernel-desktop-latest vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:53:48 UTC 2017 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.i586 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-1.mga6.i586 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Installed kernel-desktop-latest vboxadditions-kernel-desktop-latest from updates testing Reboot client [root@localhost wilcal]# uname -a Linux localhost 4.14.10-desktop-1.mga6 #1 SMP Sat Dec 30 00:56:37 UTC 2017 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.14.10-1.mga6.i586 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-5.mga6.i586 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work.
In a Vbox client, M6, Plasma, 64bit Testing: kernel-desktop-latest vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:55:31 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-1.mga6.x86_64 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work. Installed kernel-desktop-latest vboxadditions-kernel-desktop-latest from updates testing Reboot client [root@localhost wilcal]# uname -a Linux localhost 4.14.10-desktop-1.mga6 #1 SMP Sat Dec 30 01:10:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.14.10-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-5.mga6.x86_64 is already installed Boots to a working desktop. Screen resolution is correct. Common apps work.
On real hardware, M6, Plasma, 64-bit initial install: kernel-desktop-latest virtualbox vboxadditions-kernel-desktop-latest dkms-virtualbox virtualbox-guest-additions virtualbox-kernel-desktop-latest x11-driver-video-vboxvideo kernel-desktop-devel-latest dkms-nvidia-current [root@localhost wilcal]# uname -a Linux localhost 4.9.56-desktop-1.mga6 #1 SMP Thu Oct 12 22:55:31 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox Package virtualbox-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-virtualbox Package dkms-virtualbox-5.2.2-1.mga6.noarch is already installed [root@localhost wilcal]# urpmi virtualbox-guest-additions Package virtualbox-guest-additions-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox-kernel-desktop-latest Package virtualbox-kernel-desktop-latest-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi x11-driver-video-vboxvideo Package x11-driver-video-vboxvideo-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi kernel-desktop-devel-latest Package kernel-desktop-devel-latest-4.9.56-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-nvidia-current Package dkms-nvidia-current-384.98-1.mga6.nonfree.x86_64 is already installed [wilcal@localhost ~]$ 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_drm, nvidia_current M6 i586 Xfce Live-DVD runs as a Vbox client. Boots to a working desktop. Common apps work. Screen sizes are correct. update: kernel-desktop-latest virtualbox vboxadditions-kernel-desktop-latest dkms-virtualbox virtualbox-guest-additions virtualbox-kernel-desktop-latest x11-driver-video-vboxvideo kernel-desktop-devel-latest dkms-nvidia-current from updates_testing [root@localhost wilcal]# uname -a Linux localhost 4.14.10-desktop-1.mga6 #1 SMP Sat Dec 30 01:10:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi kernel-desktop-latest Package kernel-desktop-latest-4.14.10-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox Package virtualbox-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-5.2.2-5.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-virtualbox Package dkms-virtualbox-5.2.2-1.mga6.noarch is already installed [root@localhost wilcal]# urpmi virtualbox-guest-additions Package virtualbox-guest-additions-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi virtualbox-kernel-desktop-latest Package virtualbox-kernel-desktop-latest-5.2.2-5.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi x11-driver-video-vboxvideo Package x11-driver-video-vboxvideo-5.2.2-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi kernel-desktop-devel-latest Package kernel-desktop-devel-latest-4.14.10-1.mga6.x86_64 is already installed [root@localhost wilcal]# urpmi dkms-nvidia-current Package dkms-nvidia-current-384.98-2.mga6.nonfree.x86_64 is already installed [wilcal@localhost ~]$ 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_drm, nvidia_current M6 i586 Xfce LiveDVD still runs as a Vbox client. M6 x86_64 Gnome LiveDVD runs as a Vbox client. Boots to a working desktop. Common apps work. Screen sizes are correct. M6 x86_64 CI installs and runs as a Vbox client. Updates then reboots back to a working desktop. Screen sizes 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) Looks good
MGA6-32 on Dell Latitude D600 MATE Installed desktop kernel and rebooted Then read newspaper in Firefox with text, pictures and video items. Checked NFS access to shares on desktop machine, opened txt ,ods and odp files, played wav and mpg file, all OK. As far as I can test here, OK for me.
CC: (none) => herman.viaene
Tested 64bit server kernel in two qemu vms (proxmox 5.1). Nothing to note.
CC: (none) => lists.jjorge
Updated the kernel on a 64-bit MBR laptop (Lenovo Ideapad Y500). On reboot nvidia was not rebuilt against the kernel although there was a message about the 'dkms-autoinstaller on first boot'. Nothing happened and the screen ended up with the Good Luck message. Installing nvidia at that point did no good - it just went round in a loop through reboot. Tried installing the vesa driver and succeeded in booting to the Mate desktop. Ran drakx11 again and installed the nvidia driver. Rebooted to the grub prompt. Having lost the bootloader that laptop is toast until I have time for a recovery operation.
(In reply to Len Lawrence from comment #102) > Updated the kernel on a 64-bit MBR laptop (Lenovo Ideapad Y500). > On reboot nvidia was not rebuilt against the kernel although there was a > message about the 'dkms-autoinstaller on first boot'. Nothing happened and > the screen ended up with the Good Luck message. Installing nvidia at that > point did no good - it just went round in a loop through reboot. Tried > installing the vesa driver and succeeded in booting to the Mate desktop. > Ran drakx11 again and installed the nvidia driver. Rebooted to the grub > prompt. Having lost the bootloader that laptop is toast until I have time > for a recovery operation. which nvidia ? If it was nvidia-current, did you remember to use the one in testing: https://bugs.mageia.org/show_bug.cgi?id=22256 did you install the matching kernel-devel ?
re comment 103: Yes it was nvidia-current but not the one from testing. I had wondered. Yes, I always install the kernel-devel package. In the process of recovering the laptop just now - I may have to run the nvidia update under the vesa driver.
Updated the kernel packages on this machine: System: Host: difda Kernel: 4.14.10-desktop-1.mga6 x86_64 CPU: Quad core Intel Core i7-4790 (-HT-MCP-) speed/max: 3600/4000 MHz Machine: Device: desktop Mobo: MSI model: Z97-G43 (MS-7816) v: 3.0 UEFI: American Megatrends v: V17.8 date: 12/24/2014 Graphics: Card: NVIDIA GM204 [GeForce GTX 970] GLX Version: 4.5.0 NVIDIA 384.98 $ drakboot --boot Warm reboot to a working desktop. glmark2 and stress tests completed successfully and everything else looks fine. OK for this machine.
re comments 103,104: You were right Thomas. No kernel-devel package for that installation. Repairing that now. I always "intend" to install kernel-devel but somehow that one slipped through the net. Trying to work on three machines at once - you get confused.
Three hours down the line it finally works. Adventures with vesa and nouveau on one partition always ended in tears aka the grub prompt. After three bootloader rescues I gave up on that and marked that partition as no entry. Moved to the adjacent partition and found that nvidia-current had already been updated. After that it was plain sailing. Updated to the new kernel. Mageia release 6 (Official) for x86_64 4.14.10-desktop-1.mga6 Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz NVIDIA Corporation GK107M [GeForce GT 650M] RAM 7.75 GB $ drakboot --boot Warm reboot to a working desktop. Ran the stress tests successfully and glmark2 returned a surprisingly high score for this old slow machine, practically double those returned by earlier tests. Common desktop applications seem to be OK. Mounted nfs share manually because there was an outdated entry in fstab. ssh login on the LAN works. 219 package update from Core Updates. This kernel update is good on this 64-bit hardware.
I've been running on 4.14.8-desktop-2.mga6 without issues the last couple of weeks. About to reboot for 4.14.10-desktop-1.mga6. Wireguard been working great (thanks tmb!) Intel E3-1230 V2 @ 3.30GHz Asrock H77 Pro4/MVP Radeon RX580 8GB (amdgpu) 16GB DDR3 RAM (4x 4GB)
CC: (none) => sam
All kernels ok on my system, both under vb and on real hardware. Note: To avoid the apparent lockup while installing all of the kernels on the 16GB ram system, I've added ... # cat /etc/sysctl.d/vm.dirty.conf vm.dirty_bytes = 629145600 vm.dirty_background_bytes = 314572800 That's from https://www.novell.com/support/kb/doc.php?id=7010287 That appears to fix the problem.
(In reply to Dave Hodgins from comment #109) > All kernels ok on my system, both under vb and on real hardware. > > Note: To avoid the apparent lockup while installing all of the kernels on > the 16GB > ram system, I've added ... > # cat /etc/sysctl.d/vm.dirty.conf > vm.dirty_bytes = 629145600 > vm.dirty_background_bytes = 314572800 > Is this on 32bit or 64bit ? I guess that it is somewhat hw dependent as I have systems here with 8/16/32GB ram and neither have a problem (I only use x86_64)
The new kernel-desktop worked fine on my Core i3 live x86-64 system with 8 GB of RAM - tested startx, plasma5, extreme tuxracer, vlc with vid+aud, konsole, freecell solver, firefox on youtube/etc.
CC: (none) => shlomif
# uname -a Linux mag6-final 4.14.10-desktop-1.mga6 #1 SMP Sat Dec 30 01:10:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Tested on a Sony Vaio E Series notebook - Intel i5 4Core host kernel driver radeon, Radeon HD 7550M/7570M/7650M guest Mageia 6 on qemu/kvm kernel driver virtio-pci Everything is working fine. No regression found.
CC: (none) => bequimao.de
Whiteboard: (none) => MGA6-64-OK, MGA6-32-OKKeywords: (none) => validated_update
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2018-0062.html
Status: NEW => RESOLVEDResolution: (none) => FIXED