[Stable Update] 2018-04-02 - Kernels, ZFS, Pamac, Udisks2

update
stable

#1

Hi community,

welcome to another stable update of Manjaro. This is more a fixup. We worked again on our Kernels, Udisks2, spl/zfs and Pamac.

Our effort and all the needed information about the new security risk can be found here.

So please report back and give us feedback for given changes made to our repositories. Users of our 32-bit Distro should read this.


Current supported Kernels

  • linux316 3.16.56
  • linux318 3.18.102 [EOL]
  • linux41 4.1.51
  • linux44 4.4.126
  • linux49 4.9.92
  • linux414 4.14.31
  • linux415 4.15.14
  • linux416 4.16.0
  • linux-RT-LTS 4.14.28_rt23
  • linux-RT 4.14.28_rt23

Package Updates (Sat Mar 24 19:10:10 CET 2018)

  • stable core x86_64: 12 new and 12 removed package(s)
  • stable extra x86_64: 70 new and 69 removed package(s)
:: Different overlay package(s) in repository core x86_64

-------------------------------------------------------------------------------
                             PACKAGE           2017-03-27           2017-04-02
-------------------------------------------------------------------------------
                             linux41             4.1.50-1             4.1.51-1
                     linux41-headers             4.1.50-1             4.1.51-1
                            linux414            4.14.30-1            4.14.31-1
                    linux414-headers            4.14.30-1            4.14.31-1
                            linux415            4.15.13-1            4.15.14-1
                    linux415-headers            4.15.13-1            4.15.14-1
                            linux416 4.16.r180325.g3eb2ce8-1          4.16.0-1
                    linux416-headers 4.16.r180325.g3eb2ce8-1          4.16.0-1
                             linux44            4.4.124-1            4.4.126-1
                     linux44-headers            4.4.124-1            4.4.126-1
                             linux49             4.9.90-1             4.9.92-1
                     linux49-headers             4.9.90-1             4.9.92-1


:: Different overlay package(s) in repository extra x86_64

-------------------------------------------------------------------------------
                             PACKAGE           2017-03-27           2017-04-02
-------------------------------------------------------------------------------
    bootsplash-theme-manjaro-elegant                0.1-3                0.1-4
                bootsplash-theme-tux                0.1-2                0.1-4
                        linux316-spl              0.7.6-2              0.7.7-1
                        linux316-zfs              0.7.6-2              0.7.7-1
                        linux318-spl              0.7.6-2              0.7.7-1
                        linux318-zfs              0.7.6-2              0.7.7-1
                   linux41-acpi_call             1.1.0-34             1.1.0-35
                    linux41-bbswitch               0.8-34               0.8-35
                 linux41-broadcom-wl      6.30.223.271-15      6.30.223.271-16
                    linux41-catalyst     1:15.201.1151-31     1:15.201.1151-32
                 linux41-ndiswrapper              1.61-15              1.61-16
                      linux41-nvidia           1:390.42-1           1:390.42-2
                linux41-nvidia-304xx          1:304.137-9         1:304.137-10
                linux41-nvidia-340xx            340.106-5            340.106-6
                    linux41-nvidiabl              0.88-31              0.88-32
       linux41-open-vm-tools-modules      2:2013.09.16-34      2:2013.09.16-35
                       linux41-r8168           8.045.08-5           8.045.08-6
                   linux41-rt3562sta        2.4.1.1_r4-15        2.4.1.1_r4-16
                         linux41-spl              0.7.6-2              0.7.7-1
                    linux41-tp_smapi              0.41-35              0.41-36
                 linux41-vhba-module          20161009-15          20161009-16
    linux41-virtualbox-guest-modules              5.2.8-2              5.2.8-3
     linux41-virtualbox-host-modules              5.2.8-2              5.2.8-3
                         linux41-zfs              0.7.6-2              0.7.7-1
                  linux414-acpi_call             1.1.0-27             1.1.0-28
                   linux414-bbswitch               0.8-27               0.8-28
                linux414-broadcom-wl      6.30.223.271-27      6.30.223.271-28
                   linux414-catalyst     1:15.201.1151-27     1:15.201.1151-28
                linux414-ndiswrapper              1.61-27              1.61-28
                     linux414-nvidia           1:390.42-4           1:390.42-5
               linux414-nvidia-304xx         1:304.137-27         1:304.137-28
               linux414-nvidia-340xx           340.106-15           340.106-16
                   linux414-nvidiabl              0.88-27              0.88-28
                      linux414-r8168          8.045.08-15          8.045.08-16
                  linux414-rt3562sta        2.4.1.1_r4-27        2.4.1.1_r4-28
                        linux414-spl              0.7.6-5              0.7.7-1
                   linux414-tp_smapi              0.41-27              0.41-28
                linux414-vhba-module          20161009-27          20161009-28
   linux414-virtualbox-guest-modules              5.2.8-7              5.2.8-8
    linux414-virtualbox-host-modules              5.2.8-7              5.2.8-8
                        linux414-zfs              0.7.6-5              0.7.7-1
                        linux415-spl              0.7.6-5              0.7.7-1
                        linux415-zfs              0.7.6-5              0.7.7-1
                  linux416-acpi_call           1.1.0-0.10           1.1.0-0.12
                   linux416-bbswitch             0.8-0.10             0.8-0.12
                linux416-broadcom-wl    6.30.223.271-0.10    6.30.223.271-0.12
                   linux416-catalyst   1:15.201.1151-0.10   1:15.201.1151-0.12
                linux416-ndiswrapper            1.61-0.10            1.61-0.12
                     linux416-nvidia        1:390.42-0.10        1:390.42-0.12
               linux416-nvidia-304xx       1:304.137-0.10       1:304.137-0.12
               linux416-nvidia-340xx         340.106-0.10         340.106-0.12
                   linux416-nvidiabl            0.88-0.10            0.88-0.12
                      linux416-r8168        8.045.08-0.10        8.045.08-0.12
                        linux416-spl           0.7.6-0.10           0.7.7-0.12
                   linux416-tp_smapi            0.41-0.10            0.41-0.12
                linux416-vhba-module        20161009-0.10        20161009-0.12
   linux416-virtualbox-guest-modules           5.2.8-0.10           5.2.8-0.12
    linux416-virtualbox-host-modules           5.2.8-0.10           5.2.8-0.12
                        linux416-zfs           0.7.6-0.10           0.7.7-0.12
                         linux44-spl              0.7.6-4              0.7.7-1
                         linux44-zfs              0.7.6-4              0.7.7-1
                         linux49-spl              0.7.6-5              0.7.7-1
                         linux49-zfs              0.7.6-5              0.7.7-1
                               pamac              6.2.6-1              6.2.7-1
             pamac-tray-appindicator              6.2.6-1              6.2.7-1
                            spl-dkms              0.7.6-1              0.7.7-1
                           spl-utils              0.7.6-1              0.7.7-1
                            zfs-dkms              0.7.6-1              0.7.7-1
                           zfs-utils              0.7.6-1              0.7.7-1
                             udisks2                    -            2.7.6-1.1

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:


KDE - Issue when mount USB
NVIDIA Prime setup errors
IPsec stack on 4.15.13-1
[Stable Update] 2018-05-26 - Kernels, Nvidia, Xorg-Server, Mesa, Browsers, Deepin, Calamares, Pamac
#2

Known issues and solutions

This is a wiki post; please edit as necessary.


/dev/mapper/control: open failed: No such device

Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.146 (2017-12-18) and kernel driver (unknown version).

This is affecting some systems (but not others, it may be related to LVM/LVM2). To fix:

sudo modprobe dm-mod
sudo update-grub

If you get modprobe: FATAL: Module dm-mod not found in directory ... reboot and try again (confirmed working by three people).


I don’t know if I’m up-to-date?

Compare your installed packages against those in the OP.


Pamac doesn’t show any updates

If Pamac don’t show any update, try these solutions:

  • Open Pamac, click on Pamac’s menu, then click on Refresh Database.
  • Open a terminal and do sudo pacman -Syu to do this update.

Something doesn’t work right with kernel 4.16

It’s still a very early kernel release so will have some bugs (e.g. brightness control doesn’t work on some laptops). This is pretty normal. Switch back to an earlier kernel version and try 4.16 as it matures.


My mouse is jittering like hell!

Seems the new libinput update created some issues with some touchpads. If our new kernel updates don’t solve the issue for you, you may think about downgrading libinput instead, until upstream found a proper solution for you:

sudo pacman -U https://archive.archlinux.org/packages/l/libinput/libinput-1.9.4-1-x86_64.pkg.tar.xz


[Testing Update] 2018-04-02 - Kernels, Gnome, Mesa, Pamac, Browsers, GStreamer, LibreOffice, PHP
Can't adjust screen brightness
#3

hello ,
i have this error on start with linux416 ( testing )

-- Logs begin at Sat 2016-08-20 17:10:45 CEST, end at Mon 2018-04-02 13:03:05 CEST. --
avril 02 13:01:10 mjro kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:07 [mem 0xfdb00000-0xfdffffff]
avril 02 13:01:10 mjro kernel: caller pmc_core_probe+0x95/0x222 mapping multiple BARs
avril 02 13:01:10 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata3.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata2.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata1.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata1.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata3.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata2.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: vboxdrv: loading out-of-tree module taints kernel.
avril 02 13:01:10 mjro kernel: VBoxNetAdp: Successfully started.
avril 02 13:01:10 mjro kernel: VBoxNetFlt: Successfully started.
avril 02 13:01:10 mjro kernel: VBoxPciLinuxInit
avril 02 13:01:10 mjro kernel: nvidia: module license 'NVIDIA' taints kernel.
avril 02 13:01:10 mjro kernel: Disabling lock debugging due to kernel taint
avril 02 13:01:10 mjro kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 PST 2018 (using threaded interrupts)
avril 02 13:01:10 mjro avahi-daemon[431]: Failed to parse address 'fe80::237:b7ff:fe98:964%enp0s31f6', ignoring.
CEST, end at Mon 2018-04-02 13:03:05 CEST. --
avril 02 13:01:10 mjro kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:07 [mem 0xfdb00000-0xfdffffff]
avril 02 13:01:10 mjro kernel: caller pmc_core_probe+0x95/0x222 mapping multiple BARs
avril 02 13:01:10 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata3.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata2.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata1.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata1.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata3.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: ata2.00: supports DRM functions and may not be fully accessible
avril 02 13:01:10 mjro kernel: vboxdrv: loading out-of-tree module taints kernel.
avril 02 13:01:10 mjro kernel: VBoxNetAdp: Successfully started.
avril 02 13:01:10 mjro kernel: VBoxNetFlt: Successfully started.
avril 02 13:01:10 mjro kernel: VBoxPciLinuxInit
avril 02 13:01:10 mjro kernel: nvidia: module license 'NVIDIA' taints kernel.
avril 02 13:01:10 mjro kernel: Disabling lock debugging due to kernel taint
avril 02 13:01:10 mjro kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 PST 2018 (using threaded interrupts)
avril 02 13:01:10 mjro avahi-daemon[431]: Failed to parse address 'fe80::237:b7ff:fe98:964%enp0s31f6', ignoring.
avril 02 13:01:12 mjro kernel: ------------[ cut here ]------------
avril 02 13:01:12 mjro kernel: Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
avril 02 13:01:12 mjro kernel: WARNING: CPU: 7 PID: 539 at mm/usercopy.c:81 usercopy_warn+0x7e/0xa0
avril 02 13:01:12 mjro kernel: Modules linked in: snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_cl>
avril 02 13:01:12 mjro kernel:  ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto hid_generic usbhid hid sd_mod ahci xhci_pci libahci xhci_hcd libata crc32c_intel usbcore scsi_mod usb_com>
avril 02 13:01:12 mjro kernel: CPU: 7 PID: 539 Comm: Xorg Tainted: P           O     4.16.0-1-MANJARO #1
avril 02 13:01:12 mjro kernel: Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 TH/Z170X-UD5 TH-CF, BIOS F22d 12/01/2017
avril 02 13:01:12 mjro kernel: RIP: 0010:usercopy_warn+0x7e/0xa0
avril 02 13:01:12 mjro kernel: RSP: 0018:ffffa4b902643b58 EFLAGS: 00010286
avril 02 13:01:12 mjro kernel: RAX: 0000000000000000 RBX: ffff92198a69dcb0 RCX: 0000000000000001
avril 02 13:01:12 mjro kernel: RDX: 0000000080000001 RSI: ffffffff86e5390c RDI: 00000000ffffffff
avril 02 13:01:12 mjro kernel: RBP: 0000000000000003 R08: 0000000000000098 R09: 000000000000035b
avril 02 13:01:12 mjro kernel: R10: ffffffff86e8c661 R11: 0000000000000001 R12: 0000000000000001
avril 02 13:01:12 mjro kernel: R13: ffff92198a69dcb3 R14: 0000000000000000 R15: ffff92198a69dcf8
avril 02 13:01:12 mjro kernel: FS:  00007f28de055940(0000) GS:ffff92199edc0000(0000) knlGS:0000000000000000
avril 02 13:01:12 mjro kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
avril 02 13:01:12 mjro kernel: CR2: 00007f28d5fe60f0 CR3: 0000000440ac6005 CR4: 00000000003606e0
avril 02 13:01:12 mjro kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
avril 02 13:01:12 mjro kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
avril 02 13:01:12 mjro kernel: Call Trace:
avril 02 13:01:12 mjro kernel:  __check_object_size+0x130/0x1a0
avril 02 13:01:12 mjro kernel:  os_memcpy_to_user+0x21/0x40 [nvidia]
avril 02 13:01:12 mjro kernel:  _nv009376rm+0xbf/0xe0 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv028060rm+0x79/0x90 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv028060rm+0x55/0x90 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv013692rm+0xee/0x100 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv015340rm+0x154/0x270 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv008309rm+0x134/0x1a0 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv008288rm+0x29c/0x2b0 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv001073rm+0xe/0x20 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv007315rm+0xd8/0x100 [nvidia]
avril 02 13:01:12 mjro kernel:  ? _nv001172rm+0x627/0x830 [nvidia]
avril 02 13:01:12 mjro kernel:  ? rm_ioctl+0x73/0x100 [nvidia]
avril 02 13:01:12 mjro kernel:  ? nvidia_ioctl+0x573/0x720 [nvidia]
avril 02 13:01:12 mjro kernel:  ? kmem_cache_free+0x1bd/0x1f0
avril 02 13:01:12 mjro kernel:  ? nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
avril 02 13:01:12 mjro kernel:  ? do_vfs_ioctl+0xa4/0x630
avril 02 13:01:12 mjro kernel:  ? __fput+0x131/0x1e0
avril 02 13:01:12 mjro kernel:  ? preempt_count_add+0x68/0xa0
avril 02 13:01:12 mjro kernel:  ? SyS_ioctl+0x74/0x80
avril 02 13:01:12 mjro kernel:  ? do_syscall_64+0x74/0x190
avril 02 13:01:12 mjro kernel:  ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
avril 02 13:01:12 mjro kernel: Code: 48 c7 c0 c9 db e5 86 48 0f 44 c2 41 50 51 41 51 48 89 f9 49 89 f1 4d 89 d8 4c 89 d2 48 89 c6 48 c7 c7 20 dc e5 86 e8 42 a4 e3 ff <0f> 0b 48 83 c4 18 c3 >
avril 02 13:01:12 mjro kernel: ---[ end trace 08f5822d3da93865 ]---

but Xfce start well :slight_smile:


#4

Currently the driver doesn’t play nice with the spectre/meltdown protection. Please turn it off for now or use an older kernel/nouveau drivers.


Nvidia dmesg stack trace with kernel 4.16
#5

udisks2 fix the ‘Malformed URL’ when inserting usb pen drives


#6

Linux416 is still some git commit version. I thought it was the stable one, released yesterday?

But I guess my mirror hasn’t finished syncing yet.


#7

Please use a mirror which already had synced


#8

I have same issue than Pepito in this post : [Testing Update] 2018-03-31 - Kernels, UDisks2, spl/zfs, Pamac

Indicator update and commande line for update is ok. But PAMAC don’t show any update.

I hope pamac in this update (6.2.7) will fixed this issue for the next update.


#9

Thanks for update! All OK! Kernel 4.14, radeon, KDE.


#10

9 posts were split to a new topic: Desktop pauses, jerky video, running hot, kswapd


#13

Hi,

Nice update!
This resolved my (little) issue with USB.

Thank you Team!


#14

earlier today, i received a update message, just for a few packages inxi, kernel, udisks2, pamac and applied before checking the forum.

now reading about todays stable update…

so i went ahead: sudo pacman -Syyu

nothing to do

first entry in my mirrorist:

# Country : Germany
Server = https://mirror.netzspielplatz.de/manjaro/packages/stable/$repo/$arch

but in mirror check service it seems to be up to date? :slight_smile:


#15

Check the list of packages in the OP. It’s kernels, udisks2, and Pamac… :roll_eyes:

:wink:


#18

sure, but i do not know about every package installed on my sys - looking at the ‘long’ list of packages and the very few updates received made me wonder.

quickest stable update ever, great stuff :wink:

thank you


#19

Flawlessly…


#23

I got again the issue with Pamac 6.2.6-1 that I reported in Testing on my laptop.

However, I could solve it entirely graphically with Pamac. I have just clicked on Pamac’s menu, then Refresh Database. Once it’s done, updates were shown by Pamac and I could update my system with Pamac without problem.

I don’t know why I didn’t tried that out in the first place, back in Testing, before using the command line. :smile:

This time, I didn’t refresh my mirror list at all, unlike what I previously did.

I added this solution in Wiki post.


#24

Update was smooth

Switched to kernel 4.16 (used 4.14 LTS previously)…gonna see if its worth the try.


#25

Hi there. Thanks for the update. I had issues switching to kernel 4.16.

I’m on a dell xps-15-9560, with nvidia proprietary drivers. I was using kernel 4.15 and had added acpi_rev_override=1 as a boot parameter.

After upgrading to kernel 4.16, I was unable to boot, the computer froze before the login screen. I tried removing the acpi_rev_override=1 thinking that maybe it was no longer needed with the new kernel but it didn’t work. Since I had to get back to work quickly and didn’t have time to look further into the issue, I logged in to a terminal and switched back to kernel 4.15.

Everything is working fine now. But I thought I would mention it in case this information is useful to anyone.


#26

Been using Manjaro- xfce-stable-kernel 4.14… for few months now without any major issue, untill I did the 3-27-2018 update. It was supposed to update kernel from 4.14.29 to 4.14.30.
The update went well without error ( that I could tell ). On 3-30-18 I was using my computer as usual, when i noticed on boot up the kernel being loaded was 4.14.29 not 30 , as per the update , tried using pacmac to check for updates it showed my system was up to date !
I do not know what happened but i went to pacmac history and there was no indication what so ever that there was an update performed on 3-27-18, the last repoted history was of the 3-23 update . Manjaro settings manager kernel app was showing the system running 4.14.29 and no new kernels avilable for 4.14 Lts . I ended up refreshing my mirrors as well as the database through pacmac but still it told me, my system was up to date ?? i did the refresh again but this time using the command line and this time it found the updates for 3-27-18 , and my kernel was actually updated this time to 4.14.30 as well as all the other updates. I thought may be it was just a glitch and did not worry about it.
Today I noticed on the forum that there is a new stable update 4-2-2018, which i did not recieve any notification about from pacmac . I went through the same steps and ended up updating through the terminal, now i am on the latest version fo pacmac (6.2.7.1) . My question now is : is there something different i should be doing to get pacmac notification or should i expect this to contiue for a while and should check for updates manually ? I am assuming my system is Ok as i recieved no errors and been working perfectly for several months since I installed Manjaro. I like Manjaro and planning to stick with it , and i like the idea of rolling release, OR to avoid future issues should i download the latest ISO and do a fresh install ?


#27

have you tried what it says at the top of the forum before you log in?

after these do sudo pacman -Syyu

If you’re getting an error similar to “Can’t update: signature from *** is marginal trust” or “invalid or corrupted package” you probably just need to update your package signing keys:

sudo pacman -Sy archlinux-keyring manjaro-keyring
sudo pacman-key --populate archlinux manjaro
sudo pacman-key --refresh-keys

If one fails, try the next then retry, and once all succeed retry the update.

If these still don’t work, check these threads: Issues with “signature is marginal trust” or “invalid or corrupted package”