[Stable Update] 2018-04-28 - Kernels, Cinnamon, Browsers, Mesa, KDE Apps, KDE Framework, Virtualbox

Hi,
No issue with KDE and Kernel 4.14.36-1.

Many thanks Team.

Thank you for your quick replies :slight_smile:
The 3 lines from @FadeMind solved the problem.

Sorry for posting about this AUR package here, I was not sure.

Thanks for your help!

1 Like
Age	Commit message (Expand)	Author	Files	Lines
2 days	Linux 4.14.37v4.14.37linux-4.14.y	Greg Kroah-Hartman	1	-1/+1
2 days	mac80211_hwsim: fix use-after-free bug in hwsim_exit_net	Benjamin Beichler	1	-2/+5
2 days	Revert "KVM: X86: Fix SMRAM accessing even if VM is shutdown"	Sean Christopherson	1	-1/+1
2 days	RDMA/mlx5: Fix NULL dereference while accessing XRC_TGT QPs

Linux 4.14.37v4.14.37linux-4.14.y have BugFiX

|2 days|mac80211_hwsim: fix use-after-free bug in hwsim_exit_net| |---|---|
|2 days|mac80211_hwsim: fix possible memory leak in hwsim_new_radio_nl()|

You have HowTo to create new Manjaro - Kernel ??

Followed the instruction and installed via TTY terminal. No errors and running smooth after the reboot back into Gnome. Thanks!

maybe related to DC?
you could try to add

amdgpu.dc=0

to your boot parameters (just a guess though)

always this error ( warning or not ? ) from drivers Nvidia at boot

avril 28 12:04:24 mjro kernel: ------------[ cut here ]------------
avril 28 12:04:24 mjro kernel: Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
avril 28 12:04:24 mjro kernel: WARNING: CPU: 3 PID: 513 at mm/usercopy.c:81 usercopy_warn+0x7e/0xa0
avril 28 12:04:24 mjro kernel: Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 nls_cp437 vfat fat snd_usb_audio snd_usbmidi_lib mousedev inpu>
avril 28 12:04:24 mjro kernel:  ipmi_msghandler vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) crypto_user ip_tables x_tables ext4 crc16 mbcache hid_generic jbd2 usbhid fscrypto hid sd_m>
avril 28 12:04:24 mjro kernel: CPU: 3 PID: 513 Comm: Xorg Tainted: P           O     4.16.4-1-MANJARO #1
avril 28 12:04:24 mjro kernel: Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 TH/Z170X-UD5 TH-CF, BIOS F22g 03/09/2018
avril 28 12:04:24 mjro kernel: RIP: 0010:usercopy_warn+0x7e/0xa0
avril 28 12:04:24 mjro kernel: RSP: 0018:ffffa5e502437b58 EFLAGS: 00010286
avril 28 12:04:24 mjro kernel: RAX: 0000000000000000 RBX: ffff933f8a53dcb0 RCX: 0000000000000001
avril 28 12:04:24 mjro kernel: RDX: 0000000080000001 RSI: ffffffff97e68e34 RDI: 00000000ffffffff
avril 28 12:04:24 mjro kernel: RBP: 0000000000000003 R08: 0000000000000098 R09: 0000000000000366
avril 28 12:04:24 mjro kernel: R10: ffffffff97ea5709 R11: 0000000000000001 R12: 0000000000000001
avril 28 12:04:24 mjro kernel: R13: ffff933f8a53dcb3 R14: 0000000000000000 R15: ffff933f8a53dcf8
avril 28 12:04:24 mjro kernel: FS:  00007f163c576940(0000) GS:ffff933f9ecc0000(0000) knlGS:0000000000000000
avril 28 12:04:24 mjro kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
avril 28 12:04:24 mjro kernel: CR2: 00007f1634502010 CR3: 0000000489086003 CR4: 00000000003606e0
avril 28 12:04:24 mjro kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
avril 28 12:04:24 mjro kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
avril 28 12:04:24 mjro kernel: Call Trace:
avril 28 12:04:24 mjro kernel:  __check_object_size+0x130/0x1a0
avril 28 12:04:24 mjro kernel:  os_memcpy_to_user+0x21/0x40 [nvidia]
avril 28 12:04:24 mjro kernel:  _nv009377rm+0xbf/0xe0 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv028067rm+0x79/0x90 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv028067rm+0x55/0x90 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv013694rm+0xee/0x100 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv015342rm+0x154/0x270 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv008310rm+0x134/0x1a0 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv008289rm+0x29c/0x2b0 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv001072rm+0xe/0x20 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv007316rm+0xd8/0x100 [nvidia]
avril 28 12:04:24 mjro kernel:  ? _nv001171rm+0x627/0x830 [nvidia]
avril 28 12:04:24 mjro kernel:  ? rm_ioctl+0x73/0x100 [nvidia]
avril 28 12:04:24 mjro kernel:  ? nvidia_ioctl+0x573/0x720 [nvidia]
avril 28 12:04:24 mjro kernel:  ? kmem_cache_free+0x1bd/0x1f0
avril 28 12:04:24 mjro kernel:  ? nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
avril 28 12:04:24 mjro kernel:  ? do_vfs_ioctl+0xa4/0x630
avril 28 12:04:24 mjro kernel:  ? __fput+0x131/0x1e0
avril 28 12:04:24 mjro kernel:  ? preempt_count_add+0x68/0xa0
avril 28 12:04:24 mjro kernel:  ? SyS_ioctl+0x74/0x80
avril 28 12:04:24 mjro kernel:  ? do_syscall_64+0x74/0x190
avril 28 12:04:24 mjro kernel:  ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
avril 28 12:04:24 mjro kernel: Code: 48 c7 c0 09 31 e7 97 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 60 31 e7 97 e8 82 a7 e3 ff <0f> 0b 48 83 c4 18 c3 >
avril 28 12:04:24 mjro kernel: ---[ end trace e5db606e02977a25 ]---

Good known issue. Resolved in 396.18 nvidia release (current in unstable manjaro branch). This drivers release drop support for fermi.
Reference: https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-Dropping-Fermi-Mainline

I think I install it few days ago. In unstable and didn't had any problems.
Does oracle would repackage without changing name? :thinking:

I manually removed js:

$ sudo pacman -Rs $(pacman -Qqdt)
[sudo] password for mparillo: 
checking dependencies...

Packages (1) js-24.2.0-4

Total Removed Size:  11.42 MiB

:: Do you want to remove these packages? [Y/n] y

1 Like

Xfce update went well with no errors, but keepass would not start after the update and a fresh boot.
Uninstall keepass and reinstall fixes the problem.
Happen with the last update as well.
Thanks for the update and hard work.

1 Like

smooth update no issues at the moment

1 Like

Termy you are right, it works with amdgpu.dc=0.
What am I missing out with this setting?
What would be the next step to get it working without this boot parameter?

Problem was with the extention pkg from AUR :slight_smile:

The login screen no longer shows for me. I'm investigating if a posted solution will work.

Weird enough, pressing the key combination "Control + Alt + F1" brings up the login screen.

Further info about this bug here.

I was only waiting for Nvidia driver 396.18 as the new Tomb Raider has some graphic glitches and poor performance on stable 390.48, any way to install 396.18 on stable manjaro gnome?

Hi comunity!!!
Update without problems in Manjaro Gnome on the desktop PC (AMD A10 7700K)

In Manjaro KDE, when restarting once the update was done, it did not turn on again, it remained cursor blinking in black screen. Install Manjaro Gnome and restart without problems after installation. (Laptop HP Intel I3 M350)

Thanks

is in unstable branch right now. you can switch branches or install the required packages by using:

sudo pacman -U http://manjaro.melbourneitmirror.net/unstable/core/x86_64/mhwd-nvidia-1:396.18-1-any.pkg.tar.xz

but you will need also the kenel and the modules i think ...

1 Like

This update completely hosed my /boot partition. I'm getting the unresolvable "vfat" partition error. Fun stuff.

rolling...

Oh i'm sure it was in testing updates at one point, that's why i thought it might be in Stable, funny how you can pick and chose kernels, but no way to pick Nvidia driver versions?

Forum kindly sponsored by